13:59:48 #startmeeting Glance 13:59:49 Meeting started Thu Mar 24 13:59:48 2016 UTC and is due to finish in 60 minutes. The chair is flaper87. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:59:51 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:59:53 The meeting name has been set to 'glance' 14:00:04 o/ 14:00:05 #topic agenda 14:00:06 #link https://etherpad.openstack.org/p/glance-team-meeting-agenda 14:00:07 o/ 14:00:10 o/ 14:00:38 o/ 14:00:41 o/ 14:01:06 ok, let's kick this off! 14:01:18 #topic Updates Glare 14:01:21 o/ 14:01:23 o/ 14:01:34 o/ 14:01:40 mfedosin: floor is yours 14:01:42 :) 14:01:44 just in time 14:02:16 so, what was done in last week... 14:02:29 we created several patches 14:02:37 1. Policy support 14:02:44 2. Notification support 14:03:06 3. DB layer for Glare 14:03:29 4. FaultWrapper middleware 14:03:41 5. Functional tests for Image Artifact type 14:04:03 it will be merged with the existing code today 14:04:26 What's going to be merged? 14:04:30 also we had a long chat with app-catalog yesterday 14:04:53 Is that changing the API? I thought that work depended on the spec being approved 14:04:54 flaper87: these 5 patches with Glare All-in-one patch 14:05:19 flaper87: don't worry :) 14:05:19 mfedosin: can those be kept separate instead of having a single huge patch? 14:05:40 flaper87: it's hard to develop if they're separated 14:06:05 when it is ready we will split the code in small patches 14:06:20 that are more confortable for review 14:06:24 mfedosin: sounds good 14:06:27 thanks 14:06:28 :) 14:06:31 anything else? 14:06:31 but now we have all code in one place 14:06:57 I think it's all we have 14:07:10 cool! thanks a bunch 14:07:19 #topic Updates Cross Project 14:07:22 nikhil: o/ 14:07:32 yo 14:07:47 THe process of cleaning up stale specs has begun 14:08:19 So, if you'd liked a spec and need it seen in cross prj, please consider adding comments, updating patch etc. 14:08:34 all of them in openstack/cross-project-specs 14:08:51 besides that 14:09:14 I'd sent a email regarding quotas and asking for feedback last week 14:09:35 I've had a great number of responses and varied use cases 14:09:55 that sort of helps gauge the openstack community perspective and set a soft direction 14:09:56 Is the convo leaning towards a separate service? 14:10:02 no 14:10:18 When I started contributing to Glance, that was the current state of mind (Boson) 14:10:20 it's leaning towards a library backed with DB model 14:10:21 or something like that 14:10:29 sounds good 14:10:45 more maintainable and scalable 14:10:49 here's a good summary 14:10:50 http://www.openstack.org/blog/2016/03/openstack-developer-mailing-list-digest-20160318/ 14:11:00 (I think it directly links it) 14:11:12 coolio! 14:11:16 Anything else? 14:11:21 We'd have some more emails today 14:11:22 yes 14:11:27 one more thing 14:11:52 there's a email thread on "what are specifications?" 14:12:02 people should read and comment on it 14:12:14 ++ 14:12:20 * nikhil done 14:12:26 Thanks for the heads up! Folks ^ 14:12:34 okidoki! 14:12:45 #topic Oslo CPL (Call for volunteers) 14:12:50 #link http://lists.openstack.org/pipermail/openstack-dev/2016-March/090092.html 14:13:06 Just a heads up! There's a calls for volunteers for the Oslo CPL role 14:13:33 If you feel like you have time to do it, please step up 14:13:49 * sigmavirus24 apologizes for being late 14:13:53 It doesn't take much time other than raising issues to the oslo team when things happen 14:13:59 or bringing oslo feedback to this meeting 14:14:00 etc 14:14:14 Attending Oslo meetings (On Monday) would be recommended 14:14:24 that's it 14:14:40 #topic Glance Newton Priorities 14:14:54 #link http://specs.openstack.org/openstack/glance-specs/priorities/mitaka-priorities.html 14:15:17 That's our list of Mitaka priorities 14:15:29 I've created this etherpad for us to start drafting what newto nshould look like: https://etherpad.openstack.org/p/glance-newton-priorities 14:15:38 I'll put some content in it in a bit 14:15:57 TBH, I believe the priorities shouldn't shift from what they were in Mitaka. Not much, at least. 14:16:12 1. Deprecate v1 14:16:15 Image import refactor and Nova v1 -> v2 should be kept as top prio 14:16:23 ++ 14:16:29 +1 14:16:33 The rest should be "nice to have" 14:16:34 ++ 14:16:57 I'll keep an eye on that ehterpad but I'll start drafting the priorities spec for newton 14:16:59 I also want to see Glare in prioritis 14:17:01 so we can comment on it 14:17:18 yep 14:17:23 let's start working on etherpad 14:17:40 I think everyone undoubtedly agrees on Nova v1/v2 and import stuff 14:17:41 #link https://etherpad.openstack.org/p/glance-newton-priorities 14:18:11 the problems within the community are always beyond the obvious 14:18:16 Just as a reminder for everyone: The priorities list should be kept small 14:18:38 2 to 3 items top that are critical for the project 14:18:46 This doesn't mean other things can't be implemented 14:19:03 As I explained at the beginning of mitaka, other specs can (and likely will) be approved 14:19:26 The important bit is that the work not considered priority mustn't conflict with the priorities of the cycle 14:19:39 flaper87: agree - priorities are not nice-to-have things, they are essential 14:20:18 ok, anything else? Questions ? 14:20:50 #topic Glance Summit Sessions 14:20:53 ooooook 14:20:56 lets continue this on the etherpad/spec review 14:21:10 not the summit sessions obviously :P 14:21:12 As promised, I think we should start discussing the summit sessions 14:21:27 jokke_: summit sessions too, I think :) 14:21:30 I'll start some of these discussions and the upcoming PTL will likely take over 14:21:47 #info PTL voting closes today at 23:59 UTC 14:22:17 The reason I believe we should start discussing some of these topics here is that, apparently, no one is paying much attention to the etherpad and some topics need some clarifications 14:22:24 etherpad is a terrible messaging tool 14:22:57 So, I'll try to go in order (unless people have a better suggestion) 14:23:03 should we start tracking summit session proposals in the specs-repo as well? 14:23:12 please no 14:23:14 hahahaha 14:23:17 :P 14:23:28 it would get us rid of the etherpad comms issues 14:23:33 flaper87: surely, go ahead 14:23:35 Proposal #3 Title: Glare v1 API 14:23:41 probably should encourage specs for the ones that attract some interest 14:23:53 (I'm skipping the ones that have a description and folks have chimed in) 14:24:02 mfedosin: what do you want to talk about in this session? 14:24:07 is it going to be a demo? 14:24:12 do you plan to discuss the new API? 14:24:12 sure 14:24:14 flaper87: mind to drop the EP link again 14:24:21 #link https://etherpad.openstack.org/p/newton-glance-summit-planning 14:24:23 jokke_: ^ 14:24:42 mfedosin: it'd be interesting to have a description written on the etherpad 14:25:02 will be doen 14:25:07 sorry :) 14:25:18 ok 14:25:26 Proposal #4 Title: Deprecating v1 API 14:25:37 mfedosin: ditto. Is this about Nova v1->v2? 14:25:44 or is it literally about deprecating v1 ? 14:26:01 A description and a spec would be awesome :D 14:26:08 seems that even without description we all want it 14:26:09 hahahaha 14:26:09 * jokke_ hopes the later 14:26:18 ++ 14:26:30 jokke_: yeah! 14:26:36 mfedosin: same for the compatibility layer 14:26:48 I wanted it to be about v2 adoption in Nova 14:27:09 mfedosin: sounds good! 14:27:20 We can use that as a shared session with folks from Nova 14:27:30 and it will be great 14:27:31 If so, we need to decided asap and let Nova folks know 14:27:38 so we can schedule things accordingly 14:27:46 in that case we can combine deprecation of v1 and compat layer 14:27:56 in on session 14:27:59 ++ 14:28:06 Sounds good! Mind updating the etherpad ? 14:28:17 * flaper87 thinks this discussion has been useful already 14:28:18 :D 14:28:38 Proposal #8 Glance tasks - present, future and the requirements. 14:28:43 nikhil: was that you? 14:28:45 кшпре фаеук ьууештп 14:28:49 yep 14:28:53 right after the meeting 14:28:55 What exactly is it going to be about? 14:29:09 Wondering since we've marked the task API as admin only already 14:29:13 I can update the etherpad too 14:29:16 and we've planned to deprecate it in Newton 14:29:31 The story around what's out there and where it's heading isn't clear to me 14:29:35 I guess my question is: What do we want to talk about as far as the future of this API goes? 14:29:40 ok 14:29:52 The last feedback was 14:29:58 we can't get rid of the HTTP APIs 14:30:09 and we've this public API sitting with some clouds exposing it 14:30:12 Is that something that we could perhaps clarify during the meetup session or even during the Glance meeting? 14:30:33 the TL;DR is: We can deprecate APIs, we're not removing them from the code base, though. 14:30:51 We can make it admin only, mark it as deprecated and advice not to use it ever again 14:30:57 Plus, we can stop supporting it 14:31:14 anyway 14:31:15 that support part is bit strong statement 14:31:26 That's the part is bit confusing 14:31:34 we can either make it admin only or deprecate it 14:31:45 Sure, let's put it as a topic for the next meeting 14:31:47 sounds good? 14:31:50 but admin only is a soft contraint 14:31:53 ++ 14:32:04 constraint* 14:32:07 Just to make sure we discuss it thoroughly and then we can decided if a session is worth it 14:32:27 that should be pretty clear based on the discussions and decisions made in Tokyo + after 14:32:51 flaper87: sounds good 14:33:40 Proposal #9 Glance and Glare image sharing, Glance community images 14:33:53 Is that something that will have an impact on the import refactor? 14:34:05 don't think so 14:34:21 I want to come and discuss it 14:34:31 Did we hear anything more from Symantec about this? 14:34:37 no 14:34:42 I have no final decision on community sharing 14:35:06 They did send a mail to the list a while back. 14:35:14 mmh, who proposed it? 14:35:16 rosmaita: u ? 14:35:21 me 14:35:25 a-ha! 14:35:27 gotcha 14:35:29 i added the descriptioin, though 14:35:30 We need to clear the air on that 14:35:40 there are some discussions around sharing in glare too 14:35:50 and community stuff has been almost implemented 14:35:51 (my interest is making sure the "old" work on this isn't wasted!) 14:35:57 rosmaita: +! 14:35:59 +1 14:36:05 :D 14:36:21 Understood! My worry is that we might endup using the summit to clear the air on several topics that won't be worked on during the cycle, hence all these questions 14:36:38 flaper87: no, it's good to have all the questions out there 14:36:40 Trying to make sure we use the slots for things that are actually going to be worked on 14:36:49 that was my motive to add the topics! 14:36:53 Symantec spec: https://review.openstack.org/#/c/271019/ 14:37:06 flaper87: understood, just floating some proposals to get feedback 14:37:08 let's make sure we use the summit topics to ensure we all are on same page on all the things 14:38:08 I noticed mclaren put the Image Import REfactor 14:38:18 I've ocmmented on the etherpad (Proposal #16) 14:38:28 I'd really advice not having a session on it! 14:38:59 I think if we set some ground rules it could be useful 14:39:02 As I've mentioned before, I'm sure we'll end up discussing the spec from scratch, coming up with a whole new proposal and then we'll be back to where we were before Mitaka 14:39:09 mclaren: thanks for the link, i somehow completely missed that spec 14:39:12 we've set ground rules in the past 14:39:16 That's why I'm skeptical 14:39:17 ;) 14:39:24 that might be sending a) wrong message about where we are on that and b) open can of worms we don't want to have all over the place ;) 14:39:48 I'm with mclaren on this one 14:40:10 i think we should devote a 2 hour session during the Friday workday 14:40:16 it's worth taking the risk than loosing another cycle in noop 14:40:17 an informal session 14:40:26 nikhil: +1 14:40:36 rosmaita: I mentioned that in my comment on the etherpad. 14:40:48 Well, it's not like we have not taken the risk in the past 6 months 14:40:50 flaper87: yeah, just re-emphasizing it 14:40:54 That's my point 14:41:14 If there are things to change in the spec, we can do that in the spec 14:41:19 Ok, let me ask this: 14:41:35 What would be the topics that are going to be discussed during that session? 14:42:11 plan of action, corner cases we need to consider etc 14:42:13 What's the expected output? 14:42:13 for me it's mostly whiteboarding and discussing the challenges & architecture 14:42:41 nikhil: that's what was done in Tokyo and over the last 6 months, FWIW 14:42:59 mclaren: the plan of action is, partly, laid down on the spec already 14:43:16 IF we want to discuss corner cases, we need to list them and keep the discussion on those 14:43:28 flaper87: my chat with few folks in glance community made me realize that there are still unresolved questions on import refactor 14:43:44 same with it's architecture 14:44:18 you mean unresolved questions that haven't been brought up? 14:44:27 There are some that we've discussed over the spec 14:44:29 you 14:44:33 :) 14:44:34 sorry 14:44:43 you're asking me to open a can of worms now! :) 14:45:03 No, I'm asking you to bring those up in the spec or ask the folks that have open questions to do so 14:45:10 sure 14:45:41 TBH, not everyone has read the spec completely (and all etherpads relating to it) 14:45:44 by the way, i have a new patch up about the "message" element: https://review.openstack.org/#/c/296167/ 14:45:50 because we've spent more than 8 months asking these questions and it's a bit annoying to know that now that we almost consider this spec as "almost done" there are still fundamental questions around 14:45:54 yes, thanks rosmaita 14:45:59 I saw that it looks great 14:46:03 rosmaita: saw it and posted one comment. Thanks :) 14:46:06 So, again, my point is: 14:46:10 s/point/question/ 14:46:18 What exactly do we want to discuss there? 14:46:28 Even the exercise of walking through what we have and collectively looking for holes would be useful. 14:46:32 What's the output we expect? 14:46:47 aha moment! :P 14:46:52 can we get those details to the session proposal and continue from there (We're running out of time) 14:47:07 jokke_: +1 14:47:21 Sure, I'll try to add something. 14:47:25 mclaren: mind adding the expected output and specific topics to the session proposal? 14:47:27 cheers! 14:47:27 :) 14:47:28 :D 14:48:05 Proposal #15 Glance rolling upgrades 14:48:10 rosmaita: was that you? 14:48:15 yes 14:48:23 I'm curious to know if you've given this a try 14:48:35 not me personally 14:48:35 I think it's an important topic (hope others think so too) 14:48:56 I do 14:48:57 they have it almost done in Nova, and that's way more complicated than glance 14:48:57 It'd be interesting to gather feedback on the topic and perhaps run some tests 14:49:03 mclaren: w00h00000 14:49:19 mclaren: wait, was that re-rolling upgrades ? 14:49:20 :D 14:49:25 (I was happy to see Abhishek's mail) 14:49:29 pff 14:49:59 Right, I was under the impression that Glance is not really far from supporting r-upgrades 14:50:29 it's not like some work has been done there but it doesn't have an overly complicated architecture 14:51:27 I guess there are no comments 14:51:32 or my internet connection dropped 14:51:40 Anyway, it'd be cool to have some feedback on that 14:51:48 !ping 14:51:49 pong 14:51:53 yay1 14:51:54 ok 14:52:04 #topic Open Discussion 14:52:07 I have not tried nor even looked closely into it so can't say 14:52:23 remember PTL elections close today 14:52:30 Vote if you haven't :) 14:52:41 * jokke_ is always few seconds late before topic change :P 14:52:56 did we skip some session proposals, or did my connection drop? 14:53:08 we skipped some! 14:53:14 rosmaita: flaper87 just went through the very empty ones 14:53:14 There are too many for a single meeting 14:53:17 :D 14:53:21 ok, just checking 14:53:25 :) 14:53:33 We can go through more heated ones next week if there are questions there 14:53:47 * jokke_ likes the fact that we have way too many sessions proposals this time 14:53:58 yes! 14:54:00 * flaper87 loves that 14:54:04 jokke_: you do! o// 14:54:08 That's why I think we should ask all the questions 14:54:41 Also there should be a session about race conditions 14:54:47 ok, I guess there are no open discussion topics today 14:54:49 mfedosin: add it :D 14:54:51 flaper87: how did you come up with your nick? :P 14:54:51 nikhil: I'm not saying I agree with all of them, but this is better situation that truing to figure out topics for last two sessions 2min before deadline 14:54:58 mfedosin: I'd make it HA 14:55:16 nikhil: LOL, It's super easy and it provides way too much information about me 14:55:26 Name+Lastname+BirthYear 14:55:27 :D 14:55:41 I wanted flaper but flaper.com was not available 14:55:48 Nice! (I was missing some info) 14:55:50 It's like the movies when they guess your password :-) 14:55:56 nikhil: for you it is Niko87 14:56:01 mclaren: :) 14:56:01 and people still call me falper because it's dumb to say nicks+numbers outloud 14:56:09 mfedosin: that's almost a russian name 14:56:21 nikhil: u 87 too ? 14:56:23 mfedosin: nikkom87 :) 14:56:29 flaper87: heck yeah! 14:56:32 * flaper87 highfives nikhil 14:56:35 \o 14:56:41 jokke_: :P 14:56:52 ok folks! 14:56:52 jokke_: I've considered nikkom as my website 14:56:58 flaper87: nikhil ++ 14:57:02 but my family will disapprove of it 14:57:11 mfedosin: too 87! 14:57:19 anyways, don't wannna block people 14:57:22 hahaha 14:57:25 nikhil: family approval is way too overrated 14:57:32 jokke_: heh 14:57:39 tty'all next week! Please, add more info to proposals and questions as well 14:57:41 #endmeeting