16:00:33 #startmeeting openstack_ansible_meeting 16:00:34 Meeting started Thu Mar 30 16:00:33 2017 UTC and is due to finish in 60 minutes. The chair is asettle. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:36 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:39 The meeting name has been set to 'openstack_ansible_meeting' 16:00:46 yay 16:00:47 o/ 16:00:53 o/ 16:00:58 Good job team 16:01:02 \o/ 16:01:11 o/ 16:01:14 Love to see you all here :) 16:01:15 https://media.giphy.com/media/14urMYvFxIKEms/giphy.gif 16:01:19 o/ 16:01:20 Oh c'mon gif 16:02:09 #topic Roll call (just so we have it, although thanks everyone for already doing it) 16:02:15 Omg I made that the whole topic hAHHAHAHAHAHAHAH 16:02:17 *head desk* 16:02:24 odyssey4me: I hear you, but I don't see you. 16:02:28 o/ 16:02:59 yes yes we get you andymccr :p 16:03:15 I'll give it 2 more mins before we kick off the fun 16:03:26 o/ 16:04:10 o/ 16:04:13 jmccrory: bout time 16:04:17 slacker 16:04:22 Where is logan- 16:04:25 * asettle taps foot 16:04:32 o/ 16:04:34 hahah 16:04:39 :D 16:04:41 That's right logan- 16:04:51 odyssey4me: bro I see you typing commit messages. 16:05:03 Okay let's rock it 16:05:05 #topic Review action items from last week 16:05:12 andymccr: did we have any? 16:05:17 There's none in the agenda. 16:05:25 i was out for the last 2 meetings 16:05:28 so im guessing no :) 16:05:31 Beautiful 16:05:41 *dusts off hands* 16:05:45 #topic Operations guide requires review 16:05:47 I think there was none 16:05:51 #link http://docs.openstack.org/developer/openstack-ansible/draft-operations-guide/index.html 16:05:54 Yo homies, all review 16:06:03 #action OSA TEAM TO REVIEW OR ALEX WILL BE UPSET 16:06:07 Good action 16:06:10 asettle: didn't we have some offers to do that last time? 16:06:14 well it would've been 3 meetings ago 16:06:27 we should track that - i think people usually just need a prod to say "hey you were interested is that still the case here" 16:06:36 well we skipped that part on previous meeting 16:06:47 but I think this deserves # actions items 16:07:05 evrardjp: make it so 16:07:06 #action evrardjp work on the firewll for ops guide 16:07:11 Gracias evrardjp :) 16:07:12 haha already one :p 16:08:10 andymccr: you want to go back to action items yo 16:08:16 yeah sorry i checked the logs 16:08:19 *tsk* 16:08:24 i know im terrible 16:08:31 #action Andy to actually update the meeting agenda each week 16:08:58 hahaha 16:08:59 yes yes 16:09:06 we had 2 action items 16:09:09 1 was to unblock the gate 16:09:17 AFAIK this is a big tick - so thank you everybody for that help 16:09:25 https://media.giphy.com/media/xb8zoHFCKU0Ra/giphy.gif 16:09:25 if that isn't the case let me know. 16:10:01 we have another action item which is for me to look into getting an onboarding room at the summit - i need to do that still 16:10:02 so 16:10:12 #action andymccr to look into getting an on-boarding room at the summit (carry-over) 16:10:22 You can get a lunch room, email Kendal andymccr 16:10:24 Kendall* 16:10:33 On the dev list 16:10:36 sweet nice tip :) 16:10:42 and 2 other action items 16:10:43 Try for Thursday if possible, so I can help:) 16:10:53 spotz: awesome will do - and thanks for the offer! 16:10:55 Good idea :) 16:11:02 so last 2 action items: review https://review.openstack.org/#/c/445334/ 16:11:05 thats another tick since its merged :P 16:11:22 http://quotesblog.net/wp-content/uploads/2015/05/PuW18jf.gif 16:11:25 and one more which is a carry over 16:11:27 Oh c'mon gif 16:11:38 We'll go back to this since it worked: https://media.giphy.com/media/xb8zoHFCKU0Ra/giphy.gif 16:11:42 #action review https://review.openstack.org/#/c/447151 and talk about shared "osa community goals" for network integration best practices next week (useful for trove and octavia) 16:11:59 xgerman: have you spoken with kylek3h and some of the other people working on the trove role - if there is link over there? 16:12:14 we discussed it last week 16:12:14 ahh i see kylek3h is on that review already :) so magic is happening 16:12:26 at the meeting 16:12:29 :) 16:12:34 sweet :) xgerman do we need to talk more about that this week? 16:12:36 though reviews have been slow after last week 16:12:43 ok cool so another prod to get some reviews in 16:12:48 yep 16:13:02 https://encrypted-tbn2.gstatic.com/images?q=tbn:ANd9GcT_PRvH1I6k2uI8IGJNdrVvGg0dAkRRs5bpZcyvsRgL9jb_d_kcyg 16:13:04 Omg wh 16:13:08 ok so that is all the action items i believe 16:13:23 https://media.giphy.com/media/m80Q4HTDNPFHq/giphy.gif 16:13:26 OMG WHAT 16:13:30 I should realy test these before the meeting 16:13:38 true story 16:13:58 palendae: the next item is python naming, is this really still a thing? 16:14:07 asettle: It is not 16:14:12 REMOVE IT 16:14:14 nope - cleaning up the agenda is not really a strong point :p 16:14:16 * asettle slams gavel 16:14:25 odyssey4me: periodic jobs? 16:14:33 i think we hav enew ones coming up 16:14:36 that can come off too 16:14:37 Cause if it's not, imma rage quit. 16:14:38 OH that's it 16:14:41 You're all useless :p 16:14:46 no i mena 16:14:47 there are some new ones coming in 16:14:51 yeah ^ that 16:14:52 I should prod infra to merge them 16:14:55 asettle: No argument from me 16:14:56 #topic Periodic jobs 16:14:56 odyssey4me: 16:15:06 #link https://review.openstack.org/449272 16:15:09 a whole bunch more 16:15:46 MOre? 16:15:56 yeah the periodical work is great, so if we have more ideas around thigns we should be testing but aren't - lets discuss get them setup and move on! 16:16:19 https://admin.mashable.com/wp-content/uploads/2013/07/excited-baby.gif 16:16:30 ^^ a gif of me, moving on 16:16:30 heh 16:16:42 #topic Moving to uWSGI/NGinx 16:16:42 odyssey4me: do we need anything else on periodicals or are we good/no more topic needed for next week? 16:16:43 andymccr: 16:17:06 OK! so - I have proposed a WIP patch for using upstream NGinx and uWSGI for Nova placement: https://review.openstack.org/#/c/451425/ 16:17:08 there is some discussion going on 16:17:20 so please review and comment and give thoughts/feedback 16:17:25 #action review and comment on https://review.openstack.org/#/c/451425/ 16:17:43 this will then be used as the base of the pattern for our community goal around using wsgi apps everywhere 16:17:44 #link https://review.openstack.org/#/c/451425/ 16:17:51 Ooohh Ahhhh 16:17:52 Importento 16:17:54 so we need consensus on how that will go 16:18:19 I think we all need a time to digest this before consensus can happen 16:18:23 evrardjp: agreed 16:18:32 when do we take decision? 16:18:39 next week's meeting? 16:18:47 That seems reasonable. 16:18:48 evrardjp: there is no immediate rush, since half the projects don't support wsgi apps properly yet 16:18:52 Okay :) 16:18:55 but once they are ready i'd like to start motoring through them 16:19:01 that said, i'd really like to get some reviews on that 16:19:25 so logan- jmccrory looking at you 2 :) and anybody else - this is an important change that is going to shape the arch/way we install services etc 16:19:25 yea, and we can already think of cloudnull's ideas (or alternatives) because they are already technically doable 16:19:38 evrardjp: yeah agreed - that is literally a first pass, (or second since i reworked it today) 16:19:53 if it would help i will write a blueprint/spec about it and we can discuss whilst looking at that patch 16:19:54 but yes, adding reverse proxying there in the mix or not 16:20:39 * asettle nods thoughtfully 16:20:43 I agree. 16:20:53 ok cool :) 16:21:14 Shall we move on? 16:21:20 yeah, as this is a change in architecture, I think it's important to have a spec to help us and others understand the motivations 16:21:25 and the decisions made 16:21:27 ok cool 16:21:33 #action andymccr to create spec for uwsgi/nginx changes 16:22:11 ok all good on this topic i think! 16:22:31 You got it boss 16:22:33 #topic Weekly meeting host! 16:22:42 mhayden has abandoned us 16:22:44 Because he hates you all 16:22:47 ANd now we need a new meeting host 16:22:51 Ok so - mhayden has a meeting clash or the above might be more true :) 16:22:56 ... it's the above andymccr 16:23:02 Don't be lying to the children now 16:23:29 evrardjp already is a champ and hosts our weekly bug triage 16:23:30 so if there is somebody who would be keen to get involved and start hosting the meetings on a weekly basis that would be awesome! 16:23:42 It's not hard. Having a core be able to participate would be ideal. 16:23:56 logan- jmccrory spotz odyssey4me mgariepy 16:24:40 * asettle sits, and waits. 16:24:49 or perhaps we should look at changing the meeting time - i know we've had this discussion before, but if the consensus is that this time doesnt work at all - for the majority of people. we should look to change it 16:24:50 :) I'd prefer to give someone else a chance. 16:25:03 I'm happy to rotate with someone though. 16:25:04 odyssey4me: true, you've done your duties. You're honourably discharged. 16:25:41 meeting time change is fine for me, but would that be earlier or later 16:25:51 time is rough for me, i'm catching commute near beginning or end depending on daylight savings time 16:26:06 odyssey4me: would have to figure it out based on when works for people 16:26:10 Hmmm okay, maybe we should consider moving. But only on the basis there's more participation? 16:26:10 i think ^ is the key issue 16:26:22 Like, I'm going to call it, there's no point in having meetings where andymccr odyssey4me and evrardjp chat to themselves. 16:26:32 yeah i think the key question is would another time work better for more people 16:26:32 we'd also have to identify which days there are meeting room slots available 16:26:40 :) 16:26:41 So, if it means more participation moving, I'm all for it. 16:26:48 or is there a better way to get work items discussed that is outside of meetings. 16:26:49 odyssey4me: true, we would. 16:27:29 andymccr: maybe its worth sending out to the OSA cores a poll? 16:27:42 asettle I might be able to host, need to double check conflicts. Sorry was on phone with vets 16:27:43 andymccr and odyssey4me - yo I get that it's easier to speak, but let's have this recorded please. 16:27:48 spotz: no problem :) 16:27:52 That would be cool, if you have no conflicts. 16:27:58 probably best to do a ML post with the details of time slot options 16:28:04 yeah lets try that 16:28:04 +1 16:28:20 ok 16:28:22 i'll start that off 16:28:28 Okay, andymccr action that please :) 16:28:46 #action andymccr to look into timeslots for meeting and poll the team to decide a best time 16:29:08 *nods* like it 16:29:23 ok next! 16:29:39 #topic Release Planning and Decisions 16:29:41 andymccr: go go go 16:29:48 ok so releases will be going out this week, so tomorrow basically 16:30:01 i think we got in all the critical fixes that im aware of - but if there are any outstanding let me know 16:30:29 exit 16:30:37 xgerman: yo yo IRC bro 16:30:40 we've done a minor version bump due to the change in repo server build 16:30:45 I know 16:30:48 but yeah. 16:31:20 that is all for releases :) 16:32:06 Thanks andymccr :) 16:32:14 #topic Blueprint work 16:32:21 #link https://blueprints.launchpad.net/openstack-ansible/+spec/upgrade-testing 16:32:23 andymccr: 16:32:28 Upgrade testing for core roles in openstack-ansible 16:32:28 ok so 16:32:33 we are at the last step 16:32:35 just as an update 16:32:45 https://review.openstack.org/#/c/450198/ once that merges 16:32:52 we will have voting upgrade jobs on the core roles 16:33:04 #link https://review.openstack.org/#/c/450198/ 16:33:06 so that may be a pain at first :) btu they are passing as of now, so lets try keep it that way 16:33:25 Sweet :) 16:33:31 that is all on that bp - but after that it's gonna be closed and all done :) 16:33:39 Sweet as :) 16:33:47 #topic Open discussion 16:36:03 for upgrade jobs in those roles, is plan to add testing to see how long any downtime is as well? 16:36:27 jmccrory: id say yes if/when we start to implement the zero downtime upgrades per service 16:36:32 i think keystone is the only one right now 16:36:40 atm its more just a test that it works before and after 16:36:53 ah right, not sure where other projects are with that 16:37:05 jmccrory: yeah i know cinder has some - they did a presentation at the ops midcycle 16:37:11 would be great to get some time to actually work on that 16:38:37 yeah, we ideally should try and implement the rolling upgrades for cinder and nova 16:38:47 and swift, although that might already be there 16:38:59 with those we can add the measurements 16:39:08 I'm hoping to start submitting reviews for glance zero-downtime upgrades during pike 16:39:33 hmm yeah i guess although in swift we can't do serial i think - which is the main issue with zero-downtime on restarting services 16:39:52 andymccr: Cause of ring rebalancing? 16:40:19 palendae: yeah mostly because of the way we sync things - it means if all hosts haven't run certain tasks it'll fail 16:40:28 like it does an md5sum check on each hosts ring to make sure its good 16:40:36 and then does some checks - but if you serialise that the var doesnt exist 16:41:06 ideally need to rework that whole thing 16:41:15 whilst ensuring it still works properly :P 16:41:24 Hm, yeah 16:41:26 That'll be tricky 16:41:43 And neutron routers have to shift around, too 16:41:55 yeah i think swift is easy from a tech perspective, hard from how we imp it perspective 16:41:59 neutron is just hard i imagine :D 16:42:14 Yeah, until we enable l3ha it's gonna be annoying 16:42:32 It was enabled, then turned off due to bugs, I don't know the current status 16:43:17 not really hard 16:43:19 * asettle nods sagely 16:43:20 Mmhmm 16:43:43 just disable one agent, migrate the routers/networks, upgrade the disabled agent when they're done, then do the same for the other 16:44:03 Anyway, sounds like odyssey4me's got it 16:44:37 the tools are all there 16:44:47 theoretically it will work perfectly :P 16:45:07 and we enable l3ha by default anyway, so it'll likely just work :p 16:45:21 ship it 16:45:30 for a real online migration without it there's a bit more orchestration that needs doing 16:46:49 anyway, are we done for the day? 16:46:57 WE are 16:46:58 i believe so! 16:47:00 thanks all :) 16:47:09 #endmeeting