16:00:18 <inc0> #startmeeting kolla
16:00:19 <openstack> Meeting started Wed Feb  1 16:00:18 2017 UTC and is due to finish in 60 minutes.  The chair is inc0. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:20 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:22 <openstack> The meeting name has been set to 'kolla'
16:00:31 <inc0> #topic rollcall - w00t please
16:00:34 <duonghq> woot o/
16:00:36 <gema> o/
16:00:37 <inc0> you know what to do;)
16:00:38 <egonzalez> woot o/
16:00:44 <sp__> woot o/
16:00:54 <vhosakot> o/   (sorry I missed the past 3 meetings as I had conflicts with other meeting)
16:00:58 <vhosakot> w00t
16:01:03 <zhubingbing__> o/
16:01:05 <pbourke> w00t
16:01:09 <Jeffrey4l_> o/
16:01:09 <inc0> vhosakot, no problem, glad to have you back
16:01:12 <zhubingbing__> o/
16:01:27 <vhosakot> thanks inc0 :)
16:01:49 <SamYaple> o/
16:01:49 <sayantani01> Woot
16:02:22 <inc0> #topic announcements
16:02:48 <inc0> 1. ocata-3 was tagged, now we're in feature freeze and stabilizing our release
16:03:03 <inc0> please everyone focus on testing deploy and upgrades
16:03:12 <zhubingbing__> ok
16:03:19 <inc0> our release is early march
16:03:22 <qwang> o/
16:03:25 <hrw> o/
16:03:27 <sp__> ohhk
16:03:39 <inc0> any community announcements?
16:03:42 <mliima_> \o
16:03:57 <inc0> guess not
16:04:05 <inc0> #topic ptg schedule
16:04:07 <SamYaple> im getting fiber
16:04:12 <SamYaple> thats my announcement
16:04:15 <inc0> congrats SamYaple
16:04:20 <duonghq> nice SamYaple
16:04:25 <pbourke> seed boxes available from SamYaple
16:04:40 <SamYaple> starting at $250 a month
16:04:51 <inc0> soo we need to plan for PTG
16:04:56 <pbourke> contact him by phone directly, his hours are between 1am and 3am
16:05:12 <inc0> we are left with full authority how we want to split the sessions
16:05:21 <inc0> we have room and 2 days
16:05:34 <inc0> so we can have usual 45-15min session/break
16:05:41 <inc0> or change it in any direction
16:05:51 <sdake> o/
16:06:21 <inc0> #link https://etherpad.openstack.org/p/kolla-ocata-ptg this is our session list
16:06:36 <krtaylor> o/
16:06:40 <inc0> #link https://etherpad.openstack.org/p/kolla-pike-ptg-schedule lets put actual schedule here
16:07:35 <sdake> inc0 i like the 40 minut esessiosn with 10 or20 minutes breaks
16:07:37 <sdake> keeps people fresh
16:07:54 <sdake> do you know the hours of the ptg so we can make a rough schedule of the times and then sort out what goees where enxt?
16:08:06 <inc0> I'm not sure how lunch will look like so we probably just push sessions in time of lunch
16:08:06 <hrw> and enough time to discuss after talk + manage to get to next one
16:08:10 <inc0> I'll figure that one out
16:08:19 <sdake> hey hrw
16:08:25 <sdake> thanks for getting that answered inc0
16:08:25 <inc0> sdake, we can start/end however we want afaik
16:08:46 <inc0> hrw, well, all our talks are in same room
16:08:50 <sdake> inc0 I know we can manage our own schedule I wasn't sure if the facilities at a start or end time
16:08:54 <hrw> inc0: ;)
16:08:54 <inc0> we just get a room
16:09:09 <sdake> right- although if we don't set a strict schedule we will overrun topics
16:09:12 <inc0> and if you want to move to different room, I can't promise that our sessions will be in sync
16:09:30 * hrw is not going to PTG
16:09:35 <sdake> and some topics will get less time while others will get more
16:09:40 <inc0> sdake, I asked ttx and he's not sure either, but that's a hotel so I don't expect to have too much problems either way
16:09:42 <gema> not sure where exactly to add the ARM64 topic
16:09:46 <gema> under deliverable?
16:09:47 <inc0> not like we want to stay for hours
16:09:51 <inc0> into night
16:09:57 <sdake> inc0 cool - so 9am-5pm then?
16:10:13 <sdake> gema we are not to that point in our agenda yet :)
16:10:21 <gema> sdake: lol, ok
16:10:24 <inc0> sdake, how about we plan for 8 sessions a day and I'll figure out hours when we get lunch info and stuff?
16:10:29 <gema> I was looking at the PTG list of topics :D
16:10:29 <sdake> gema im not sure if that is on the agenda -a t present we are talking about ptg agenda
16:10:36 <sdake> inc0 cool
16:10:43 <sdake> inc0 we can adjust from there
16:11:01 <sdake> icn0 before making the final schedule are we going to vote or make up the voting or what on the sessionss we wnt to have
16:11:09 <inc0> gema, frankly I'd keep arm out of full ptg agenda, unless you feel it's 40min worth of talking
16:11:13 <sdake> (not beinga pita, just want to understnad how we transfer the  first etherpad to the second)
16:11:42 <gema> inc0: probably won't need 40 mins, I will grab you all one by one at coffee time and ask questions, you are right :D
16:11:49 <inc0> I'd like to have plenty of time for random open convos there
16:12:00 <hrw> inc0: do s/arm64/all-non-x86-archs/ and it makes sense
16:12:38 <inc0> hrw, well, yes and no, it will be same thing with more. Once we'll figure out how to add arm
16:12:41 <inc0> with gema
16:12:42 <hrw> inc0: there is ppc64le patch for kolla already in review. I have ppc64le+aarch64 one based on review one
16:12:48 <inc0> we can add stuff like that later too
16:13:35 <sdake> we have 16 time slots, lets select which of the 15 we want
16:13:37 <sdake> 16 rather
16:13:39 <inc0> we'll talk about this, I promise, just can't promise we'll make full fledged session out of it
16:13:46 <inc0> schedule is pretty tight as it is;)
16:14:33 <sdake> i am going to ordered number the first etherpad only for counting purposes
16:14:44 <inc0> I'd like to have split between kolla + kolla-ansible / kolla-k8s in about 50:50 if you agree
16:14:54 <sdake> gema add to end of the ptg schedule in the firstetherpad so we can see how many sessions we have
16:15:13 <inc0> that will put our stable deliverables at a bit of disadvantage, but I just feel we need more design time for k8s
16:15:16 <gema> the first etherpad being the ocata one?
16:15:31 <inc0> gema, yeah, I messed up naming:P
16:15:39 <sdake> you mean 50% for kolla+kolla-ansible and 50% for kolla-k8s?
16:16:05 <inc0> yes
16:16:19 <inc0> we can do 1 day for k8s and 1 day for ansible
16:16:22 <inc0> + docker
16:16:38 <inc0> so people with only one interesest can work their schedule better
16:16:57 <inc0> although I'd expect most people from kolla-k8s to be interested in at least kolla images;)
16:17:09 <inc0> thoughts guys? agree? disagree?
16:17:51 <gema> +1
16:17:55 <sdake> agreed inc0
16:18:05 <egonzalez> +1
16:18:06 <srwilkers> +1
16:18:13 <sdake> ok - so we have 29 sessions planned and 18 slots
16:18:18 <inc0> ok, so let's make Monday kolla-k8s and Tue kolla-ansible
16:18:21 <zhubingbing__> +1
16:18:24 <sdake> we either need to select out 11 sessions or select in 18 :)
16:18:31 <sp__> +1
16:18:34 <inc0> since cross-project will be more interested in latter
16:19:04 <sdake> some of these may be duplicates as well
16:19:13 <sdake> inc0 i liked thevoting you did in the past on the session interest
16:19:37 <sdake> inc0 although we can't wait 2 weeks for results, woudl you be willing to set that up with a short timer?
16:19:50 <sdake> inc0 the oting i used as ptl was pretty terrible :)
16:20:09 <sdake> otingvoting
16:20:14 <inc0> well, I'm not too sure about that, I'd like kolla-k8s community to decide what is important for them
16:20:19 <inc0> rather than open voting
16:20:32 <gema> are they not here?
16:20:40 <inc0> and kolla+kolla-ansible doesn't have that many sessions proposed
16:20:44 <sdake> ok so next step then given that thinking is to divide the sessions between kolla-ansible and kolla-kubernetes
16:21:13 <sdake> so we have a full count of which deliverable should vote(?) on which sessions and what our capacity looks like
16:21:17 <sdake> sorry little slow  - just woke up
16:22:34 <inc0> 9 sessions in kolla-k8s
16:22:44 <inc0> I'm not going to make vote just to cast out one:P
16:24:04 <inc0> anyway, sdake since I don't think we have quorum for kolla-k8s sessions right now, let's focus on day 2
16:24:37 <inc0> so we have 20 sessions proposed total, not all of them I think are valid
16:25:13 <sdake> inc0 cool if there are only 9 sessions on kolla-k8s we cna sort that out eaisly
16:25:16 <inc0> some can be squashed to one session
16:25:22 <sdake> the other 19 sessiosn need to fit into 8 slots then?
16:26:38 <inc0> yeah, but if we need to refactor it
16:26:58 <inc0> so let's make 15min timeslot and try to squash/limit number of choices
16:27:08 <inc0> as some of sessions aren't described in any way and such
16:27:19 <inc0> let's work on that till 8:45 please
16:27:27 <inc0> don't delete, crossline
16:27:48 <sdake> inc0 sounds good - woud lyou mind moving the k8s sessions to one location and the ansible session to another location
16:28:03 <sdake> I thnk the kolla deliverable sessions are cross-project for kolla so we can share timeslots there
16:28:23 <sdake> inc0 or is it already organized that way
16:29:39 <srwilkers> is this the kolla-ptg-pike etherpad, or did i miss a link earlier at the start?
16:30:00 <inc0> I found at least one duplicate
16:30:22 <inc0> no, srwilkers https://etherpad.openstack.org/p/kolla-ocata-ptg <- lets' work on this one
16:35:14 <berendt> o/
16:40:13 <inc0> sooo....the way I see it
16:40:16 <sdake> ok made a cross-through  chane to 5
16:40:21 <sdake> about the language process
16:40:30 <sdake> please discuss with yoru flame suits on :)
16:40:56 <sdake> inc0 just trying to shed non-essential topics if possible
16:41:51 <jascott1> is after hours BOF a thing?
16:41:59 <inc0> yeah, so way I see it, I'd add docs session, separation of deliverables session and all of kolla-ansible and kolla
16:42:03 <inc0> that makes it 10
16:42:35 <inc0> so we'd need to drop 2 or maybe canibalize one session from Monday, or have a 9-session days
16:42:59 <inc0> we can have few 20min ones and few 40min ones
16:43:18 <inc0> like docs, important topic but we didnt consume full 40min last time
16:43:55 <inc0> or do just that, put a sessions in waitlist and if we feel we've finished topic, we can just jump to waitlisted one
16:44:28 <sdake> inc0 the docs session could go in the community area
16:44:43 <sdake> 9 session days with a little less breaks sounds good
16:44:47 <sdake> does the math work out there?
16:44:49 <inc0> we don't really have 'community' area:P
16:45:01 * portdirect agile mumble mumble
16:45:53 <sdake> inc0 #1, #2 on the ehterpad
16:45:58 <sdake> at the top
16:46:04 <inc0> I mean time-wise
16:46:09 <sdake> starts line 23
16:46:11 <sdake> inc0 i got it
16:46:15 <sdake> i mean put it in that bucket
16:46:19 <inc0> unless we use first day for it
16:46:42 <inc0> but again, I want to give lot of time to k8s
16:46:45 <sdake> so docs can be added to line 23
16:47:09 <sdake> doccs are important to koll-kubernetes and kolla-ansible, we could spend some time on that I think as a larger project
16:47:19 <sdake> rather group of people
16:47:24 * sdake can't form sentences today
16:47:28 <sdake> 3 hours of sleep will do that to ya
16:47:35 <inc0> ok, executive order, since these are popular lately
16:47:42 <gema> lol
16:47:48 <inc0> let's put docs and separation to Monday
16:47:56 <inc0> as both are closely related to k8s
16:47:58 <sdake> zomg - exedcutive orders need to go in the us :)
16:48:08 <inc0> especially separation
16:48:10 <vhosakot> team, I'd like to contribute to one of the k8s bp's.  I'm chekcing https://launchpad.net/kolla-kubernetes/+milestone/0.5.0 and will pick a bp.  I'm deploying kolla-k8s now and will ask questions in IRC if I have any questions :)
16:48:17 <sdake> inc0 ok that sounds reasonable - rather then an executive order its more like a general agreement :)
16:48:28 <sdake> vhosakot we are sorting out the ptg
16:48:38 <inc0> but that wouldn't allow me to make a political joke
16:48:54 <sdake> politics and religion :)
16:49:03 <sdake> vhosakot can we discuss that after the meeting or in the opens
16:49:07 <gema> inc0: we may have to do the meetings at the airport for all we know ;)
16:49:10 <inc0> so if we put these 2 to Monday
16:49:26 <inc0> we can put all the remaining kolla+kolla-ansible to tuesda
16:49:27 <inc0> y
16:49:28 <sdake> inc0 can you move the two around your talkingabout the tema can see it
16:50:00 <inc0> let me write draft of schedule and you can see what I mean
16:50:44 <vhosakot> sdake: sure, thanks sdake
16:52:01 <inc0> there ya go.
16:52:08 <inc0> #link https://etherpad.openstack.org/p/kolla-pike-ptg-schedule
16:53:24 <inc0> ok, we're running out of time
16:53:24 <sdake> inc0 looking good there!
16:53:31 <inc0> let's pick it up next week
16:53:32 <sdake> i htink we need ot figure out the 6 slots for kolla-kubernetes
16:53:35 <sdake> inc0 sounds good
16:53:40 <inc0> #topic Open Discussion
16:53:48 <inc0> let's have at least few minutes for it
16:53:59 <sdake> gema up next?
16:54:10 <sdake> or vhosakot ?
16:54:15 <gema> https://blueprints.launchpad.net/kolla/+spec/multiarch-and-arm64-containers
16:54:23 <gema> just wanted to share that and ask for reviews/comments
16:54:31 <hrw> I have to make some arm64 images locally and then get kolla working on it
16:54:32 <gema> I am sure I am missing stuff we need to do
16:54:42 <vhosakot> sure sdake  yeah, I've playing with minikube, so, just wanted to contribute to kolla-k8s and help finish some important bp's for the team
16:54:50 <sdake> gema i arbitrarly changed the priority to high
16:54:55 <gema> sdake: thanks!
16:55:07 <sdake> changed to discussion - which alllows peopel to discuss it
16:55:08 <inc0> vhosakot, so currently best think you can do is to help sdake prepare devenv;)
16:55:08 <gema> sdake: we'll treat it as such anyway
16:55:10 <sp__> https://blueprints.launchpad.net/kolla/+spec/coverage-increment-for-kolla     implementation completed need review
16:55:11 <hrw> 4 files changed, 45 insertions(+), 1 deletion(-)
16:55:12 <inc0> amirite?
16:55:21 <hrw> that's whole ppc64le+arm64 base support ;D
16:55:29 <sdake> gema right - the priority typicallly matches the priority of the contributors
16:55:35 <egonzalez> hrw: cool
16:55:39 <sdake> and i got impression you had a high priority for it
16:55:39 <gema> sounds good
16:55:42 <vhosakot> inc0: sure, is that a kolla-k8s devenv?
16:55:43 <gema> sdake: yep
16:55:47 <inc0> hrw, and you wanted 40min to discuss it?:P
16:55:50 <sdake> gema work items need more detail - i'll leave a note in the discussion
16:55:55 <hrw> egonzalez: used hacksaw on ppc64le one ;D
16:55:58 <gema> sdake: great, thanks
16:56:03 <hrw> inc0: haha
16:56:14 <vhosakot> I'll ask questions in the main channel.. thanks for the help!
16:56:24 <sdake> inc0 did you aprove that with kolla-drivers?
16:56:25 <gema> inc0: he won't even be there, it'll be yibo and myself
16:56:28 <sdake> inc0 or was that someone else
16:56:44 <sp__> sdake: please review for the BP     https://blueprints.launchpad.net/kolla/+spec/coverage-increment-for-kolla
16:56:49 <inc0> no worries, but it seems like pretty straightforward thing
16:56:57 <sdake> sp__ anyone can review blueprints :)
16:57:18 <sdake> sp__ that blueprint is in needs code review state
16:57:30 <sp__> sdake: thanks will ask someone
16:57:37 <sdake> sp__ so I think you are ready to go from a core reviewer POV
16:57:38 <inc0> sdake, I can't remember who approved it, but I would
16:57:47 <sp__> sdake: yes
16:57:48 <sdake> inc0 use kolla-drivers from now on?
16:58:02 <sdake> inc0 the downside of thatis then we dont know who to blame for who approved  a blueprint :)
16:58:20 <inc0> it is kolla-drivers now right?
16:58:26 <inc0> anyway we're out of time
16:58:29 <sdake> yes
16:58:39 <inc0> thank you all from coming
16:58:44 <inc0> #endmeeting Kolla