16:13:22 <mnaser> #startmeeting openstack_ansible_meeting
16:13:24 <openstack> Meeting started Tue Feb 26 16:13:22 2019 UTC and is due to finish in 60 minutes.  The chair is mnaser. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:13:25 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:13:25 <mnaser> #topic office hours
16:13:27 <openstack> The meeting name has been set to 'openstack_ansible_meeting'
16:13:32 <mnaser> let's try this out.
16:14:05 <guilhermesp> o/
16:14:09 <prometheanfire> \o
16:14:11 <chandankumar> \o/
16:15:06 <arxcruz> \o
16:15:49 <mnaser> how's our gate feeling these days
16:15:56 <mnaser> i tried to ping the ML about the heat stuff jrosser has been looking at
16:16:01 <jamesdenton> o/
16:16:54 <chandankumar> mnaser: I think the gate was good, few timedout on yum mirrors
16:17:54 <chandankumar> and today on cirros image url time out
16:19:05 <jrosser> we have some really funky failures with os_swift https://review.openstack.org/#/c/635186/
16:19:57 <jrosser> mnaser: no-one bit on the ML heat post
16:20:11 <mnaser> yeah i just tried to push something out today jrosser :(
16:21:04 <openstackgerrit> Kevin Carter (cloudnull) proposed openstack/openstack-ansible-ops master: Ensure the default version of Java is set  https://review.openstack.org/639378
16:24:59 <jrosser> mnaser: perhaps we should go to a heat irc meeting?
16:25:30 <mnaser> jrosser: i think that might be a good idea
16:27:57 <odyssey4me> o/
16:28:29 <odyssey4me> apologies for disappearing last week - I had a sudden urgent need to become a painter for my kitchen wall
16:29:21 <mnaser> odyssey4me: dont worry.. happens to me all the time
16:29:22 <mnaser> :P
16:32:08 <mnaser> dont think we've progressed at all about nspawn
16:32:18 <odyssey4me> I'll be spending a little time this evening working out the last bits for the python build simplification. There's a month left before we hit Stein RC, so I'd really like to have it done and dusted within the next two weeks.
16:32:18 <mnaser> im worried we wont be able to do much about it this cycle and itll put us one release behind
16:32:49 <odyssey4me> For nspawn, perhaps the best thing to do is to schedule a hackathon time frame at the PTG to get a passing gate
16:33:44 <odyssey4me> Spend a day doing restrospective, and two days hacking, with a small team working on just nspawn.
16:34:59 <spotz> hey all
16:37:16 <openstackgerrit> Mikael Loaec proposed openstack/openstack-ansible-os_nova stable/rocky: Proposition to resolve bug #1782798  https://review.openstack.org/639380
16:37:17 <openstack> bug 1782798 in openstack-ansible "AIO Build Fails on SELinux File Context Tasks" [Medium,Fix released] https://launchpad.net/bugs/1782798
16:37:22 <mnaser> odyssey4me: but the ptg is after release i think, right?
16:43:14 <odyssey4me> mnaser sure, but what matters is getting it working - more than making it work in this release
16:46:57 <openstackgerrit> Merged openstack/openstack-ansible-os_keystone master: add gentoo support to keystone  https://review.openstack.org/633423
16:48:32 <miloa> I hope I did it correctly (first contribution to openstack-ansible :) )  https://review.openstack.org/639380
16:48:42 <evrardjp> miloa: thanks !
16:53:49 <mnaser> miloa: woot
16:54:05 <d34dh0r53> I have some cycles, but am a bit out of the loop, what nspawn things need work?
16:54:23 <prometheanfire> and then there were 3 https://review.openstack.org/#/q/topic:add-gentoo-support+status:open :D
16:57:29 <miloa> :)
16:58:12 <chandankumar> hey I want to bring two topics, I need help & feedback
16:59:16 <chandankumar> evrardjp: regarding how to use config_template and python-venv-build as a dependency in os_tempest
17:00:08 <chandankumar> can we ship both the modules as a pip package so that it will be installed while doing python setup.py install on os_tempest
17:00:58 <chandankumar> os that end user does not have to worry about installing additionally and modifying the ansible.cfg while consuming it
17:01:09 <chandankumar> odyssey4me: mnaser ^^
17:01:32 <mnaser> hmm
17:01:35 <mnaser> that's interesting
17:01:41 <chandankumar> here is the patches https://review.openstack.org/#/q/topic:os_tempest_deps+(status:open+OR+status:merged)
17:01:41 <mnaser> isnt that using another dependnecy management system though
17:01:58 <odyssey4me> mnaser ansible doesn't have a dependency management system though
17:02:06 <chandankumar> ansible galaxy dependency does not solve our issue
17:02:16 <odyssey4me> if you're thinking of meta-dependencies, they're badly named
17:02:24 <odyssey4me> they're more about pre-loading
17:02:58 <chandankumar> since os_tempest is used outside may be more stuff developed by OSA can be consumed, how to solve the same issue
17:03:18 <chandankumar> we need to improve the user experince to install less dependecies as possible
17:03:45 <odyssey4me> chandankumar within tripleo, won't this be handled by using rpm packages with dependencies?
17:04:29 <chandankumar> odyssey4me: currently we have not packaged it as a dependency because of several installers involved in downstream
17:04:48 <chandankumar> to deploy a single stuff
17:05:08 <chandankumar> I want something which is easy for any enduser
17:05:35 <odyssey4me> chandankumar well, perhaps evrardjp can confirm - but we could use some other meta file to express the dependency, then tripleo's installers can consume that meta file
17:05:39 <chandankumar> if they want to run os_tempest they just install os_tempest their required dependency needs to be installed
17:05:43 <odyssey4me> we've done that for docs
17:06:10 <odyssey4me> eg: https://github.com/openstack/openstack-ansible-os_tempest/blob/master/meta/openstack-ansible.yml
17:06:15 <chandankumar> odyssey4me: we need something some thing so that ansible can recognixe those roles
17:06:34 <openstackgerrit> Merged openstack/openstack-ansible-os_neutron master: [docs] Add Open vSwitch Hardware Offloading (ASAP^2) Deployment Scenario  https://review.openstack.org/563547
17:06:47 <odyssey4me> yeah, ansible doesn't have anything that solves this issue unless there's something new I don't know about
17:07:06 <evrardjp> I will read this backlog when I am done with my meeting
17:08:00 <evrardjp> mnaser: odyssey4me chandankumar there is another person that asked pip packaging of our role, ansible-hardening for example.
17:08:16 <evrardjp> I added this to the agenda of this meeting
17:08:21 <chandankumar> odyssey4me: evrardjp I think python setup.py install solves the issue,
17:08:38 <evrardjp> it's just part of the solution
17:08:49 <evrardjp> let me finish my meeting and I can explain
17:09:18 <odyssey4me> ok, what time will that be - I need to go afk for a bit
17:09:19 <chandankumar> evrardjp: config_template is just a script so shipping as a module as fixes it
17:09:46 <chandankumar> just dump it at right path so that ansible recognizes it
17:10:12 <chandankumar> it also removes copying config_templates script in ceph ansible
17:10:44 <chandankumar> it might also help in adoption of osa developed ansible modules
17:10:48 <odyssey4me> alright - I'll be back in about an hour
17:11:31 * chandankumar not sure that is the right solution
17:11:48 <arxcruz> I like the pip idea to be honest
17:12:19 <arxcruz> but would be a good use of pip for ansible role?
17:13:24 <chandankumar> odyssey4me: evrardjp mnaser arxcruz what about bringing this topic to ML may be someone has better idea?
17:13:34 <evrardjp> odyssey4me: you're right, we can have anything in meta/ folder.
17:13:34 <arxcruz> sure fine by me
17:14:09 <evrardjp> ansible doesn't have anything in itself for self resolving of dependencies outside of galaxy
17:14:15 <mnaser> #endmeeting