16:00:30 <sdake> #startmeeting kolla
16:00:30 <openstack> Meeting started Wed Aug 24 16:00:30 2016 UTC and is due to finish in 60 minutes.  The chair is sdake. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:31 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:35 <openstack> The meeting name has been set to 'kolla'
16:00:36 <sdake> #topic rollcall
16:00:37 <duonghq> o/
16:00:40 <srwilkers_> o/
16:00:41 <berendt> o/
16:00:41 <wirehead_> o/
16:00:41 <rhallisey> hey
16:00:45 <britthouser> \0/
16:00:49 <vhosakot> o/
16:01:03 <inc0> o/
16:01:23 <sdake> o\
16:01:49 <akwasnie> O/
16:02:30 <vbel> anything I could do similarly ? :)
16:02:30 <sdake> #topic announcements
16:02:40 <pbourke> o/
16:02:52 <sdake> 1. summit space will be tighter this summit
16:03:03 <sdake> there are more big tent proejcts and less space available
16:03:25 <egonzalez90> o/
16:03:48 <janki> o/
16:03:51 <sdake> we are going to spend a considerable amount of time this meeting doing our planning for summit
16:04:00 <sdake> our deadline is the 28th to submit space requirements
16:04:32 <sdake> so this is pertty much it - although we can fine tune when we find out actual space provided
16:04:41 <sdake> #topic osic cluster status
16:04:43 <wirehead_> Space requirements?  I’ll get elon musk on the line
16:04:46 <berendt> sdake which type of meetings for kolla on the last summit?
16:05:01 <rhallisey> wirehead_, nice
16:05:19 <sdake> ;-)
16:05:38 <sdake> berendt i dont understand your quesiton but i assume its related to the summit ,so we will hold off on that until the rain storm session
16:05:47 <sdake> I'll give a q uick update here
16:06:10 <sdake> basically we have *finally* debugged rally well enough that it runs perfectly in kolla
16:06:24 <sdake> we are going to be running 3 types of rally benchmarks per scenario
16:06:26 <berendt> sdake ok
16:06:41 <sdake> 192 iterations, 24 concurrency
16:06:45 <sdake> 192 iterations, 48 concurrency
16:06:49 <sdake> 192 iterations 96 concurency
16:07:13 <sdake> the running of the scripts along with capturing the data will be automated in a few hours
16:07:37 <sdake> we have 10-12 scenarios to get through and 2 platforms at minimum to work with
16:07:41 <sdake> i'd like to ssee xenial as well
16:07:46 <sdake> but that may not happen
16:07:59 <sdake> by platforms i mean ubuntu 14.04 and centos 7.2
16:08:10 <sdake> I can't automate the scenario setup
16:08:24 <sdake> so that still requires manual intervention
16:09:00 <sdake> I am creaitng a file called "NEXTSTEP" in the /root directory
16:09:10 <sdake> it will detail what he next step is for the next person to wander ont othe machine
16:09:24 <sdake> we really need to consume this gear 24 hours a day for the next 6 days
16:09:25 <pbourke> sdake: great idea
16:09:46 <sdake> so if folks could wanderon every couple of hours and see where things are at
16:09:52 <pbourke> i've been having trouble finding where people are at
16:10:03 <sdake> if the tests are done running - notify me or any of the other coordinators
16:10:19 <sdake> and we will work on getting the next scenario setup
16:10:40 <pbourke> can we get an up to date list of people interested in helping
16:10:46 <pbourke> and redistribute the tasks
16:11:01 <pbourke> as the original list is not reflecting reality and its all falling to 1-2 people
16:11:03 <sdake> i need eveyrone that knows how to deploy kolla in osic on board for helpign with the deploy process
16:11:12 <sdake> pbourke yup - have link to etherpad
16:11:19 <sdake> pbourke lets get that straightened out now
16:11:23 <pbourke> https://etherpad.openstack.org/p/kolla-N-midcycle-osic
16:11:30 <sdake> please open
16:11:48 <sdake> please only add your name if you plan to login 1-2 hours per day and kick one of the coordinators if somehting looks wrong
16:12:00 <sdake> rather every 1-2 hours
16:12:07 <pbourke> alternatively we get a list of names beside each remaining task
16:13:09 <berendt> I do not have any time left for tests this or next week
16:13:30 <sdake> line 8
16:14:46 <sdake> pbourke the problem with that is that person may not be aorund when the next test is ready tobe run
16:14:52 <sdake> rathe then tests be owned by a person
16:14:57 <pbourke> true
16:15:00 <sdake> i want  them owned by the contributors to execution :)
16:15:23 <sdake> inc0 you not in?
16:15:39 <inc0> I'm not in?
16:15:43 <sdake> not on line 8
16:16:02 <inc0> there, fixed
16:16:16 <sdake> anyone else?
16:16:51 <inc0> how do we gather results?
16:16:51 <sdake> well i you watch meeting logs late, pleae feel free to add yourself
16:16:53 <sdake> thanks
16:17:02 <sdake> inc0 i will publish instructions a soon as I have it automated
16:17:08 <sdake> the gathering part
16:17:13 <inc0> ok
16:17:43 <sdake> scale testing priority #1 for folks on this list
16:18:00 <sdake> please please - we need to finish the job on this one
16:18:13 <sdake> anyone have any further quesetions?
16:18:51 <sdake> #topic Occata summit session brainstorm
16:19:00 <sdake> inc0 mind linking your last brianstorm session on this topic
16:19:09 * inc0 looking
16:20:36 <sdake> also if your connected to the cluster atm, please make your terminal max size
16:20:43 <sdake> (i connected via tmux)
16:20:46 <sdake> i/if
16:22:00 <sdake> inc0 can't find it?
16:22:07 <inc0> not really
16:22:21 <inc0> still looking, we can start new one and I'll figure it out in the meantime
16:22:44 <sdake> #link https://etherpad.openstack.org/p/kolla-O-summit-planning
16:23:06 <sdake> inc0 whe nyo ufidn it figure out how to cut and paste it
16:23:12 <sdake> ok folks since we are starting from scratch...
16:23:16 <sdake> this will take some etime
16:26:10 <sdake> comon folks what problems do we want ot solve int he upcoming cycle
16:26:30 <sdake> lets think about what problems we have today
16:26:39 <sdake> with kolla, with how kolla is executed, etc
16:28:47 <berendt> who should add his name to the list of contributors? who is planning to join the sessions?
16:31:42 <sdake> ok folks we don't need a suepr detailed discussio nin the etherpad
16:31:47 <sdake> just a list of topics :)
16:32:02 <sdake> but if you want to have a discussion feel free :)
16:37:35 <rhallisey> https://etherpad.openstack.org/p/kolla-O-summit-planning
16:37:39 <rhallisey> Mech422, ^
16:37:51 <Mech422> oh - thanks
16:40:41 <berendt> it's enough for 2 summits, isn't it?
16:41:10 <duonghq> berendt: likely
16:45:04 <britthouser> Enough for summit plus the next "Gathering"
16:45:08 <britthouser> =)
16:46:01 <duonghq> seem good for survice even for one half more cycle?
16:48:43 <sdake> ok folks
16:48:48 <sdake> please vote at your liesure
16:48:50 <sdake> i'm going to move on now
16:49:01 <sdake> and send a note to the mailing list for folks ot vote on subjects they are interested in
16:49:09 <sdake> when we fine tune this a little further down the road
16:49:11 <berendt> bug sessions probably makes only sense as D?
16:49:20 <sdake> berendt right
16:49:30 <sdake> #topic kolla-kubernetes
16:49:45 <sdake> rhallisey mind giving status update
16:49:51 <rhallisey> sbezverk, is going much closer with nova
16:50:08 <rhallisey> so were approaching a demo soon
16:50:21 <rhallisey> one thing though, the quickstart AIO and multinode docs are not in good shape
16:51:00 <rhallisey> If you have a working env that's awesome, but we do need those working well for new contributors
16:51:26 <rhallisey> I'll go through and try and fix the AIO doc and see if I can get the multinode doc into better shape
16:51:33 <sdake> yup - docs woudl be helpful for onramp
16:51:48 <rhallisey> I think right now the price to get going is too high
16:51:57 <rhallisey> especially multinode
16:52:06 <sdake> that is why i said focus on aio first ;)
16:52:35 <sdake> any other updates
16:52:41 <rhallisey> nada
16:52:48 <sdake> i know sbezverk is blocked on a nova bug
16:52:53 <sdake> nothing at all i can do about that
16:53:01 <rhallisey> ya that bug is interesting
16:53:13 <rhallisey> assuming it is a nova bug, but idk what else it can be
16:53:21 <sdake> well could be a config problem
16:53:29 <rhallisey> right, but the config looks solid
16:53:38 <sdake> there are deprecations this cycle
16:53:49 <sdake> plus that section of the code was rewritten by danbp that is backtracing
16:54:04 <sdake> (recently)
16:54:12 <rhallisey> ya
16:54:30 <rhallisey> anyone else from the community got anything ?
16:54:30 <sdake> #topic open discussion
16:54:58 <duonghq> chant?
16:55:07 <berendt> Will we vote on the summit topics?
16:55:16 <sdake> yes rightin the etherpad
16:55:19 <sdake> look for (F)
16:55:20 <sdake> or (D)
16:55:25 <rhallisey> I hear a call for a chant
16:55:33 <berendt> I thought this is about the classifiaction of the topics?
16:55:46 <berendt> than I have to remove some Ds..
16:55:49 <sdake> nope yu ocan classify it however you want
16:56:14 <sdake> the summit is really about what the community wants
16:56:15 <berendt> yes, but if the classification includes voting..?
16:56:24 <sdake> so if you see soehting marked f and want it d, we will try to sort it out
16:56:27 <duonghq> rhallisey: n-3 is coming
16:56:30 <sdake> yes overloaded I know berendt  :)
16:56:41 <inc0> I put my "D" only on session I want
16:56:41 <inc0> sessions
16:56:57 <berendt> inc0 I put them everywhere :( I will cleanup this later.. when do we need the final list?
16:57:23 <sdake> i hae to submit by 27th a rough count of space requirements
16:57:37 <duonghq> I need some opinion on host playbook placement (in baremetal or somewhat more general)
16:57:54 <sdake> duonghq we hae a host paybook in the queue already
16:58:17 <duonghq> sdake: I see, but it is in baremetal?
16:58:41 <sdake> dont know
16:58:52 <duonghq> a bit of clumsy if it's true
16:58:53 <duonghq> IMO
16:59:06 <sdake> software dev is an iterative process :)
16:59:26 <duonghq> agree, and we're running out of meeting time?
16:59:35 <sdake> yup thanks all for coming
16:59:44 <sdake> #endmeeting