16:01:58 <mnaser> #startmeeting openstack_ansible_meeting
16:01:59 <openstack> Meeting started Tue Feb  5 16:01:58 2019 UTC and is due to finish in 60 minutes.  The chair is mnaser. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:02:00 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:02:00 <mnaser> #topic rollcall
16:02:02 <cloudnull> o/
16:02:03 <openstack> The meeting name has been set to 'openstack_ansible_meeting'
16:02:08 <cloudnull> presente!
16:02:13 <jamesdenton> o/
16:02:54 <jrosser> o/
16:03:10 <prometheanfire> o/
16:05:31 <mnaser> #topic last week highlgihts
16:05:34 <mnaser> #topic last week highlights
16:05:47 <mnaser> https://review.openstack.org/#/q/projects:openstack/openstack-ansible+is:merged
16:06:10 <mnaser> looking over merged code over the past week, looks like mostly master branch merges, a bunch of cool os_tempest work
16:06:19 <mnaser> and some other stuff around nspawn
16:06:50 <mnaser> anyone else want to highlight anything in specific this week?
16:07:01 <jrosser> we are a little closer to aarch64, we got fixed packages for haproxy landed in bionic -proposed repo this week
16:08:03 <jamesdenton> I'll prob be working on getting other deployment scenarios for MNAIO, esp OVS
16:08:17 <mnaser> nice
16:08:29 <mnaser> arm gating would be really cool, and thats' awesome, i should hack around mnaio at some point
16:08:48 <jrosser> we need aarch64 wheels on the mirror - thats the next bigge
16:08:57 <mnaser> yeah, i saw that convo over -infra
16:08:57 <cloudnull> I recently just updated the plugins to pull in changes for config_template into our main plugins repo. is there a plan in place to switch over to that ?
16:09:13 <cloudnull> https://review.openstack.org/#/c/634857/
16:09:32 <cloudnull> i remember evrardjp working on that a while back
16:09:37 <jrosser> mnaser: should i prod ianw about that, is that the correct approach to move that aarch64 on?
16:09:44 <cloudnull> however IDK what the state is currently ?
16:09:57 <mnaser> jrosser: i think he is the infra arm resident expert
16:10:07 <jrosser> ok, cool, i will follow that up
16:10:47 <mnaser> cloudnull: yes, i think we should get rid of that and use the one that's on it's own
16:10:55 <cloudnull> ++ agreed
16:11:18 <mnaser> it's a significant amount of work involved i think, updating all ansible-role-requirements across all roles before ripping it out
16:11:18 <jrosser> iirc evrardjp and odyssey4me were cooking up a plan for how to do that withoug breaking everything
16:11:31 <cloudnull> ^ ++
16:11:33 <mnaser> unless we actually jump to using integrated repo for testing, then it might be easier
16:11:43 <mnaser> i think both aren't present at the moment so we may keep this to next week
16:11:47 <cloudnull> I'm not sure what the best plan of attack is
16:12:40 <openstackgerrit> James Denton proposed openstack/openstack-ansible-os_neutron stable/rocky: Fix the subprocess invocation of neutron-l3-agent  https://review.openstack.org/634968
16:13:01 <mnaser> let's wait to hear from them
16:13:13 <mnaser> also, another topic, i sent out an eamil about a bug squash slash hackday with zero response on the ML
16:13:33 <mnaser> i'm wondering if folks just don't follow the ML as much (totally ok, there is a lot of email) or if it's more of a "not possible for us"
16:14:08 <jamesdenton> I filter the ML and have a habit of not checking the folders
16:14:25 <cloudnull> ^
16:14:50 <jamesdenton> I am open to a bug squash and pretty flexible on date/time.
16:14:55 <jrosser> i have some new people on my team and would be able to carve out a day for this
16:15:43 <cloudnull> ++
16:15:53 <mnaser> no problem, is there any specific timeframe that works better for some folks in terms of a day of week?
16:16:03 <mnaser> someone proposed a '24 hour' thing which seemed cool given how we're pretty distributed
16:16:29 <jamesdenton> sounds good
16:16:38 <jrosser> fridays are not so good for me
16:16:59 <jamesdenton> Wednesday(s)?
16:17:13 <archklikk> Hello guys, im trying to deploy an openstack build with ansible but i'm getting an error while running the "setup-hosts" playbook. At the "lxc_container_Create : Create container (dir)" task some of the containers are failing to start. One of them says "instantiate_veth: 172 Operation not permitted - Failed to attach "be909e25_eth1" to bridge "br-mgmt". What can be the problem?
16:17:25 <mnaser> archklikk: we're in an openstack ansible meeting, we can look into this shortly after :)
16:17:41 <mnaser> how does wednesday sound jrosser (and cloudnull maybe?)
16:18:14 * cloudnull checks cal
16:18:27 <jrosser> weds in general is fine
16:18:42 <jrosser> tomorrow, specifically not so good :)
16:18:46 <cloudnull> ^
16:18:59 <cloudnull> but wednessday/thursday is generally good
16:20:23 <mnaser> yeah that's already last minute
16:20:36 <mnaser> okay, so i'll aim for wednesday next week for a bug squash day
16:20:47 <mnaser> we can even discuss options of high bandwidth methods of communication
16:21:07 <cloudnull> excellent
16:21:28 <cloudnull> I have zoom available and can open it up to folks
16:22:14 <mnaser> done and announced
16:22:24 <mnaser> samesies
16:23:09 <mnaser> cools
16:23:30 <mnaser> next up, making meeting more like office hours, we brought it up last week and it feels like we're getting a bit more traction in our meetings with it that way
16:24:19 <cloudnull> just informed my team that we're doing bug smash things next Wednesday :)
16:24:30 <mnaser> yays
16:25:45 <mnaser> any thoughts about the office hours rather than meeting
16:27:18 <jamesdenton> not familiar with the office hours....
16:27:37 <jrosser> ^ same, not sure really what the choice is between
16:27:51 <jrosser> or if we just need to iterate the format of the meeting in general
16:28:23 <mnaser> office hours would be more like
16:28:25 <mnaser> no specific agenda
16:28:38 <mnaser> just a time where we all open in our calendars to be available at
16:28:49 <mnaser> so we can discuss all sorts of stuff like this in a more sync manner
16:29:05 <mnaser> office hours can be open for an entire hour, even if we're not really discussing much rather than a meeting that's "ok we're done"
16:30:53 <jamesdenton> sure, i guess? The format doesn't make much difference to me as long as we get done what needs to get done
16:31:14 <mnaser> alright, fair enough, we can discuss more in depth later..
16:31:24 <mnaser> (skipping bug triage because next week we'll clear all this stuff out)
16:31:29 <mnaser> #topic open discussion
16:31:36 <mnaser> anyone has anything to bring up?
16:31:45 <prometheanfire> not really
16:32:18 <prometheanfire> gentoo stuff will need another dib release to get the infra image fixed for the systemd bug, but that's it (and I'll bug them for it)
16:32:33 <mnaser> woot
16:32:36 <jrosser> how are we doing on the goals for Stein?
16:32:37 <mnaser> then we can create our OSA distribution
16:32:38 <mnaser> :)
16:32:51 <mnaser> jrosser: are you talking about community goals or the things we aimed to accomplish discussed at the ptg
16:33:22 <mnaser> ptg discussions are https://etherpad.openstack.org/p/osa-stein-ptg
16:33:30 <jrosser> perhaps a bit of both, seems like there is probably more to do than we have effort for right now?
16:33:43 <mnaser> i agree.  so there's a few things
16:33:57 <mnaser> Simplifing release: evrardjp picked this up and put up a few reviews but i think it's a wip that he's working on
16:34:31 <mnaser> Moving towards nspawn: what's needed? -- i have been putting efforts but i have been blocked, i'm hoping for help from cloudnull on this, right now, ./run_tests.sh aio_nspawn will fail in tempest because the flat network doesnt work
16:34:53 <mnaser> bridging a macvlan interface seems to work but it doesn't seem to be functional (aka, data doesnt land on the interface)
16:35:11 <mnaser> so we either revert to using a normal bridge or use a dummy interface for the 'vlan' network (aka eth12 in old world)
16:35:24 <mnaser> or i'd need a bit of help in getting the last bits of nspawn working in the gate
16:35:46 <cloudnull> Im around today if we want to hack on that some ?
16:35:53 <prometheanfire> mnaser: I've been targeting nspawn, after cloudnull's patch merged it seems to be working for me
16:36:03 <prometheanfire> but my test is just keystone
16:36:12 <mnaser> yeah i'm working with the integrated repo
16:36:25 <mnaser> it's more of a neutron/macvlan/bridge thing
16:36:46 <mnaser> cloudnull: if you have time, i can show you my findings and leave the vm with you because i've exhausted my knowledge domain at least :<
16:37:48 <mnaser> and we're very very very close to working upgrade jobs, https://review.openstack.org/#/c/627782/ fails in the second tempest in some workspace related thing that guilhermesp has been iterating on recently
16:37:55 <prometheanfire> nice
16:38:27 <mnaser> the upgrade does complete, just the tempest stuff seems to be acting weird, but yeah, it is great progress
16:38:51 <mnaser> i think those were the big 3 things for that we mainly talked about, unless i'm missing something
16:39:11 <jrosser> mnaser: what would you like to land for S for nspawn, feels like we are behind what that describes
16:39:26 <jrosser> ^what the etherpad describes
16:39:41 <prometheanfire> mnaser: question about py3 switch, where is OSA there?
16:39:47 <mnaser> jrosser: yes, we are, i've put in efforts a few times to get nspawn going but i keep getting blocked
16:39:57 <prometheanfire> and ya, is nspawn default in S?
16:40:15 <mnaser> i'd love to hit that goal if we can our gating working
16:40:27 <mnaser> it looks like it's more of a gating issue rather than an nspawn issue given folks have been using it
16:41:04 <mnaser> i'm hoping i can get some hacktime with cloudnull (or if anyone else can help, just spin up a vm and `./run_tests.sh aio_nspawn`)
16:43:03 <cloudnull> I also have test VMs I can donate to the cause
16:43:22 <cloudnull> and would be happy to join a hangout, zoom, tmux, to work through the issues
16:43:54 <prometheanfire> always a helper
16:43:56 <mnaser> i'll take you up on that later today if you're free cloudnull -- i think i'm really like 1 config option away from it i feel
16:44:08 <cloudnull> ++
16:44:30 * cloudnull gotta run to a meeting. bb in an hour
16:44:50 <mnaser> cool, i'll try to jump into figuring out the upgrade jobs more in depth as well and follow up with evrardjp about the release stuff
16:44:54 <mnaser> anyone else have anything for discussion?
16:45:37 <prometheanfire> the py3 question?
16:45:41 <prometheanfire> 10:41 <  prometheanfire > mnaser: question about py3 switch, where is OSA there?
16:45:52 <mnaser> da heck
16:45:55 <mnaser> i swear i wrote a reply to that
16:46:19 <mnaser> prometheanfire: all projects were lobbed in there, we're likely not going to be doing that until our deployment targets supposed python3 well and natively
16:46:40 <prometheanfire> kk
16:46:45 <mnaser> we've switched most of our non-functional jobs to py3 like docs and so on, but eventually hopefully once rhel8 is out we can start doing all the python3 stuff
16:46:51 <mnaser> so hopefully that works out for the T cycle cleanly
16:47:07 <prometheanfire> ya, with py2 dying
16:47:32 <mnaser> yep, kill it with fire
16:47:43 <mnaser> also, having projects with py3 out for a cycle will help us make sure that everything is already working
16:47:52 <mnaser> and with the work odyssey4me has put in recently it puts us in a good place with python_venv_build
16:48:14 <prometheanfire> cool
16:48:33 <mnaser> thanks for bringing that up prometheanfire
16:48:54 <mnaser> anything else? :>
16:49:03 <prometheanfire> non
16:49:12 <jamesdenton> i'm good
16:50:26 <guilhermesp> for the upgrade job there is a way suggested by odyssey4me for this https://review.openstack.org/#/c/627782/6
16:50:41 <guilhermesp> that is deploy an aio and run the gate-check script
16:50:50 <guilhermesp> but I think I'd need someone of tempest close to help with this
16:51:11 <mnaser> cool, we can chat over this as well in a bit with some of teh tempest experts :)
16:51:13 <mnaser> thanks everyone
16:51:14 <mnaser> #endmeeting