14:00:09 #startmeeting glance 14:00:10 Meeting started Thu Oct 6 14:00:09 2016 UTC and is due to finish in 60 minutes. The chair is rosmaita. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:12 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:12 o/ 14:00:15 The meeting name has been set to 'glance' 14:00:22 #topic roll call 14:00:29 o/ 14:00:36 * sigmavirus was pre-on-topic 14:00:38 o/ 14:00:39 o/ 14:00:54 o/ 14:00:57 \o 14:01:07 o/ 14:01:09 o/ 14:01:33 looks like a decent turnout, hello everyone! 14:01:44 #topic agenda 14:01:46 #link https://etherpad.openstack.org/p/glance-team-meeting-agenda 14:02:00 #topic updates 14:02:50 #topic import refactor 14:03:07 we had the first recurring sync on tuesday 14:03:23 turns out that the meetbot is in the glance channel, so for those who want to follow along: 14:03:37 #link http://eavesdrop.openstack.org/meetings/image_import_sync/ 14:03:56 o/ 14:04:11 currently we're looking over the MVP proposal and some patches 14:04:50 and we're doing a followup meeting tomorrow at 13:30 utc 14:05:01 but will mostly stick with the tuesday syncs 14:05:22 key point is, things are moving 14:05:33 #topic community images 14:06:09 reviews, please 14:06:35 so for the first patchset, both stevelle and abashmak have provided great feedback. i believe that i've addressed all of it save for one point that i'll do today (making a new error string easier to i18n). 14:06:56 excellent 14:07:34 the second patchset that utilizes the new values is at the point where i'm going through individual tests to figure out how to best allow them to work with, for example, the fact that private + members doesn't "work like that" anymore. this may not be a quick process but progress is being made. 14:07:38 that's all i have. 14:07:52 we can talk about the is_public=false -> viz=shared at tomorrow's sync 14:07:59 great 14:08:07 thanks 14:08:22 new update topic 14:08:30 #topic rolling upgrades 14:08:45 hemanthm and abashmak have been working on this pretty steadily 14:09:01 and one of them would like to say something now 14:09:01 The updated RLGUPG DB strategy spec has been waiting for reviews 14:09:09 https://review.openstack.org/#/c/331740/ 14:09:17 This spec proposes triggers utilization 14:09:36 To facilitate RLGUPG, we have another spec for moving migrations to Alembic: 14:09:46 https://review.openstack.org/#/c/374278/ 14:09:55 Would be good to see some reviews there 14:10:21 And there is a new PS from hemanthm to make the switch from SQLAlchemy-migrate to Alembic 14:10:32 https://review.openstack.org/#/c/382958/ 14:10:59 Hemanth and I have been working towards a POC demonstrating RLGUPG. 14:10:59 Expand and Contract Alembic scripts are ready (holding off on the PS for now) 14:10:59 MySQL triggers are ready: 14:10:59 http://paste.openstack.org/show/584520/ 14:10:59 The Keystone team has looked at and consulted on the triggers. 14:11:25 Currently waiting for community images use case to mature 14:11:46 We'd need at least the first PS from Timothy to merge and the 2nd one in a workable state 14:11:56 So we can cherry pick and install it as 'N' service to test rolling upgrade from ‘N-1’ 14:12:08 That's all I have 14:12:19 thanks, and that brings us to another new update topic 14:12:26 #topic Core Awareness 14:12:40 ok, i want to be explicit about what our priorities are right now 14:12:44 I like the sound of it :) 14:12:53 no, explicit is bad :P 14:13:05 * rosmaita ignores sigmavirus 14:13:11 (That's always a good idea) 14:13:43 we need reviews on the rolling upgrade stuff ... there are a lot of comments on the spec, but mostly from non-glance 14:14:02 and we need reviews of the switch to alembic to make sure we are all on the same page, community-wise 14:14:41 and, we need reviews of the community images work, because that is important, but also because the sooner it merges, the sooner the rolling upgrades stuff can be completed 14:14:45 so 14:15:06 anyone not working on image import right now, please spend some time reviewing the patches discussed above 14:15:20 any questions? 14:15:59 is that for the entire cycle? 14:16:10 no, for the next two weeks 14:16:13 what does "right now" mean ... every week? 14:16:26 ok thanks 14:16:34 ok, more explicitness 14:16:44 rosmaita: be more explicityyyy 14:17:01 croelandt Jokke_ rosmaita are working on image import right now 14:17:14 so croelandt and Jokke_ will be focused on that 14:17:20 * Jokke_ goes and picks up some popcorn, this is fun :) 14:17:38 all other cores, i request that you look at the rolling upgrades and community images patches 14:18:02 except for security bugs, those are our #1 priorities 14:18:10 * sigmavirus looks 14:18:30 further priorities will be determined at the design summit (or around that time, depending on attendance) 14:18:56 but we know we want to do import, community images, and rolling upgrades, so we don't need to wait 14:19:27 I won't be at the summit, but I'd strongly urge those attending to pick very small goals for additional goals that the community talks about 14:19:39 good point 14:19:40 These three are large and achievable but only if we don't have another 3 large ones :P 14:19:49 ++ sigmavirus 14:20:05 We can only split our focus so much =/ 14:20:20 my plan is to put up a priorities patch to ocata specs during the summit 14:20:25 and we can discuss on the patch 14:20:30 SGTM 14:20:40 cool 14:20:48 ok, any other questions? 14:21:02 Yes, that would be great. Smaller, additional goals to work on. 14:21:08 do we have any expected milestones yet for the priorities? 14:21:25 I'd assume we would like to get community images in at least by O-1 14:21:44 actually, it would be good to have community images close to done by summit time 14:21:50 ++ 14:22:01 but there is no milestone before summit :P 14:22:05 tsymanczyk has been working hard, and it's pretty close 14:22:12 just a personal milestone 14:22:17 so, do we want to get community images merged first and then make it rolling upgrade-able? 14:22:30 we can have glance-milestones 14:22:39 hemanthm: yes, i think so 14:22:52 but that's subject to change if some kind of weird edge case is a blocker 14:23:02 I'd say out of these big ones, we really want to have the community images in asap and not delay it by any other work that might be overlapping 14:23:17 Jokke_: i agree 14:23:19 +1 14:23:22 it's very very close to be done and would be shame to put that into limbo 14:23:37 ok, time for more explicitness! 14:23:48 reviewers: look at commuinity images first 14:23:59 but also keep the rolling upgrade stuff in mind 14:24:03 getting community images done before the summit really would be best. i'm not sure how much time i'll have to work on it come november. i'm trying to address feedback ASAP after its posted. 14:24:23 tsymanczyk: good point 14:24:43 unfortunately for the second changeset there's no real way forward beyond me adjusting the old unit tests one by one to be cool with the new behaviour. 14:24:50 but that's on me and i'll take care of it. 14:24:58 i think if we as a community concentrate, we can land this soon 14:25:23 any other questions, comments? 14:25:48 Not sure if this is appropriate, but I can help with the unit tests or anything for the community images if required. 14:25:58 dharinic: very appropriate! 14:26:27 dharinic: and highly appreciated. Talk to tsymanczyk ;) 14:26:30 dharinic: community images sync is tomorrow at 11 central time 14:26:32 awesome. Will get in touch with tsymanczyk :) 14:26:38 thanks! 14:26:45 any and all help is deeply appreciated. 14:26:54 this has been going on long enough. 14:26:55 great. 14:27:21 ok, let's close that discussion on a high note 14:27:33 #topic first PTG coming up 14:27:55 the PTG is the "project team gathering" 14:28:03 it's intended to replace midcycles 14:28:06 http://www.openstack.org/ptg 14:28:29 it's in Atlanta, Georgia, USA, February 20-24, 2017 14:29:04 so, as we can see by the sparse attendance, Barcelona hasn't been a travel priority for many of our employers/sponsors 14:29:28 so i want to give you a heads up to start talking to your managers about the PTG 14:29:55 (Doesn't help that PTG often means the Project Team Guide too in OS) 14:30:05 because it would be nice to have good attendance there so we can meet face to face 14:30:18 sigmavirus: duelling acronyms 14:30:23 Acronyms 14:30:26 3 14:30:28 rosmaita: also faces are overrated 14:30:37 sigmavirus: speak for yourself! 14:30:38 maybe we should namespace our acronyms 14:30:51 stevelle: The TC organizes both so that won't work 14:30:52 :/ 14:30:53 stevelle: and then namespace the namespaces 14:31:00 rosmaita: gets it 14:31:01 I guess the foundation organizes the gathering 14:31:01 id 14:31:24 just want to drop a quote in here from the organizers aobut the structure of the PTG meeting 14:31:38 "Horizontal teams (Infrastructure, Documentation, QA...) and cross-project workgroups will meet on Monday-Tuesday (Monday optional). Vertical teams (Nova, Cinder, Swift...) will meet on Wednesday-Friday (Friday optional). Teams that fall in between (Packaging, Kolla, Horizon...) might be placed with horizontal or vertical teams, depending on room availability. Attendees will be encouraged to pick one horizontal effort and one vertical team an 14:31:50 sigmavirus: we could start talking about openstack.events.ptg and openstack.docs.ptg 14:32:08 nah, openstack.tc.ptg 14:32:18 yes, please make sure your managers are willing to send you to events.ptg, not docs.ptg 14:32:28 and then the docs folks need to refer their specific part of the gathering as openstack.events.ptg.docs where they talk about openstack.docs.ptg ;) 14:33:02 events.ptg.glance::priorities 14:33:07 anyway 14:33:09 moving along 14:33:17 anyway, my point is ... please start talking to your managers 14:33:23 the TPG is supposed to be informal 14:33:35 but, if your managers say you need to be presenting or something 14:33:51 we will "formalize" the glance design sessions so that you can present something 14:34:37 i just want to get an early start on figuring out how to make this work so we can get a large turnout 14:35:05 that's all about that from me, any questions? 14:35:10 TPG is better than PTG :) 14:35:15 openstack.events.ptg.glance.formal. :P 14:35:19 * Jokke_ stops 14:35:38 * stevelle 's work here is done 14:36:02 definitely a lively meeting today 14:36:14 #topic cross project liasons followup 14:36:52 just a reminder, any current c-p liasons, review whether you still want to do it, and next week i'd like to open things up 14:37:03 #link https://wiki.openstack.org/wiki/CrossProjectLiaisons 14:37:35 * sigmavirus needs to update the release liaison 14:37:40 is flaper87 still our oslo liaison? 14:38:00 possibly, i'm not completely sure 14:38:16 i was going to discuss with him at the summit 14:38:41 so most likely, now that i think aobut it, we'll open things up for new c-p liasons after the summit 14:38:56 that way i can speak with all the current people and assess interest/time commitments 14:39:19 rosmaita: how about before summit and we can finalize them in the team meetup we have Fri afternoon? 14:39:37 Jokke_: ++ 14:39:50 * sigmavirus added himself for relmgt since I've already started doing that work 14:40:11 ok, that's a good suggestion 14:40:15 Jokke_: do you want to be stable branch liaison? 14:40:27 * sigmavirus was supposed to be it but I keep managing to not find the meeting 14:40:45 i will send out an email to the current people explicitly asking about their commitments 14:41:02 and maybe we can work on it at the friday meetup 14:41:11 sigmavirus: likely could. I'll think about it 14:41:18 * sigmavirus adds himself as a stand-in fo rnow 14:41:22 speaking of which ... of the people going to barcelona, how many will be available for the friday afternoon meetup? 14:41:32 o/ 14:41:36 o/ 14:41:38 will be 14:42:12 so 3 of us ... lets find a good pub for it :D 14:42:21 see, that's what i'm worried about 14:42:24 not the drinking 14:42:29 jsut the light attendance 14:42:46 so, next topic: 14:42:51 #topic design summit 14:42:59 i haven't finalized things yet 14:43:08 am waiting to see the cross project topics announced 14:43:24 because i think rolling upgrades will be covered there 14:43:39 plus, hemanthm and abashmak , who are leading the glance effort, won't be there 14:44:10 the rolling upgrades, and the move away from sqlalchemy-migrate to alembic is really importnat for glance 14:44:16 hemanthm won't be in the summit? :o 14:45:14 i think we'll need to have a virtual summit (we can call it something else) for hemanthm and abashmak to present their work 14:45:44 i want to make sure the glance community understands/is committed to the direction this effort is taking 14:46:02 probably the best time for this would be after the physical summit 14:46:17 we'll talk more later 14:46:19 yeah ... /me has bit of holes on the above 14:46:48 I have ditches :) 14:46:57 agreed, i think we need a question/answer session 14:47:09 so we'll need to think about video communication tools 14:47:28 Jokke_: no, I'm not super important at Rackspace 14:47:51 Jokke_: hemanthm is super important, he just flies under the radar 14:47:54 Aren't hackers supposed to be good atr written communication? :p 14:48:01 rosmaita: I can still provide bluejeans 14:48:12 Jokke_: I'd rather brownslacks 14:48:14 hemanthm: that's shame :( 14:48:37 hemanthm: I was looking forward to have few (kegs) beers with ye 14:48:41 Jokke_: ok, i'd like to set up a test or something 14:48:47 of bluejeans, not beers 14:48:57 suuurrreeeee rosmaita 14:48:58 Jokke_: same here :) 14:49:09 i coulnd't hear mike very well in bluejeans last time 14:49:24 but he was in russia, you were in ireland i think, and i was in usa 14:49:54 anyway, we'll discuss video tools at another meeting 14:50:17 ok, one last topic before open discussion 14:50:23 #topic TC election 14:50:35 just a note that the TC election is closing soon 14:50:57 you should have received an email with a link to the election site 14:51:27 ok, that's it from me 14:51:33 #topic open discussion 14:53:22 so that much to our video conferencing ... I think Vidyo has been fine apart from it tends to be well blocked from corp firewalls (at least that was the case in HPE), BlueJeans seems to work very well on good day, normally it's doable ... the WebEx is just something you can forget having me on :P 14:53:46 Jokke_: i agree about the WebEx thing, that wasn't very good 14:54:03 All these tools require non-free software on the user's PC, right? :p 14:54:13 croelandt: i believe so 14:54:20 some teams use google hangouts 14:54:42 but i believe the community kind of frowns on it becasue not all google stuff is available in china 14:54:49 (though i am not 100% sure about that) 14:54:50 iirc BlueJeans works (or are working towards) being just webrtc or what ever that open standard is 14:54:53 afaik hangouts licenses the tech from Vidyo 14:55:09 rosmaita: nice for Free Software hackers :) 14:55:24 problem with hangouts on any work is the very limited attendee number 14:55:38 Jokke_: good point 14:55:42 if you have any chance to have more than 10 people participating, just forget about it 14:56:12 what i'd like to do is to have a test mabye during the open discussion at the next meeting 14:56:16 croelandt: google, open ... 14:56:21 next few meetings 14:56:24 one tool per meeting 14:56:46 if we could have a person from each continent on the tool, we'd be able to get some feedback 14:56:59 lets just keep our meetings as meetings and have these test runs out of meeting band 14:57:21 well, i was thinking the meeting is a time when the entire community should be available 14:57:28 it's always more than couple of minutes of hassle to get folks joining to a different meeting tool 14:57:29 otherwise, it may be hard to find a time 14:57:35 Jokke_: good point 14:57:54 Jokke_: what if that's on meeting agenda :) 14:58:02 and we can expect some having issues no matter what platform we are using if the attendees spans across the globe 14:58:28 ok, we may have to think about this some more 14:58:38 any other topics on anyone's mind? 14:58:44 1.5 min left 14:59:35 30 sec 14:59:57 Thanks all! 14:59:58 ok, i guess that's about all for Glance this week ... thanks, everyone! 15:00:06 #endmeeting