16:00:18 #startmeeting openstack_ansible_meeting 16:00:19 Meeting started Thu May 4 16:00:18 2017 UTC and is due to finish in 60 minutes. The chair is andymccr. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:20 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:23 The meeting name has been set to 'openstack_ansible_meeting' 16:00:25 howdy 16:00:31 o/ 16:00:31 o/ 16:01:04 o/ 16:01:10 give it a few minutes 16:02:02 -o- not really here:) 16:02:18 #addchair evrardjp 16:02:25 o/ 16:02:52 #chair evrardjp 16:02:53 Current chairs: andymccr evrardjp 16:02:55 there we go :D 16:03:02 o/ 16:03:03 haha 16:03:29 ok! i think thats the majority of people - just as an fyi i need to run off in like 20 mins or so, there isnt much to cover but evrardjp is gonna finish up if we're not quite finished yet! 16:03:46 #topic Action items from last week 16:03:54 so we have 2 action items from last week 16:04:00 add spec for hyper-converge - mhayden cloudnull 16:04:09 with the summit coming up im guessing neither of you have had time 16:04:09 o/ sorry am here 16:04:38 I guess mhayden is busy with rh summit 16:04:42 I'll add that one back as an action item and we can follow up after the summit 16:04:43 yeah 16:04:44 cloudnull: ? 16:04:49 #action add spec for hyper-converge - mhayden cloudnull 16:05:31 ok cloudnull isnt available :) 16:05:35 the only other action item was: volunteers to investigate py35 requirements 16:05:47 I didn't got the chance to do it 16:05:53 odyssey4me: told me he hasn't either 16:06:06 i think after the summit i'll have a bit more time so i can hopefully start working on that myself 16:06:25 on top of that ansible under python3 now started to fail for me due to urlparse change 16:06:25 #action prod on the py35 requirements goal 16:06:33 hmm 16:06:43 *pokes andymccr* sign up on etherpadif going to Boston.... 16:06:47 but I have to dig deeper into that later. 16:06:49 guess thats why we need testing at some point ;P 16:07:02 spotz: will get to that! summit talk coming up next! 16:07:15 lets move on! next up 16:07:16 I think we covered AP 16:07:19 yup! 16:07:23 #topic Summit next week in Boston! 16:07:32 have fun! :p 16:07:45 ok so - as spotz said anybody going take a look at the etherpad link 16:07:47 #link https://etherpad.openstack.org/p/osa-summit-talks 16:08:04 add your details if you're keen to talk with the rest of the crew - there is a hangouts session up 16:08:14 we'll try do dinner/drinks and definitely catch up during the week 16:08:26 also if there are any sessions missing from the etherpad feel free to add 16:08:37 Sunday night official outing, Thursday unofficial! 16:09:00 ^ this - looking forward to meeting some of you, and seeing familiar faces. should be great 16:09:25 OK SO - forward thinking - but i'll add this as an agenda item until the event :P 16:09:29 #topic PTG - 11-15 September - Denver, Colorado 16:09:46 o/ 16:09:48 just to keep it in peoples minds - there really is no additional info at this point, but it's a good point to start arranging and planning 16:10:03 #link https://upload.wikimedia.org/wikipedia/en/f/f3/Denver_the_Last_Dinosaur_title_card.jpg 16:10:11 I'm not sorry. 16:10:12 evrardjp: so relevant 16:10:14 hahaha 16:10:19 heheh 16:10:21 im sure the PTG will be exactly like that! 16:10:41 ok so! moving on 16:10:43 #topic Release Planning and Decisions 16:11:11 OK SO! Ocata is on hold (for SHA bump) until reno 2.2.1 is released 16:11:15 #link https://review.openstack.org/#/c/462528/ 16:11:34 theres nothingreally to do there, but once that merges we can push the SHA bump, and it should unblock any releasenote gates on master & stable/ocata 16:11:51 i'll still aim to do a release next week - especially for stable/newton 16:12:36 For pike the next milestone is the first week of June - so we have a bit of time til that happens, but it marks the end of projects being able to be added as part of the release 16:12:50 so if you have anything you want to get in for the final release it needs to be apart of m3. (june 05-09 will be m3) 16:13:30 anyway moving along :) 16:13:32 #topic uWSGI/NGinx Blueprint: https://review.openstack.org/#/c/458595/ 16:13:55 I've refactored the uwsgi patch to make use of the other nova services (nova-api, nova-metadata) - its not working just yet - will fix that up 16:14:04 thanks for the feedback so far, i responded for the most part 16:14:33 lets keep that going - it'd be cool to discuss at the summit a bit and get a workable/agreed solution going. 16:15:51 handlers are defined per play if that can help. Also you can define some of them in plays directly, not only in roles, I'll adapt my review 16:16:13 evrardjp: ok cool - lets discuss that and come up with a better method then. that sounds workable 16:16:48 evrardjp: i think practically its there - it just needs some tinkering (like the role dependency and other things) to bring it to the best possible outcome. 16:17:06 i also ran into a lint issue because im calling handlers from a role that has a lint issue 16:17:07 Ok cool. Thanks for the spec! 16:17:19 trying to get that fixed upstream - but it may mean we have to come up with another method of doing this 16:17:32 or i need to dig into ignoring lint issues on handlers :P 16:17:40 if you have a link to code that would be good 16:17:53 well ignoring linting on an outside role could be fine for me 16:17:57 it's outside our control 16:18:02 #link https://github.com/jdauphant/ansible-role-nginx/pull/140 16:18:12 thanks. 16:18:13 evrardjp: agreed - but usually we ignore lint on the actual task by using the tag to ignore lint 16:18:21 im not sure how to ignore linters on the handler - although im sure there must be a way 16:18:31 andymccr same tag on the handler 16:18:42 odyssey4me: but we dont own the handler - and i cant tag the notify statement 16:18:47 ah 16:18:51 are we using listen? 16:18:56 no they're using listen 16:19:00 hmm, that's a fun one 16:19:37 yeah. im sure there's a way 16:19:39 just need tofigure that out 16:19:47 would be awesome to ignore linters on any roles that arent ours. without having to tag 16:20:02 just tag it on the complete role 16:20:21 in the play or the meta dependency :p 16:20:27 yeah well i think we'll change how we do that dep anyway 16:20:28 well that's another conversation 16:20:43 I mean that conversation is probably for a review instead of for the meeting 16:20:49 hahahaha yeah probably 16:20:58 i'll revise the spec after the summit and we can redo that! 16:20:59 anyway lastly! 16:21:02 #topic open discussion 16:22:01 nothing from me at this time - thanks for everyone pitching in to reviews 16:22:13 we're slowly getting more cross-repo testing functionality coming through 16:22:16 thanks for the work on that cross-repo testing odyssey4me! and the 2.3 fixes, and all the other stuff :P 16:22:30 Also - can some of y'all take a wee looksie at my wee patch here: https://review.openstack.org/#/c/462477/ 16:22:47 #link https://review.openstack.org/#/c/462477/ 16:22:51 oh yes! that reminds me 16:22:54 the current stuff is focused on our own repositories, but I have some more WIP patches which are enabling cross-repo testing with ARA and will extend that to any openstack services 16:22:55 asettle - pulled up and will review after meeting 16:23:00 the Ops guide is coming along nicely - so im told. 16:23:07 Thanks spotz 16:23:12 Yeah mate where'd you hear that awesome news andymccr ? 16:23:18 :p 16:23:24 We are very nearly done :P 16:23:29 Anyway andymccr you gotta go flo 16:23:32 haha 16:23:41 if we could get reviews on the guide as a whole that'd be great 16:23:47 so if you have a chance to read through it please do! 16:23:48 +2 to that 16:24:00 #link https://docs.openstack.org/developer/openstack-ansible/draft-operations-guide/index.html 16:24:08 andymccr: sorry was afk , back now :) 16:24:09 file bugs, fix bugs, do the things 16:24:17 I'm still working through the atomic policy file changes too, which I see as a pre-requisite for the git-sourced config files... so I'm working through those over time and would appreciate reviews and/or help on those 16:24:19 :) 16:24:21 haha cloudnull no worries - hyperconverge spec after summit si si? :) 16:24:27 si si 16:24:28 the pattern is set, so anyone who feels like it can go for it 16:24:30 thanks! 16:24:32 cool 16:24:55 andymccr: jdauphant just merged your PR 16:25:00 evrardjp: nice! 16:25:05 wasnt mine - but yeh 16:25:07 thats quick response time 16:25:25 anymore for anymore? 16:25:33 for anyone? 16:25:39 I don't have anything to add. 16:26:04 in that case. thanks all - and looking forward to next week (for those who are going to be there) 16:26:15 #endmeeting