16:01:45 <odyssey4me> #startmeeting OpenStack-Ansible
16:01:45 <openstack> Meeting started Thu Apr  7 16:01:45 2016 UTC and is due to finish in 60 minutes.  The chair is odyssey4me. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:01:46 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:01:49 <openstack> The meeting name has been set to 'openstack_ansible'
16:01:54 <odyssey4me> #topic Agenda & rollcall
16:02:15 <spotz> \o/
16:02:27 <v1k0d3n> o/
16:02:35 <odyssey4me> #link https://wiki.openstack.org/wiki/Meetings/openstack-ansible#Agenda_for_next_meeting
16:02:45 <eil397> \o
16:03:02 <jmccrory_> o/
16:03:04 <evrardjp> hi
16:06:47 * mhayden woots
16:08:18 <odyssey4me> Alright, we had no action items from last week so let's move to discussion topics.
16:08:28 <odyssey4me> #topic Release notes in the IRR's
16:08:35 <odyssey4me> palendae any updates?
16:08:45 <palendae> Nope, been working on testing liberty upgrades all week
16:09:21 <odyssey4me> alright, let me at least set an action item to instrument all the repositories for release notes
16:09:40 <odyssey4me> #action odyssey4me to instrument all repositories for release notes
16:10:11 <odyssey4me> do you need help with anything or would you like to raise anything related to the topic?
16:11:02 <palendae> I don't have much to raise at the moment
16:11:15 <odyssey4me> ok, we'll move on then
16:11:25 <odyssey4me> #topic Newton Summit Planning
16:12:21 <odyssey4me> The schedule is up. I'm busy populating the details into it. It should be done early next week.
16:12:35 <odyssey4me> I'll put a link to the filtered schedule up asap.
16:12:45 <odyssey4me> Does anyone have any summit related questions or comments?
16:13:12 <mattt> any way for those of us not at the summit to participate in anything?
16:13:24 <evrardjp> good question
16:13:40 <spotz> I wonder if we could stream via vidyo on a laptop?
16:14:29 <odyssey4me> well, we did try that at the mid-cycle and it wasn't great
16:14:31 <mattt> yeah you don't want it to distract from the in-person stuff as that time is precious, but if there is a mechanism it'd be great for those of us not there to join in on
16:14:34 <spotz> odyssey4me I need to see my whole schedule but would like to make the doc sessions, any way to coordinate?
16:14:47 <odyssey4me> also we don't really have the same facilities available at the summit
16:14:54 <cloudnull> o/
16:15:01 <spotz> odyssey4me And it depends on network:(
16:15:14 <mattt> yeah if it's a hurdle then i wouldn't worry about it
16:15:24 <odyssey4me> so I think the best way to facilitate is to work through each topic's etherpad beforehand and discuss with anyone's who's going so that your views are well represented
16:15:38 <cloudnull> odyssey4me: maybe we can do it w/ hangouts live + IRC
16:15:55 <cloudnull> re: remote participation
16:16:19 <odyssey4me> The sessions are 40m so there's not even much time to try and use IRC to discuss, but we can try and ensure that some people are around on IRC and can therefore interact with anyone who's around
16:16:28 <mattt> odyssey4me: fair enough
16:16:48 <evrardjp> irc isn't gonna work I think
16:17:02 <odyssey4me> The session times due to time zone differences will also make it a bit hard for anyone outside of the US to participate
16:17:24 <odyssey4me> #action odyssey4me to complete uploading session details and publish a link for review
16:17:30 <evrardjp> I agree with odyssey4me : let's prepare beforehand
16:17:43 <odyssey4me> for now the session list is https://www.openstack.org/summit/austin-2016/summit-schedule/#day=2016-04-27&summit_types=2&tags=3542
16:17:57 <odyssey4me> although I see that some other stray sessions are in the list - not sure what's going on there
16:18:09 <odyssey4me> that also seems to be missing some sessions
16:18:22 <stevelle> as much as possible, having an outline and related reading items linked in the etherpads for each session seems important so folks can choose sessions and prepare to contribute in them
16:18:33 <mhayden> mattt: i could bring a better quality webcam to the summit and try to use it
16:19:47 <odyssey4me> aha, this is better: https://www.openstack.org/summit/austin-2016/summit-schedule/global-search?t=OpenStackAnsible
16:19:55 <mattt> mhayden: sounds like it may not be worth it, and you don't want in-person time wasted fiddling w/ cams, networks, etc.
16:20:11 <spotz> fishbowl goes right up to my session but I'll come for the start
16:20:13 <mhayden> mattt: i'll do it for you, though
16:20:23 <mattt> mhayden: you da bayst
16:20:34 <odyssey4me> yeah, what stevelle said - please ensure that you prepare yourself for each session based on the outline in the session details
16:20:57 <odyssey4me> everyone needs to come with ideas and ideally PoC patches prepared
16:21:15 <odyssey4me> with the limited time for each session we need to try and make the most of the in-person time
16:21:43 <spotz> I need a clone on Wednesday:(
16:22:05 <odyssey4me> I'm putting them in the order we decided on here: https://etherpad.openstack.org/p/openstack-ansible-newton-summit
16:22:06 <evrardjp> spotz only one ?
16:22:25 <odyssey4me> can anyone see any specific clashes with other sessions that means we should switch things around a bit?
16:22:34 <spotz> evrardjp Just one so far
16:22:57 <stevelle> I would like to ask we consider moving dynamic inventory earlier
16:23:20 <odyssey4me> yeah, I thought about that - maybe the first session on Wednesday?
16:23:28 <stevelle> that works
16:24:19 <odyssey4me> maybe switch it up with the role documentation session?
16:24:40 <stevelle> the 9:50 slot is ideal for me, personally
16:24:46 <stevelle> to do inventory
16:24:50 <spotz> Just don't put docs middle of the day on Wednesday and I'll make it work
16:25:32 <odyssey4me> ah, I meant the first on Thu - not Wed
16:25:52 <stevelle> any slot thurs before lunch works
16:25:58 <odyssey4me> spotz the suggested time for the docs session is 4:30-5:10 or the later one
16:26:07 <odyssey4me> (on Wed)
16:26:39 <spotz> That'll work, I can do video's of the hands-ons I wanted to go to but can't miss the session I'm running:)
16:28:06 <odyssey4me> spotz which works better - the 4:30-5:10 or the 5:20-6:00?
16:28:31 <mhayden> i'm good with either of those docs-wise
16:29:04 <spotz> odyssey4me Either will work:)
16:29:36 <odyssey4me> ok, I'll put some thought into the demands of the other sessions and put a suggested schedule down
16:30:50 <odyssey4me> anything else from anyone?
16:30:57 <spotz> appreciate it odyssey4me!
16:31:48 <odyssey4me> #topic Release Planning and Decisions
16:32:43 <odyssey4me> so due to our current project tagging, we didn't get the chance to go through a release candidate process - so Mitaka is effectively released
16:32:59 <odyssey4me> please keep testing to identify any bugs\
16:33:21 <spotz> So we're bug fixing and newton?
16:33:25 <odyssey4me> also keep a lookout for backports or patches to the stable/mitaka branch - I expect that we'll be doing quite a few of them all the way up to Newton-1
16:34:04 <odyssey4me> I've applied to change the project tag to follow the releases and will discuss what that means at the summit.
16:34:20 <odyssey4me> spotz yeah, master is on Newton already
16:34:39 <spotz> nice:)
16:34:59 <odyssey4me> we have some patches that need herding or votes: https://review.openstack.org/#/q/project:%255Eopenstack/openstack-ansible.*+status:open+branch:stable/mitaka
16:36:16 <odyssey4me> it looks like the upstream projects are pretty much done at RC3, but I'd like to get those patches merged so that we can tag 13.0.1 as the finalised release including any additional role patches needed
16:37:10 <stevelle> looks like we have some gate instability issues right now too
16:37:45 <odyssey4me> stevelle yeah, some of the providers are quite problematic although I haven't been digging into those failures in detail
16:38:01 <odyssey4me> if you have a gap to do so to try and figure out whether there are other problems then that'd be appreciated
16:38:27 <evrardjp> let me guess, ovh apt issues
16:39:04 <odyssey4me> evrardjp for the most part we're using the infra provided apt/pypi/pip repositories which are localised per provider/region so we shouldn't be
16:39:16 <odyssey4me> if that hasn't been done in the role, then that's a fix-up needed for sure
16:39:22 <evrardjp> indeed, it's not what I see on the first ones
16:39:47 <odyssey4me> I think that the galera extra download bits is hurting the galera_server role success
16:39:56 <stevelle> ^
16:40:36 <odyssey4me> those aren't mirrored, so we either need to figure out something better or make another plan
16:40:42 <stevelle> so many galera_server timeouts, but that reflects something delaying those tests
16:41:00 <evrardjp> pkg-query: package 'mariadb-galera-server-10.0' is not installed and no information is available
16:41:03 <stevelle> It seems like there are a few issues in that role we might identify
16:41:53 <odyssey4me> yeah, that role does a lot of things - we might have to pare it down a little or figure out another way to test what it's testing
16:42:01 <evrardjp> that's a discussion we can have outside the meeting right?
16:42:06 <odyssey4me> but ideally I'd like to identify real problems and resolve them
16:42:12 <odyssey4me> yeah, we can do that
16:43:33 <odyssey4me> are there any issues with the Kilo/Liberty branches that should prevent a fresh tag?
16:44:40 <odyssey4me> it looks like https://review.openstack.org/301283 / https://review.openstack.org/302333 / https://review.openstack.org/280844 need review for kilo
16:45:19 <odyssey4me> and there are some patches in review for liberty: https://review.openstack.org/#/q/project:%255Eopenstack/openstack-ansible.*+status:open+branch:liberty
16:47:04 <odyssey4me> as the release team is pretty much on skeleton crew until after the summit, I'm not sure that our tags will be done - but I'll ask
16:47:39 <odyssey4me> #topic Open discussion
16:47:48 <odyssey4me> alright - we have 10 mins for open discussion
16:47:54 <odyssey4me> anyone got anything to discuss or raise?
16:51:10 <evrardjp> nothing right now, except thanks for the meeting
16:52:57 <odyssey4me> alright, as there's nothing else - thank you all for attending!
16:53:15 <odyssey4me> #endmeeting