15:03:57 <bswartz> #startmeeting manila
15:03:57 <openstack> Meeting started Thu Oct 13 15:03:57 2016 UTC and is due to finish in 60 minutes.  The chair is bswartz. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:03:58 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:04:00 <openstack> The meeting name has been set to 'manila'
15:04:09 <mkoderer> hello
15:04:10 <cknight> Hi
15:04:12 <ganso> hello o/
15:04:13 <vponomaryov> hello
15:04:13 <tbarron> hi
15:04:13 <markstur> hi
15:04:13 <xyang2> hi
15:04:15 <kaisers_> hi
15:04:16 <toabctl> hi
15:04:20 <bswartz> #agenda https://wiki.openstack.org/wiki/Manila/Meetings
15:04:24 <zengyingzhe> Hi
15:04:26 <dustins> \o
15:04:30 <gouthamr> hello o/
15:04:34 <ravichandran> hello
15:05:17 <bswartz> barcelona in just 12 days!
15:05:39 <bswartz> #topic Ocata Design Summit
15:05:50 <bswartz> #link https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Manila%3A
15:06:20 <bswartz> #link https://etherpad.openstack.org/p/manila-ocata-design-summit-topics
15:06:43 <bswartz> sorry it's been slow going pulling together the design summit sessions
15:07:06 <bswartz> I've been without email due a rather spectacular failure at my email provider
15:07:36 <bswartz> I've been trying to find leaders for the discussion topics
15:07:45 <bswartz> ganso: I hope you are okay leading the discussion on jobs
15:08:16 <bswartz> and I'm hoping either mkoderer or dmellado will lead the Tempest session
15:08:34 <dmellado> bswartz: we'll do
15:08:42 * dmellado just needs to check the schedule
15:08:45 <bswartz> both of you? or just dmellado
15:09:01 <mkoderer> I can lead or co-lead
15:09:02 <dmellado> bswartz: btw, besides that, there will be a session on the plugins, most probably
15:09:08 <dmellado> mkoderer: let's co-lead that
15:09:10 <bswartz> we want dmellado and mkoderer at that session so we can move it if there's a conflict
15:09:21 <dmellado> +1 from my side ;)
15:09:23 <dmellado> thanks bswartz
15:09:32 <bswartz> please lmk if you have any schedule problems
15:09:38 <dmellado> will do!
15:09:50 <ganso> bswartz: sure :)
15:09:51 <bswartz> ganso: can you confirm about the jobs session?
15:09:52 <mkoderer> bswartz: I hope it's not conflicting with my presentations :(
15:09:55 <ganso> bswartz: yes
15:09:55 <mkoderer> sure we'll do
15:09:59 <bswartz> k
15:10:06 <bswartz> that just leaves the HA topic
15:10:30 <bswartz> I don't know who is the peach color on the etherpad
15:10:46 <bswartz> but HA got a ton of votes so we will cover it
15:11:24 <bswartz> I can lead that topic but I wanted to know if anyone else had an agenda related to HA
15:11:41 <bswartz> I think most of the pressure for HA support is coming from the distros
15:11:51 * bswartz glances at tbarron
15:12:06 <mkoderer> bswartz: and people who run it in production! ;)
15:12:27 <tbarron> hi, yes we would like to be able to run share service active-active but
15:12:30 <bswartz> mkoderer: do you have active/active HA working for other services?
15:12:33 <tbarron> ocata is a very short cycle
15:13:03 <tbarron> fixing race conditions is a pre-requisite
15:13:12 <mkoderer> bswartz: we have a kubernetes deployment.. it takes care automagically :)
15:13:17 <bswartz> okay we're on the same page then
15:13:42 <bswartz> mkoderer: does the magic actually work?
15:13:56 <tbarron> and cinder not doing active-active volume service yet relieves some pressure downstream
15:13:59 <mkoderer> tbarron: we should spend some effort in thinking about testing - how we indentify all race conditions
15:14:07 <bswartz> which services are able to run in A/A configuration without opening up possibilities for races?
15:14:07 <mkoderer> bswartz: sometimes
15:14:08 <toabctl> mkoderer, but kubernetes can't make manila-share active/active
15:14:11 <tbarron> mkoderer: ++
15:14:22 <mkoderer> tbarron: no it can't but it's less painful
15:14:35 <bswartz> toabctl: that's what I was going to say
15:14:58 <toabctl> so it's less painful than pacemaker active/passive but the same result in the end
15:15:00 <bswartz> you can run the services A/A but it might be way more dangerous than running A/P
15:15:57 <bswartz> okay well I'm sure that will be a lively session
15:16:03 <bswartz> and it looks like I'm still leading it
15:16:22 <bswartz> now that we have sessions, the next step is putting up the etherpads
15:16:44 <bswartz> I'll do that, and then contact session leaders to populate the etherpads with their agenda
15:17:04 <bswartz> anything else about the design summit?
15:17:22 <tbarron> are you posting a list of topics for the contributor's meetup?
15:17:33 <ganso> tbarron: it is in the etherpad
15:17:44 <tbarron> ganso: kk
15:17:44 <ganso> tbarron: top section
15:17:45 <bswartz> tbarron: we'll cover the "remaining" topic there
15:17:56 <bswartz> tbarron: I've started sorting the topics by vote count
15:18:06 <bswartz> yes they're in the etherpad
15:18:21 <bswartz> and the meetup will get its own etherpad which people can add to
15:19:19 <bswartz> #topic open discussion
15:19:28 <bswartz> okay that was the only agenda item
15:19:35 <ganso> can we merge https://review.openstack.org/#/c/375164/ ?
15:19:36 <bswartz> anything else we should discuss today?
15:20:09 <tbarron> ganso: +1
15:20:25 <bswartz> ganso: you asking for reviews or are you asking if the quiet period is ended?
15:20:47 <ganso> bswartz: asking for reviews, I am assuming the quiet period is ended
15:20:51 <bswartz> because the quiet period has been over officially since last week
15:20:53 <bswartz> yeah okay
15:20:53 <vponomaryov> ganso: he just wants get it merged ))
15:21:01 <bswartz> :-)
15:21:27 <ravichandran> )
15:21:45 <bswartz> okay I guess it's a short meeting
15:21:47 <tbarron> bswartz: mention the PTG so people can start travel plans/budgets?
15:21:47 <markstur> Are we meeting next week?
15:22:01 <bswartz> we'll meet one more time next week and the obviously there will be no meeting during the design summit
15:22:13 <bswartz> tbarron: oh thx
15:22:17 <tbarron> bswartz: some teams are doing virtual only is why i bring it up
15:22:27 <bswartz> So I think we should plan to participate in the PTG
15:22:39 <bswartz> it is replacing the design summit after all
15:22:43 <ganso> cknight: thanks!
15:22:47 <toabctl> bswartz, +1
15:22:48 <xyang2> bswartz: we have so many conflicts with Cinder sessions this time at the summit
15:22:50 <cknight> ganso: np
15:23:01 * markstur forgets what PTG acronym stands for
15:23:05 <bswartz> I don't know what to expect but I not participating seems like a missed opportunity
15:23:12 <vponomaryov> markstur: project team gathering
15:23:13 <bswartz> PTG = project team gathering
15:23:28 <bswartz> #link http://www.openstack.org/ptg
15:23:34 <markstur> the "gathering" is catchy.  PTG not-so-much
15:24:04 <bswartz> the details are TBD (thanks to my email SNAFU) but everyone should plan on attending that just like you would a design summit
15:24:12 <bswartz> markstur: ikr
15:24:36 <bswartz> what I don't know so much about will be boston
15:24:46 * markstur googled for ikr
15:24:59 <bswartz> boston will call in the middle of the pike release and AFAIK there won't be so much space for developery stuff
15:25:05 <bswartz> s/call/fall/
15:25:16 <xyang2> bswartz: will the manila and cinder sessions happening in parallel at PTG?
15:25:33 <bswartz> xyang2: no idea -- I really hope not
15:26:19 <bswartz> xyang2: I'll take an action to find out more and make our plans official
15:26:36 <xyang2> bswartz: thanks
15:26:49 <bswartz> hopefully we'll have a clear plan by the the design summit
15:27:05 <markstur> Wondering if "mid-cycles" will happen in Boston.  I think some will.
15:27:41 <bswartz> markstur: that's been suggested but it's totally unclear if that will make sense
15:27:51 <zengyingzhe> bswartz: will all of the manila sessions webcast?
15:28:03 <bswartz> the whole point of separating the summit and the PTG is so that people like me can attend both
15:28:20 <bswartz> if we have a midcycle in boston then we will fail as that goal
15:28:25 <bswartz> s/as/at/
15:29:11 <bswartz> zengyingzhe: we will setup a hangout/webex as we have before, but we don't have anyone savvy enough to record the sessions like cinder does
15:30:06 <bswartz> alright anything else?
15:30:28 <bswartz> thanks everyone
15:30:31 <bswartz> #endmeeting