14:00:18 #startmeeting glance 14:00:23 Meeting started Thu May 19 14:00:18 2016 UTC and is due to finish in 60 minutes. The chair is nikhil. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:24 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:26 The meeting name has been set to 'glance' 14:00:29 #topic agenda 14:00:36 Welcome everyone 14:00:38 o/ 14:00:40 we've a small agenda today 14:00:41 o/ 14:00:46 ohai bpoulos 14:00:49 welcome back 14:00:51 hello, thanks! 14:00:51 congrats!!! 14:00:58 bpoulos: \o 14:01:02 thank you :) 14:01:05 o/ 14:01:08 how's your 'boy?'? 14:01:10 bpoulos: all good? 14:01:17 doing very well, 15 pounds already! 14:01:24 how did you call him? 14:01:27 mazel tov 14:01:28 Gregory 14:01:58 nice! good news indeed :) 14:02:19 so, here's the agenda for today: 14:02:25 #link https://etherpad.openstack.org/p/glance-team-meeting-agenda 14:02:41 Please be mindful of the dates when you propose the agenda 14:03:05 I usually keep next week's agenda open in case this week's full 14:03:33 We have decided to limit the agenda to only 4 items per meeting (besides updates and open discussion) 14:03:52 #action nikhil update the etherpad with more info on adding items to agenda 14:04:09 Let's get started. 14:04:15 #topic Updates 14:04:25 #info Glare updates ( mfedosin ) 14:04:42 hello again 14:04:52 two main things 14:05:02 1. api spec 14:05:15 I think we are ready to public discussion 14:05:50 for that reason I'll update the spec, add API examples that Darja made and upload new PS today 14:06:09 then I'm going to send a message to ML and ask for review 14:06:30 I hope it will be done early tomorrow 14:06:49 2. Glare code 14:07:12 Kairat and Darja are fixing bugs 14:07:26 6 of known 7 are done 14:07:38 that means that code is pretty stable at the moment 14:07:41 nice 14:07:49 mfedosin: this is good news indeed 14:07:58 we're getting to discussion early in cycle 14:08:03 we still have to add several features 14:08:29 ok 14:08:31 but my proposal, that in early June we'll start to prepare the code for merging 14:08:51 kairat: dshakhray correct me if I'm wrong 14:09:07 I hope so 14:09:31 but now, we need to concentrate on the spec 14:10:13 if API is agreed, then we can start implementing glare client 14:11:00 I think this is all the updates at the moment. 14:11:06 mfedosin: I think we need next meeting to decide on the features later (including more code like client). we agreed to a skeleton patch first, just to make sure that the team can focus on the bare minimum code. 14:11:21 mfedosin: and on the note to ML please link all tags that were interested. we need everyone on same page when it comes to the API! 14:11:37 yeah, sure 14:11:51 #info Nova v1, v2 ( mfedosin , sudipto ) 14:11:59 #link https://review.openstack.org/#/c/301741/ 14:12:21 hooray 14:12:22 SO, great news 14:12:36 thanks sudipto and flaper87 14:12:36 we have 3 different people +2 on it already 14:12:47 great job all three! 14:13:00 cheers mfedosin nikhil 14:13:02 (Acutally let's inclde Eddie on this good news too) 14:13:24 SO, what remains? 14:13:33 sudipto: mfedosin ? 14:13:48 emm, I think we need some clarification about v2 gate 14:14:07 mfedosin: I can update that later 14:14:18 from the coding front, i think we are sorted. 14:14:35 there was a mention about some code changes required in sudipto 's later spec patches? 14:14:35 because it blocks me from writing the code 14:15:00 k 14:15:02 also I updated sudipto's second patch 14:15:16 and fixed unit tests there 14:15:28 will upload new PS in a moment 14:15:47 thx mfedosin 14:16:07 also, as I mentioned, code is done 14:16:15 it's WIP but anyway 14:16:33 #link https://review.openstack.org/#/c/316440/ 14:17:17 unit tests will be fixed in sudipto's commit 14:17:33 yeah 14:17:59 So i am in sync with mfedosin and we should be able to put out all the reviews shortly after the spec is merged. 14:18:18 the main point is that all tempests are good :) 14:18:35 sudipto: even earlier :) 14:18:58 mfedosin, sure. Also I will work on the driver changes - that still use v1 - like i discussed with you. 14:19:24 mfedosin, i think we might be able to merge the spec today :) 14:19:25 ok, great stuff. 14:19:25 what driver again? 14:19:32 ah 14:19:33 Let's focus on the spec first 14:19:50 now spec is not our job 14:20:08 let's nova team review and merge it :) 14:20:13 That should be our priority, but looks good for now. Just keep an eye out for any last minute reviews :/ 14:20:13 *let 14:20:33 nikhil, sure. 14:20:37 also I have related question... 14:20:49 but let's postpone it to Open Discussion 14:20:55 mfedosin: this is openstack, we can only talk about merge only after the release. there are no guarantees until then. 14:21:11 let 14:21:28 let's move on, we need to have this detailed sync 30 mins before artifacts meeting on monday 14:21:35 let's keep our thursday updates small 14:21:51 Thanks much sudipto mfedosin 14:21:58 #info Releases 14:22:14 So, we're approaching newton-1 14:22:21 newton-1 Thursday June 2: 14:22:33 oh... so fast 14:22:35 http://releases.openstack.org/newton/schedule.html 14:22:51 yes, so just one more week and the week after we will tag newton 1 14:23:13 although the release page says thursdays are generally the dates when the release is cut 14:23:14 let 14:23:35 let's make sure that we get things done by Monday so that release team can cut the same on Tuesdays 14:24:03 That means all reviews to be done by Friday and keeping Monday for gate, last minute additions, etc. reviews 14:24:17 Thanks! 14:24:23 #info Announcements 14:24:56 1) Should we cancle the mid-cycle or there's last minute interest developed? Last time I checked there were 4 who were almost confirmed. 14:25:09 * nikhil waits for feedback 14:25:31 things have changed slightly here. i don't know that i could get approved anymore. 14:25:36 unfortunately I won't be able to come :( 14:25:43 same here 14:26:00 by "cancel" i assume you mean "make into a virtual meeting" ? 14:26:11 right 14:26:36 rosmaita: surely. but the plan is to have regular (~monthly) virtual meetings so, not exactly substitution. 14:27:12 I was going to propose a virtual one right after newton 1 14:27:30 and the one after can be around our midcycle dates. 14:27:36 works for me 14:27:57 +1 to virtual only 14:28:08 Atleast for a few things, so that we're not proposing another 4 hour slots everytime. 14:28:19 ok, thanks all. 14:28:42 #agreed Glance midcycle meetup to be cancelled cc/ sabari 14:28:55 #info Priorities 14:29:22 I started a WIP review last week but due to ML discussions it is in delay. 14:29:31 here's a patch up: 14:29:36 #link https://review.openstack.org/#/c/315752/ 14:30:09 I've also sent announcement email on the priorities and processes. Will be taking that into account before this is final. 14:30:36 Good points brought up by a few people over last few weeks, something that's been communicated in different threads: 14:30:53 Side-priorities (in Mitaka it was called priorities w/o clear plan) 14:30:54 nikhil: just curious about Glare there 14:31:11 Elements that will need more baby sitting, are non-controvertial and less research or dependencies. 14:31:27 They should be considered side-priorities. 14:31:46 I think we have to say several words about artifacts in this doc, right? 14:31:57 Currently, we've Glare, registry and v1 deprecation and part of categorization effort. Also, we should include lite-specs. 14:32:24 mfedosin: correct, this is all as per what we agreed at the summit. 14:32:29 can we document them as well? 14:32:35 mfedosin: the more info we can provide the better it will be. 14:33:02 also I think we must include sudipto in Nova v1-v2 work 14:33:18 hemanthm: yes, I plan to include as much info on that review. you can provide feedback on gerrit while we work on them collaboratively. BUT we need to stay very close to what has been agreed at the summit. 14:33:28 nikhil: currently only me, you and flaper87 are listed there 14:33:31 nikhil: +1 14:33:39 mfedosin: noted 14:34:04 mfedosin: you not giving me any cake for all my reviews on your spec ;-) (jk) 14:34:19 anything else? 14:34:40 moving on, then.. 14:34:48 #topic Lite-specs process finalizing 14:34:49 nick-ma: in Barselona 14:34:59 *nikhil: 14:35:39 mfedosin: ? 14:35:57 mfedosin: if not on lite-specs we need to discuss later. running short of time atm. 14:36:03 nikhil, guess he means the cake. :) 14:36:27 sudipto: mfedosin : gotcha. I am looking forward to it. you said it now ;) 14:36:34 sudipto: correct :) 14:36:37 #link https://review.openstack.org/#/c/315339/ 14:36:41 there was lots of good comments in the review for lite-spec doc change 14:36:50 yes, thanks! 14:37:01 So, we need the following: 14:37:13 1) use-case, very good problem statement 14:37:31 2) all the affected domains (notification, security, operator, end user, etc) 14:37:48 if we're using the same template, it's quite self explanary 14:37:54 3) scope of the implementation, hurdles or any workarounds that we need to do 14:38:28 As of current proposal by flaper87 , there's no enforcement on using that template. 14:38:45 I think that was implied 14:38:56 there's loose coupling with what we need and what's expected. 14:39:08 use the template for the content on the commit message 14:39:33 I did read that ... I'd like to see us enforcing renos and proper commit messages before we agree using them as lite-specs 14:39:53 #action all interested on lite-specs: please explicitly state what your thougts are on the proposal(s) 14:39:53 no-one is writing them currently 14:39:59 ok, good point jokke_ 14:40:01 ok 14:40:15 I am also in favor of reno and cm only 14:40:23 let's make sure that we get that in the reviewer's guide 14:40:30 we don't have enough review bandwidth for specs 14:40:30 I don't mind as long as: 14:40:31 although I'm not sure if we can drop indexing like flaper87 mentioned in his latest comment 14:40:36 1) they are discoverable 14:40:49 2) they can be used for referencing outside of glance or code 14:41:12 3) people won't have to click on 15 pages underneath the doc page to look for them 14:41:29 we're getting a lot of heat on documentation so we need to ensure we increase docs at least two folds 14:42:01 kairat: having them in specs makes us aware of the review bandwidth we can commit to them in a cycle 14:42:34 the point I'm tring to make is we get specs and lite-specs done first in cycle (before 15th June on soft freeze and early July on hard freeze) 14:42:45 that's the second problem there ... the drivers to move lite-specs to the glance-specs repo were following: 1) no-one is writing the renos 2) we need to document out new features at least somewhere where they are all easily findable 3) amendments to the old specs like Niall's deactivation stuff 14:42:48 that way we know what's in the pipe and what we can actually tackle 14:43:44 yes bandwith planning was the number 4 14:43:52 with what flaper87 proposed, we don't have to do spec reviews separately for lite-specs 14:43:55 Hmm, I am not sure review for specs will give us enough info about planning 14:44:12 because usually it just doubles review time for me 14:44:16 will describe that in spec 14:44:21 but we don't know how much we need to review and how much we can ignore in a cycle 14:44:44 I don't want proposers thinking and pushing before newton-3 that it's possible for them to propose something and get it merged 14:44:57 we need a way to avoid many behavior changes in one cycle 14:45:05 and we need to do that early 14:45:09 +1 14:45:25 ok, we can keep this discussion going on the review 14:45:34 I guess having the lite-spec and code in the same commit doesn't help with planning much 14:45:50 right 14:45:55 So, there are good points raised here, please make sure you jot them down completely on that review patch. 14:45:56 sure I retype my points there as gerrit was so nice and wiped my last round earlier today 14:46:08 (please do not be implicit) 14:46:46 ok, moving on for now. 14:47:10 #topic Codec can't encode characters 14:47:17 #link https://review.openstack.org/#/c/316054/ 14:47:28 dshakhray: floor is yours 14:47:30 okay, it's dshakhray's fix 14:47:54 I thinks she wants you to review the code 14:48:24 k 14:48:37 yes, only review) 14:48:39 headers were encoded in HTTPclient 14:49:07 but when we started to use SessionClient they are not 14:49:20 so Darja fixed it :) 14:49:33 cool 14:49:45 let's get that reviewed then 14:50:04 #topic open discussion 14:50:18 there's another request for review here: 14:50:18 I wanted to ask one thing... 14:50:23 Return request-id to caller 14:50:31 dshakhray: change itself seems to make sense. Please be bit more verbal on the commit message. Currently the commit message and the change are not telling the same story 14:50:38 hi, need reviews for return request id to caller, have proposed two solutions, https://review.openstack.org/#/c/261288/ and https://review.openstack.org/#/c/316052/ 14:50:45 https://review.openstack.org/#/c/261288/ 14:50:46 https://review.openstack.org/#/c/316052/ 14:51:00 2nd one is proposed by Brant and Cao, please provide your feedback on it as per time permits 14:51:03 +1 to jokke_ on commit message 14:51:14 mfedosin: please go ahead 14:51:32 in Nova for some deployments we have to enable show_multiple_locations 14:52:07 and if you read message from Heat in ML they always need it to use Glance v2 14:52:17 abhishek: do those overlap with 7150ceee1ac72361f75b3a4187e10a884166870d that I noticed had been merged lately 14:52:19 well 14:52:27 but this option has a vulnerability 14:52:51 jokke_: let me have a look 14:53:24 mfedosin: for long term this is what we want to do https://review.openstack.org/#/c/313936/ 14:53:35 so, I propose to change image_location_quota default from 10 to 1 14:53:57 nikhil: doesn't matter 14:54:04 that does reduce it a bit 14:54:17 for Heat and Nova we have to allow to set custom locations for all users 14:54:35 that is really really problematic 14:54:46 mfedosin: I don't know why we need to allow for all users 14:54:47 mfedosin, it may break some templates after glance upgrade 14:54:52 jokke_: could you please provide a link 14:55:16 nikhil: to make snapshot, for example 14:55:16 the whole locations code is really really problematic as long as we do not have service tokens 14:55:26 if this option is disabled... 14:55:31 abhishek: I don't have one ... that's commit id from glanceclient git log 14:56:09 jokke: ok I will have a look and let you know 14:56:23 Here is one situation: Heat want to use Glance v2 instead of v1. But we can't set locations as v1 did by default. 14:56:23 this won't work https://github.com/openstack/nova/blob/824c3706a3ea691781f4fcc4453881517a9e1c55/nova/virt/libvirt/imagebackend.py#L967 14:56:39 https://github.com/openstack/nova/blob/824c3706a3ea691781f4fcc4453881517a9e1c55/nova/virt/libvirt/driver.py#L1517 14:56:43 mfedosin: are you saying that currently every deployment is changing that locations option on? 14:56:49 mfedosin: I thought that driver was already using v2 and image locations ? 14:56:56 yes, because it uses v1 14:57:10 no, it uses v1 to set location 14:57:11 mfedosin: and our scope should not increase beyond that driver 14:57:13 wxy, thanks, i forgot about that 14:57:28 mfedosin: nova folks need to be more aware apparently 14:57:31 mfedosin: ok 14:57:34 Heat team want to upgrade to v2 14:57:42 wxy: I am aware of that 14:57:56 wxy: and I have responded very clearly. but no response back ! 14:58:16 nikhil: ++ 14:58:20 so, reducing this parameter from 10 to 1 will prevent a lot of bad issues 14:58:46 mfedosin: so for the 'lot' part, please start a email thread with the glance-core-sec for now 14:58:54 mfedosin: we can then involve people who have more to say 14:59:14 ikay 14:59:16 okay 14:59:21 rosmaita: you got a min 14:59:22 2min 14:59:28 1 left :P 14:59:32 more like 30 sec 14:59:37 :) 14:59:39 type faster 14:59:47 have a nice day, everyone 14:59:54 TravT: is generous in not kicking us out :) 14:59:55 i will bug people individually in glance channel 15:00:04 ok 15:00:07 :) 15:00:07 Thanks all! 15:00:14 thanks 15:00:19 thanks all 15:00:20 #endmeeting