16:00:50 <andymccr> #startmeeting openstack_ansible_meeting
16:00:50 <odyssey4me> cloudnull you gonna do it, or shall I?
16:00:50 <openstack> Meeting started Tue May 15 16:00:50 2018 UTC and is due to finish in 60 minutes.  The chair is andymccr. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:52 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:54 <andymccr> always!
16:00:55 <openstack> The meeting name has been set to 'openstack_ansible_meeting'
16:01:02 <cloudnull> odyssey4me either way
16:01:07 <andymccr> #topic rollcall
16:01:10 * cloudnull sits down for the meeting
16:01:21 <andymccr> everybody who is about put a hand in the air :D
16:01:28 <cloudnull> /o presente
16:01:37 <andymccr> and then with the other hand type on the keyboard to say youre here
16:01:44 <mmercer|2> lol
16:01:53 * mmercer|2 eavesdrops instead
16:02:24 <openstackgerrit> Merged openstack/openstack-ansible-lxc_container_create master: Enable quota system and set qgroups  https://review.openstack.org/568430
16:02:30 <andymccr> lets get started!
16:02:48 <andymccr> #topic last weeks follow ups
16:03:20 <evrardjp> o/
16:03:26 <andymccr> so the main thing is: https://etherpad.openstack.org/p/YVR-openstack-ansible
16:03:41 <andymccr> if you're going to Vancouver, or if you have anything to add to the agenda for Vancouver - please take a look and update the etherpad!
16:03:51 <evrardjp> yeah not much other last week feedback :(
16:04:05 <andymccr> super useful to have good topics for the feedback sessions etc.
16:04:15 <evrardjp> agreed
16:04:24 <andymccr> also the etherpad has some pretty good info on where/when things are - feel free to add to that!
16:04:52 <odyssey4me> o/
16:05:22 <openstackgerrit> Kevin Carter (cloudnull) proposed openstack/openstack-ansible-lxc_hosts master: Add task to regather facts after run  https://review.openstack.org/568632
16:05:31 <andymccr> that's pretty much the only topic for last weeks highlights,  does anybody have anything new this week?
16:05:47 <hwoarang> o/
16:05:52 <mattt> o/
16:05:56 <andymccr> otherwise we can move onto everybodies favourite time of the week. Bug Triage!
16:06:17 <andymccr> i'll give it a few mins
16:07:37 <andymccr> ok!
16:07:40 <andymccr> #topic bug triage
16:07:45 <andymccr> as always: https://etherpad.openstack.org/p/osa-bugtriage
16:08:17 <andymccr> first up!
16:08:18 <andymccr> #link https://bugs.launchpad.net/openstack-ansible/+bug/1771200
16:08:20 <openstack> Launchpad bug 1771200 in openstack-ansible "stable/pike (16.0.11): missing default for neutron_ovs_service_name" [Undecided,New]
16:08:43 <hwoarang> looks like this is WIP
16:09:00 <andymccr> could be already fixed
16:09:08 <andymccr> i see there was a recheck
16:09:29 <odyssey4me> yep, it's busy checking
16:09:37 <openstackgerrit> Kevin Carter (cloudnull) proposed openstack/openstack-ansible-lxc_container_create master: Add task to regather facts after run  https://review.openstack.org/568635
16:10:13 <andymccr> the fix seems ifne
16:10:14 <andymccr> fine
16:10:19 <andymccr> and the bug seems good so lets move on
16:10:27 <evrardjp> it would be very nice if we could have a scenario later. But yes :)
16:10:34 <andymccr> putting importance to high
16:10:43 <andymccr> haha yeah that has been a thing forever pretty much
16:11:13 <andymccr> #link https://bugs.launchpad.net/openstack-ansible/+bug/1769195
16:11:14 <openstack> Launchpad bug 1769195 in openstack-ansible "Ocata Series Release Notes in openstack-ansible" [Undecided,New] - Assigned to Jesse Pretorius (jesse-pretorius)
16:11:29 <hwoarang> why does the bug title say 'relase notes' ?
16:11:34 <hwoarang> when this is about resolv.conf?
16:11:59 <andymccr> haha yeah
16:12:00 <odyssey4me> because this is a bug in the release note, and an update happened after that
16:12:00 <andymccr> i was confused
16:12:32 <andymccr> well it seems like its under control, odyssey4me were you able to confirm it?
16:12:32 <odyssey4me> https://review.openstack.org/#/q/I11d069e2d0cb3becad067689fa8f1e4c9391f368 got merged earlier, so this issue should be solved in new versions
16:12:43 <andymccr> if its valid thats high/critical - but im guessing its already fixed
16:12:48 <andymccr> we're waiting on feedback so perhaps incomplete?
16:12:56 <odyssey4me> incomplete, yeah
16:13:19 <odyssey4me> we have patches up to fix both the reno, and the lxc_hosts role... so it's pretty much incomplete now until we get an answer
16:13:33 <andymccr> sweet
16:13:33 <andymccr> done
16:13:35 <andymccr> next!
16:13:42 <andymccr> #link https://bugs.launchpad.net/openstack-ansible/+bug/1758144
16:13:43 <openstack> Launchpad bug 1758144 in openstack-ansible "resolv.conf in containers set too late" [Undecided,New]
16:13:44 <andymccr> pretty similar
16:13:44 <evrardjp> incomplete indeed
16:14:01 <evrardjp> yeah the bugs remaining are old ones nobody confirmed yet
16:14:09 <evrardjp> and nobody got the time to confirm
16:14:18 <odyssey4me> no idea about this one
16:14:28 <andymccr> yeah not too sure
16:15:27 <andymccr> i feel like we need more info on that
16:16:09 <evrardjp> yeah logan- had an idea but that's as far as I go
16:16:46 <andymccr> guessing logan- isn't about
16:17:19 <logan-> i don't have an idea, I just figured some things got rearranged in queens that breaks unbound. but i haven't done queens testing with unbound yet :/
16:17:26 <evrardjp> ok
16:17:58 <logan-> correction, not breaks unbound, but maybe causes a race condition where the resolvers aren't set in the containers in time
16:18:10 <openstackgerrit> Merged openstack/openstack-ansible-os_glance master: Move database creation into role  https://review.openstack.org/568481
16:18:13 <andymccr> logan-: perhaps we can ask for more info, like way to recreate etc?
16:18:23 <openstackgerrit> Jesse Pretorius (odyssey4me) proposed openstack/openstack-ansible stable/queens: Remove default pip_links value  https://review.openstack.org/568637
16:18:44 <odyssey4me> not sure if dcdamien is about, as he registered the bug
16:19:17 <andymccr> ahh nice
16:20:09 <logan-> we might just need to add something like https://github.com/openstack/openstack-ansible/blob/b3c670faeba53eb00212deb1e197499959c40561/playbooks/repo-server.yml#L16-L20 to repo-use.yml
16:20:44 <andymccr> logan-: we could propose that as an idea and perhaps dcdamien can verify - would you mind putting a comment into that issue?
16:20:56 <logan-> although that pretty much reverts the whole unbound "JIT" thing because it runs across all containers/hosts
16:21:01 <andymccr> hmm
16:21:59 <logan-> so another possibility is to revert https://github.com/openstack/openstack-ansible/commit/b3c670faeba53eb00212deb1e197499959c40561. I think it was meant as groundwork for container JIT creation but since that never happened, this commit isnt really needed
16:24:03 <evrardjp> I am not for or against JIT unbound, but right now I am wondering what its value
16:24:10 <evrardjp> what is its* value
16:24:45 <logan-> also if we decide to do systemd-resolved it changes this whole thing entirely
16:24:52 <logan-> systemd-resolved in queens*
16:25:19 <logan-> because you'd get rid of the resolvconf role execution and have to deal with other race conditions instead when the containers are being created
16:25:26 <evrardjp> let's not talk about backporting new features in stable branches while I am close to going to bed, to avoid my future nightmares.
16:25:33 <evrardjp> :D
16:25:34 <odyssey4me> with repo-use in place doing pip_install things on the containers, the strategy either needs to be to switch the repo-use things to JIT, or to switch the resolvconf things to repo-use
16:25:59 <logan-> yeah i'm not sure what repo-use does, maybe just run the JIT using the same scoping (everything)
16:26:50 <evrardjp> basically you have the repo, then you point all the nodes to "use" it, that's repo-use. Sorry if I came up with that name.
16:27:03 <odyssey4me> repouse re-runs the pip_install role to reconfigure pip to use the repo now that it's built... but pip_install in queens installs more things
16:27:09 <logan-> ohh gotcha
16:27:25 <evrardjp> so I think resolution should happen before
16:27:28 <evrardjp> at container creation
16:27:36 <odyssey4me> we could also backport the thing in master which does the pip_install idempotently, so the second round is a noop except for the config change
16:28:11 <evrardjp> let's just wait for input to know what's working and what's not working maybe?
16:28:16 <odyssey4me> that would make repo-use not really need to do any resolving, and therefore solve the resolver issue
16:29:00 <logan-> nice odyssey4me
16:29:06 <logan-> that might do the trick
16:29:17 <andymccr> so does somebody want to propose something in that bug? and/or a PR?
16:29:25 <odyssey4me> lemme take a look at this - I've got some issues for queens to solve relating to pip which touches repo-use
16:29:48 <andymccr> ok cool
16:29:50 <odyssey4me> I've assigned it to me
16:29:56 <odyssey4me> I'll fire up an unbound setup too - never done that before, so I'm curious. :)
16:29:56 <andymccr> thanks odyssey4me!
16:30:01 <andymccr> ok
16:30:03 <andymccr> last one
16:30:05 <andymccr> #link https://bugs.launchpad.net/openstack-ansible/+bug/1743032
16:30:07 <openstack> Launchpad bug 1743032 in openstack-ansible "Galera cluster maintenance in OpenStack-Ansible" [Undecided,New]
16:30:16 <openstackgerrit> Kevin Carter (cloudnull) proposed openstack/openstack-ansible-lxc_container_create master: Add task to regather facts after run  https://review.openstack.org/568635
16:30:36 * odyssey4me runs away
16:30:41 <openstackgerrit> Kevin Carter (cloudnull) proposed openstack/openstack-ansible-lxc_hosts master: Add task to regather facts after run  https://review.openstack.org/568632
16:31:21 <openstackgerrit> Kevin Carter (cloudnull) proposed openstack/openstack-ansible master: Change to using the package module instead of apt  https://review.openstack.org/568615
16:31:30 <andymccr> *crickets* :P
16:32:07 <openstackgerrit> Kevin Carter (cloudnull) proposed openstack/openstack-ansible master: Begin testing opensuse and centos with nspawn  https://review.openstack.org/568197
16:32:34 <evrardjp> andymccr: :)
16:32:38 <andymccr> part of me feels those docs should point to a galera doc about that
16:32:46 <andymccr> its a 3 node galera cluster like any other
16:33:31 <evrardjp> we completely changed the docs too
16:33:53 <andymccr> ahh
16:33:55 <andymccr> maybe that is done
16:34:03 <andymccr> since our new instructions do not match what is listed as wrong there
16:34:04 <evrardjp> it has "Please also have a look at upstream starting a cluster page"
16:34:05 <openstackgerrit> Kevin Carter (cloudnull) proposed openstack/openstack-ansible master: Use fan out when deploying with nspawn  https://review.openstack.org/568331
16:34:52 <evrardjp> I think it's worth saying incomplete, and just get it over with
16:34:54 <odyssey4me> yeah, we should reference the upstream docs and stop trying to maintain this stuff
16:34:56 <andymccr> it explains the systemd bits better now
16:35:02 <andymccr> but yeah thats my opinion
16:35:08 <andymccr> we set it up and tell you how to set it up using our roles
16:35:22 <andymccr> but running it is something you should check on their website, we;re using base packages so nothing magical
16:36:13 <andymccr> ok cool
16:36:18 <andymccr> that's it for today
16:37:10 <andymccr> think we need to figure out a meeting chair for next week's meeting - any volunteers?!
16:37:34 <cloudnull> I will be out the summit, I can take the following week though
16:37:38 <andymccr> ahh yeah
16:37:42 <andymccr> of course, summit is next week!
16:37:48 <andymccr> evrardjp: should we skip next week's?
16:38:00 <odyssey4me> perhaps a good idea
16:38:37 <hwoarang> sure
16:38:47 <evrardjp> yes
16:38:59 <andymccr> ok cool. and cloudnull is up for the week after! (and since he's at the summit we can get a recap of summit activities yay)
16:39:00 <evrardjp> we should still roll the meeting chair
16:39:03 <evrardjp> ok
16:39:11 <evrardjp> cool
16:39:13 <evrardjp> thanks cloudnull
16:39:14 <cloudnull> ++
16:39:17 <andymccr> thanks cloudnull!
16:39:18 <andymccr> on that note.
16:39:21 <andymccr> #endmeeting