15:59:49 <evrardjp> #startmeeting openstack_ansible_meeting
15:59:49 <openstack> Meeting started Tue Jan 30 15:59:49 2018 UTC and is due to finish in 60 minutes.  The chair is evrardjp. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:59:50 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:59:53 <openstack> The meeting name has been set to 'openstack_ansible_meeting'
15:59:54 <evrardjp> #topic rollcall
15:59:55 <prometheanfire> o/
16:00:35 <mgariepy> o/
16:00:36 * mhayden struts
16:00:44 <jmccrory> o/
16:01:47 <evrardjp> leaving a few seconds for late joiners
16:01:55 <evrardjp> waiting*
16:02:08 <hwoarang> o/
16:02:10 <evrardjp> bad french -> english translation there!
16:02:53 <evrardjp> ok let's go
16:03:14 <evrardjp> #topic Review action items from last month
16:03:37 <spotz> o/
16:03:41 <evrardjp> simple, last month we had no community meeting. Christmas and all.
16:03:55 <RandomTech> oh is the meeting starting?
16:03:57 <evrardjp> so let's move on to next topic!
16:04:05 <mhayden> happy holidays retroactively
16:04:05 <evrardjp> RandomTech: yes :)
16:04:14 <RandomTech> okay i can wait with my questions :p
16:04:24 <evrardjp> Happy holidays indeed, I wish you all a good 2018!
16:04:28 <mhayden> RandomTech: meetings are for me to randomly pop in and derail evrardjp's good deeds ;)
16:04:53 <evrardjp> lol
16:05:07 <evrardjp> wondering why we schedule them every tuesday at the same time !
16:05:16 <evrardjp> hahah
16:05:17 <evrardjp> anyway
16:05:19 <evrardjp> next
16:05:22 <evrardjp> #topic Liaisons feedback
16:05:27 <evrardjp> anything to report?
16:05:55 <evrardjp> mhayden: I guess you had a nice january with the spectre and stuff, anything impacting us we should pay attention to?
16:06:13 <mhayden> i'd say the expectation should be that we're going to see more patches over time
16:06:14 <evrardjp> I think that we are covered with distro packages
16:06:26 <mhayden> bugs will be fixed which make more bugs
16:06:36 <mhayden> and also there will be gradual perf enhancements to make up for what's lost
16:06:38 <evrardjp> ok. yeah but nothing to do, as we suspected.
16:06:46 <mhayden> so keep tabs on what the distros are shipping ;)
16:06:47 <evrardjp> yeah that's another topic.
16:06:57 <evrardjp> I trust you there mhayden ! :D
16:07:04 <mhayden> but deployers should remember that the guests need love too!
16:07:04 <evrardjp> anything else?
16:07:10 <evrardjp> that's true
16:07:11 <mhayden> don't forget about your instances and patches ther e;)
16:07:16 <mhayden> that's it for now
16:08:01 <evrardjp> for releases, I submitted milestone 3 recently, a few days later than the deadlines for cycle-with-milestones (so we are in advance)
16:08:35 <evrardjp> I will do a release for the other branches, as usual, this friday. (End of month)
16:08:43 <mhayden> woot
16:08:46 * mhayden saw the emails
16:09:14 <evrardjp> at least that's what my agenda tells me I have to do for friday :p
16:09:19 <evrardjp> Anyway, next topic
16:09:35 <evrardjp> (except if any other liaison have something to say)
16:09:47 <evrardjp> moving on
16:09:51 <evrardjp> #topic PTG
16:10:10 <evrardjp> here is the etherpad: https://etherpad.openstack.org/p/osa-rocky-ptg
16:10:20 <evrardjp> Please fill in your presence and topics you want to discuss
16:11:07 <evrardjp> if you have topics for the ptg, please shoot.
16:11:52 <evrardjp> I am waiting for your ideas there :)
16:12:04 * mhayden will add some stuff but won't be able to attend
16:12:15 <hwoarang> video conference?
16:12:17 <hwoarang> :)
16:12:22 <mhayden> perhaps someone can bring me back a Guinness T-shirt ;)
16:12:24 <evrardjp> I am thinking we'll do that.
16:12:34 <evrardjp> mhayden: haha. Will do.
16:12:42 <evrardjp> or I will ask d34dh0r53
16:13:22 <evrardjp> if you're editing the etherpad, could you add your name, please?
16:14:09 <evrardjp> ok let's move on
16:14:39 <evrardjp> #topic Specs
16:14:58 <evrardjp> the docs spec has merged but I didn't work on it yet
16:15:05 <cloudnull> mornings
16:15:25 <evrardjp> the nspawn is in progress, sometimes cloudnull and I have different opinions, but it's in progress too
16:15:29 <evrardjp> cloudnull: morning!
16:15:31 <evrardjp> right on time
16:15:56 <evrardjp> the pip changes are in progress , but any help is welcomed
16:16:01 <evrardjp> for the links here they are:
16:16:24 <cloudnull> ++ will get some reviews done today for sure.
16:16:27 <evrardjp> oh we also have other sdn/opnfv specs
16:16:40 <evrardjp> yes I am trying to find the links :D
16:16:45 <evrardjp> cloudnull: could you paste yours?
16:17:21 <openstackgerrit> Major Hayden proposed openstack/openstack-ansible-os_nova master: Fix SELinux file contexts for nova's ssh keys  https://review.openstack.org/534891
16:17:23 <evrardjp> https://review.openstack.org/#/c/531850/ was the one for docs
16:17:27 <cloudnull> for nspawn https://review.openstack.org/#/q/topic:nspawn-driver+(status:open+OR+status:merged)
16:17:37 <evrardjp> thanks cloudnull
16:18:05 <evrardjp> the docs link I gave you is the blueprint for implementation, if someone got the chance to work on it, that would be great
16:18:14 <evrardjp> the nspawn part are requiring reviews
16:18:25 <evrardjp> d34dh0r53: do you want to speak about https://review.openstack.org/#/c/527769/ ?
16:19:54 <mhayden> evrardjp: he better speak about it ;)
16:20:08 <cloudnull> for nspawn I need to get https://review.openstack.org/#/c/527749 finished, then I'll have some updating to do to get the actual nspawn patch in order.
16:20:19 <evrardjp> odyssey4me: 's spec for pip changes and the following reviews are there: https://review.openstack.org/#/q/project:%255Eopenstack/openstack-ansible.*+branch:master+topic:bp/python-build-install-simplification
16:21:12 <d34dh0r53> sorry, meetin's
16:21:18 <evrardjp> so yeah, please act on the links above (review, code, whatever...) :)
16:21:26 <evrardjp> ok let's move on then
16:21:41 <evrardjp> #topic Role maturity handling
16:21:57 <d34dh0r53> evrardjp: put it on the agenda for next week?
16:22:16 <evrardjp> d34dh0r53: it will be there next week, as with every week :)
16:22:30 <evrardjp> don't worry, specs are there to stay!
16:22:44 <evrardjp> (that was a joke ... hoping we'll implement stuff!)
16:23:06 <d34dh0r53> I lol'd on the inside
16:23:18 <evrardjp> my jokes aren't as nice on irc as they are on real life, which was the perfect transition to...
16:23:29 <evrardjp> we're gonna discuss role maturity handling during the ptg.
16:24:02 <evrardjp> I think there is a risk, right now, of roles rotting (as we've seen in the past), so we need to take appropriate action before it happens.
16:24:50 <evrardjp> Let's discuss a plan at the ptg, and please come at the ptg with ideas on how we can improve our roles maturity, and prevent them from rotting
16:24:58 <evrardjp> ok next topic
16:25:06 <evrardjp> #topic open discussion
16:25:20 <prometheanfire> who's gonna be at the ptg?
16:25:29 <evrardjp> that should be on the etherpad prometheanfire
16:25:37 <prometheanfire> k
16:25:39 <evrardjp> see a little above
16:25:47 <prometheanfire> ya, have it open
16:26:02 <evrardjp> for the first open discussion topic I want to discuss our gates
16:26:21 <evrardjp> I want to raise a warning -- our project quality seems decreasing
16:26:23 <evrardjp> Have a look at our gates dashboard.
16:26:49 <evrardjp> go into http://zuul.openstack.org/builds.html select project:openstack/openstack-ansible
16:27:13 <evrardjp> In the last month, so many issues have been solved, yet so little green appears on the same dashboard.
16:27:17 <evrardjp> There are jobs which are broken for a cycle now, and I am not even talking about role tests.
16:27:17 <prometheanfire> evrardjp: gates all over are getting worse over the last month
16:27:27 <evrardjp> I know there is much orange on that dashboard page due to exceptional circumstances.
16:27:32 <evrardjp> But when a month is almost entirely composed of exceptional circumstances, the exceptional becomes ordinary.
16:27:36 <hwoarang> it's hard to tell which failures are because of us and which ones are because of infra/zuul issues though
16:27:41 <evrardjp> We should work together on making the breakage an exception, not the pure reality.
16:27:50 <evrardjp> I agree hwoarang
16:28:01 <mhayden> well prometheanfire found that rackspace's mirrors are only doing 100mbit/sec
16:28:01 <evrardjp> cloudnull for example, had to wait for more than 2 weeks before we could even think of merging the first basic nspawn patch.
16:28:05 <mhayden> so that's a recent problem
16:28:06 <evrardjp> A series of my patches is waiting for months to find out the good window of opportunity.
16:28:23 <evrardjp> I am worried: We have so few people actually working on fixing stuff .... (tremendous thanks hwoarang and odyssey4me who are the biggest fixers).
16:28:31 <evrardjp> I'd like to organise at least a bug smash after rc1, and that would be great if you could get people to work on this.
16:28:34 <prometheanfire> mhayden: rackspace's openstack mirrors
16:28:46 <mhayden> prometheanfire: ah, i stand corrected
16:28:46 <prometheanfire> mhayden: os-infra is working on rebuilding the VM hosting the mirror
16:28:48 <evrardjp> would you be ok with that?
16:28:54 <prometheanfire> mhayden: ya, they could have made that more clear
16:29:05 <mhayden> evrardjp: bug smash sounds excellent
16:29:16 <evrardjp> It would be really nice that someone handles the bug triage and its statistics.
16:29:33 <evrardjp> that would help too for the bug smash
16:29:34 <mhayden> i propose we all go to hwoarang's house and work from there -- i'll chip in for pizza
16:29:39 <evrardjp> And last point, if you think you can fix a job -- looking at the centos jobs particularily -- I'd love to have your help.
16:29:45 <hwoarang> why would you want to come to england?
16:29:48 <hwoarang> -_-
16:29:49 <mhayden> evrardjp: trying ;)
16:29:54 <evrardjp> :D
16:30:08 <evrardjp> And the last thing I wanted to say is thank you all
16:30:56 <mhayden> s/thank you all/thank y'all/
16:31:01 <evrardjp> because we had many bad moments during this cycle, but many good moments too, and I think we are heading towards new stuff even if that cycle was quite infra themed :D
16:31:13 <evrardjp> mhayden: :D
16:31:27 <mhayden> there's always gonna be bumps in the road
16:31:33 <mhayden> thanks for steering our ship, evrardjp
16:31:44 <evrardjp> now it's up to you to speak, we have 29 more minutes of open discussion!
16:31:49 <evrardjp> 28!
16:32:36 <evrardjp> oh yeah, I am trying to include config_template into core of ansible again. Let's see how it will go.
16:32:50 <RandomTech> I have a comment if you have time
16:33:09 <evrardjp> If it doesn't work, we're gonna have no choice than shipping it into a different place to help collaboration between ceph-ansible, and others.
16:33:22 <evrardjp> RandomTech: yeah, we have time, it's community meeting :)
16:33:35 <evrardjp> if you have a community thing, let's discuss it!
16:34:26 <RandomTech> Ive had to start learning openstack from ground zero, and ive noticed it can be hard figuring out how certain changes to the configs effect the outcome of the playbook
16:34:41 <RandomTech> id have to search for a second to find specific examples though
16:35:25 <evrardjp> how can we improve, RandomTech ?
16:36:19 <RandomTech> A bit more documentation on how specific changes in the openstack_user_config and user_variable effect the playbooks would be nice. Even if its just a section in the appendeces.
16:36:20 <evrardjp> RandomTech: Would this help: https://review.openstack.org/#/c/531850/ ?
16:37:00 <RandomTech> ome moment while i read
16:37:11 <evrardjp> ok I will remember that. We may assume too many things and we may assume some kind of ansible knowledge too.
16:37:22 <evrardjp> We should be more explicit
16:37:30 <evrardjp> Good proposition RandomTech !
16:38:01 <RandomTech> ya i was basically thrown into the fire by higher ups at my research center
16:38:08 <hwoarang> true but it's nearly impossible to document every variable on every role
16:38:20 <hwoarang> though we do a good job with comments in the default var files
16:38:24 <RandomTech> was told to set it up with only a basic background in computer networking
16:38:52 <evrardjp> RandomTech: yeah openstack isn't really friendly on that side either.
16:39:14 <evrardjp> hwoarang: I have another idea on that improvements, will draft a PoC for the PTG, this way we can discuss it further.
16:39:24 <evrardjp> that kind of improvements*
16:39:28 <mhayden> one of the feedback points from a coworker is that it's hard to figure out what ansible variables to set to get the corresponding change in nova
16:39:35 <mhayden> since some names don't match
16:40:07 <evrardjp> I think we should simplify those things
16:40:29 <evrardjp> it's hard for newcomers, and that will be my focus for next cycle.
16:40:39 <evrardjp> At least that's what I'd like to do.
16:41:09 <RandomTech> evrardjp: i believe that would be a decent step into helping, examples on configurations/stories with a good explanation would help alot
16:41:56 <evrardjp> RandomTech: would you be able to help us on that?
16:42:12 <RandomTech> i noticed alot of times after hearing someone explain in detail what was going on when trying to do something helped tremendously
16:42:22 <RandomTech> i can at least take a look at what you have from time to time
16:42:33 <evrardjp> ok
16:42:40 <evrardjp> anything else for the community meeting?
16:42:51 <evrardjp> 17 minutes remaining.
16:43:51 <evrardjp> ok thank you everyone!
16:43:57 <hwoarang> thank you too
16:43:59 <RandomTech> a checklist of basic requirements somewhere would be nice. Some sort of coalated "you need to do at least these things"
16:44:22 <RandomTech> no problem
16:44:31 <evrardjp> RandomTech: let's discuss this in the docs patches :)
16:44:40 <evrardjp> #endmeeting