16:01:05 <inc0> #startmeeting kolla
16:01:06 <openstack> Meeting started Wed Aug 23 16:01:05 2017 UTC and is due to finish in 60 minutes.  The chair is inc0. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:01:07 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:01:10 <openstack> The meeting name has been set to 'kolla'
16:01:15 <inc0> #topic w00t!
16:01:22 <hrw> o/
16:01:25 <Jeffrey4l> o/
16:01:25 <gema> o/
16:01:26 <inc0> w00t everyone:)
16:01:26 <duonghq> woot o/
16:01:29 <sdake> o/
16:01:36 <vhosakot> o/
16:01:43 <hrw> vvo0OT!
16:01:47 <egonzalez> w00t!
16:01:47 <vhosakot> w0ot!
16:01:56 <rwellum> W0OT
16:02:32 <spsurya_> w00t
16:03:59 <sdake> rwellum excited I see :)
16:04:06 <inc0> #topic announcements
16:04:13 <rwellum> I am!
16:04:13 <inc0> and for good reason sdake
16:04:23 <inc0> please welcome our new core!
16:04:39 <gema> \o/ congrats!
16:04:43 <spsurya_> rwellum: grats
16:04:45 * sdake welcomes rewellum to the core reviewer team :)
16:04:48 <egonzalez> congrats rwellum
16:04:54 <duonghq> congrats rwellum
16:04:54 <inc0> (I've cut voting 2 days short because we definetly have quorum of all active cores and I wanted to make this an announcement;))
16:04:55 <hrw> rwellum: congrats!
16:05:09 <hrw> one more person to pester ;d
16:05:09 <vhosakot> rwellum: congrats!  kolla-k8s has a great core team!!
16:05:11 <sdake> inc0 - ya it wasn't quorum it was unaninmous :)
16:05:26 <sdake> inc0 when voting is unanimous it makes sense to close voting
16:05:28 <Jeffrey4l> rwellum, congrats !
16:05:38 <inc0> sdake: I mean we miss few votes, but that's because I slacked with cleaning up core teams:(
16:05:44 <sdake> oh - right
16:06:08 <rwellum> Wow - thanks everyone - really appreciated.
16:06:13 <sdake> my bad - forgot about that :)
16:06:19 <inc0> well deserved:)
16:06:36 <rwellum> And all the help to get up and going and involved. It's a cool community.
16:06:44 <inc0> 2. we're releasing pike rc1 soon
16:07:01 <inc0> Jeffrey4l: when you want to trigger release?
16:07:11 <sdake> inc0 we need to branch first I think?
16:07:21 <sdake> as soon sa rc1 is cut
16:07:24 <inc0> well, that's what I mean
16:07:30 <inc0> rc1 is stable/pike
16:07:39 <Jeffrey4l> next week, around next Wednesday
16:07:44 <sdake> i think the process is submit tag for rc1, submit branch based upon git hash
16:07:55 <sdake> Jeffrey4l ++ :)
16:08:03 <rwellum> Great!
16:08:08 <Jeffrey4l> sdake, yep. when tag rc1, cut pike branch at the same time.
16:08:18 <inc0> ok, anyway I'd like everyone to run upgrade at least once for their respective configuration
16:08:26 <sdake> Jeffrey4l you might consider training other core reviewers on the release process
16:08:46 <sdake> Jeffrey4l for those interested
16:08:59 <sdake> Jeffrey4l may not be a job you want forever :)
16:09:02 <Jeffrey4l> good idea. any volunteer?
16:09:16 <inc0> speaking of training, as you've heard I'll probably won't run again for PTL (in R)
16:09:16 <sdake> egonzalez pbourke come to mind - may hae to ask around
16:09:49 <rwellum> Jeffrey4l: I'd be interested.
16:09:52 <Jeffrey4l> ping me if anyone is interested this.
16:10:22 <sdake> for those tht are interested in release manager training, I didn't find the job to be too taxing
16:10:23 <inc0> so I'd like you to consider running for this seat;) let me know if you decide so I can start teaching you what's involved
16:10:33 <Jeffrey4l> rwellum ok. i will train you next week ;)
16:10:42 <sdake> like less then a few hours a week during release periods
16:10:45 <rwellum> Cool ty.
16:10:46 <sdake> Jeffrey4l is that accurate?
16:11:13 <Jeffrey4l> yes. it doesn't take much time.
16:11:21 <rwellum> re PTL those are great choices IMO inc0
16:12:00 <Jeffrey4l> there are some scripts help to manage the bugs and bps.
16:12:16 <inc0> any community announcements?
16:12:18 <sdake> well as far as I'm concerned any of the core reviewers would have my support as PTL - I think everyone may feel this way on the team
16:12:21 <sdake> inc0 I've got one
16:12:28 <inc0> shoot
16:12:39 <sdake> Dates for Vancouver are announced - May 21-May25th
16:13:02 <sdake> Vancouver = next OpenStack summit (not PTG)
16:13:03 <serlex> nice!i just need to sell a kidney
16:13:05 <inc0> it will be beautiful at this time in pacific nw
16:13:18 <sdake> serlex you need those :)
16:13:30 <sdake> inc0 ok thats all I have
16:13:37 * hrw wants something in europe
16:13:38 <serlex> :D
16:13:46 <inc0> #topic PTG planning (https://etherpad.openstack.org/p/kolla-queens-ptg-planning)
16:14:03 <inc0> just short reminder, we have etherpad
16:14:11 <inc0> feel free to put stuff there
16:14:18 <duonghq> ya, I can get to this PTG
16:14:23 <inc0> yay!
16:14:46 <rwellum> +1 duonghq
16:15:03 <inc0> I'll give one more week on this and add times afterwards
16:15:14 <hrw> gema will have to represent aarch64
16:15:15 <inc0> I think we'll do similar form as we did last time
16:15:24 <vhosakot> +1 duonghq!
16:15:31 <inc0> 1 day for kolla-k8s, one for image+ansible (less content to discuss I think()
16:15:51 <inc0> we have 3rd day too which will be more free-form and probably I won't schedule stuff on it
16:16:09 <inc0> we'll use it as bucket for whatever comes up over the week
16:16:12 <sdake> inc0 i think we need to take more tim to look at how we can moe kolla-ansible forward
16:16:19 <inc0> I felt we could use time like that
16:16:25 <sdake> inc0 of particular interest at the operator summit was skip-level upgrades
16:16:59 <inc0> well tbh with kolla-ansible I'd say skip lever would be "just do 2 upgrades, it's fast enough"
16:17:33 <inc0> brownfield problems is another thing I'd like to discuss
16:17:47 <inc0> but again, we'll have full unscheduled day if we run out of time
16:18:13 <inc0> anything else on this topic?
16:18:38 <inc0> also sdake I added note about skip lever to etherpad
16:18:43 <duonghq> inc0, did you discuss with tripleo about the interprojcet discussion?
16:19:02 <inc0> duonghq: we'll do it on Friday I think
16:19:10 <inc0> depends on tripleo schedule too
16:19:14 <rwellum> I added that to the etherpad just now
16:19:19 <inc0> we'll figure out timeslot
16:19:24 <sdake> inc0 i think the interproject discussion is planned for monday-tuesday inc0
16:19:30 <sdake> in the #packaging room
16:19:48 <inc0> depends how you define it;)
16:19:59 <sdake> inc0 doesn't it always
16:20:06 <inc0> anyway we'll be in same hotel for 5 days, I'm sure we'll figure it out;)
16:20:08 <egonzalez> tripleo has not decided yet times, also from ML seems OSA people will join too
16:20:28 <sdake> ya - there is a monday/tuesday packaging day
16:20:33 <inc0> well this particular discussion is about future of triple being ansible+k8s
16:20:40 <inc0> kolla-k8s is ansible+k8s
16:20:45 <sdake> where the deployment tools sort out how to work together (along with the rpm and deb packaging teams)
16:21:10 <inc0> so it's specific topic
16:21:22 <sdake> i wonder if the #packaging room has a specific agenda
16:21:44 <sdake> (or any planning related to it) - inc0 do you knwo?
16:21:52 <inc0> no, I don't
16:22:00 <sdake> inc0 any chance ou can find out?
16:22:02 <inc0> also I don't knwo who would be responsible
16:22:14 <sdake> perhaps flavio or doug can be contacted
16:22:43 <sdake> i am not sure who designed the room layout for the ptg, although I think the tc should have some insight into the planning around the collobration sessions on monday and tuesday
16:22:45 <inc0> right, if I know anything about meetings like that is that it'll be sorted out closer to PTG
16:22:55 <sdake> there is an ethercalc.. :)
16:22:56 <inc0> that'd be ttx I think
16:23:14 <inc0> I know that ehterpads will be published
16:23:14 <sdake> inc0 doubt ttx did it alone:) but possible
16:23:25 <inc0> also this bot was written which is totally awesome
16:23:48 <sdake> does it do laundry automatically?  If not, then not awesome :)
16:24:09 <inc0> anyway, anything else on topic?
16:24:09 <sdake> (inc0 that was a joke - what does the bot do)
16:24:26 <rwellum> I just thought - we could do with a new 'kolla' hangouts chat - one which isn't 300 people long. How to arrange that? Numbers on an etherpad maybe?
16:24:40 <inc0> (I know, I might be grim slav, but I'm not totally devoid of sense of humor;))
16:24:41 <sdake> rwellum i dont follow
16:25:05 <sdake> rwellum you mean google hangouts?
16:25:15 <rwellum> sdake: we had a hangouts group at the last summit but it needed to be pruned I think.
16:25:17 <inc0> rwellum: I honestly don't want to splinter community by introducing new communication devices
16:25:25 <inc0> ahh ptg specific
16:25:28 <inc0> yeah, that makes sense
16:25:31 <rwellum> yeah - sorry :)
16:25:37 <sdake> oh - the chat service
16:25:46 <sdake> ya we shoul dse that up for onsight
16:25:47 * rwellum confuses everyone
16:25:58 <inc0> rwellum: can you handle that please?
16:26:04 <sdake> perhaps inc0 could make an etherpad adn kolla on tour can be igned up for
16:26:10 <inc0> just add inv link to ptg etherpad
16:26:15 <rwellum> Yup will do.
16:26:19 <inc0> thank you
16:26:22 <rwellum> np
16:26:23 <sdake> rwellum good idea :)
16:26:39 <rwellum> ty
16:27:02 <hrw> and hangouts shows where each person is in discussion (up to which place they read)
16:28:35 <sdake> the tech we used for that las ttime for group messaging was pretty cool
16:28:47 <sdake> we have used it for a few years - ymmv
16:28:53 <inc0> rwellum: if you could set it up a bit earlier than PTG that'd be awesome, so people can organize airport cab and stuff
16:29:29 <inc0> ok, can we move on?;0
16:29:46 <inc0> executive decision, we're moving on;)
16:29:51 <rwellum> on it inc0
16:29:52 <inc0> #topic arm
16:29:59 <inc0> hrw: you have the floor
16:30:13 <hrw> ok
16:30:23 <inc0> full topic: Bring multiarch and start building ARM64 containers to Kolla blueprint ;)
16:30:23 <hrw> #link https://blueprints.launchpad.net/kolla/+spec/multiarch-and-arm64-containers
16:30:46 <hrw> I would like to close that blueprint as implemented
16:31:04 <inc0> it's done? cool.
16:31:09 <gema> (we have factored out 3rd party CI to queens, which we didn't have to finish this cycle)
16:31:11 <hrw> kolla can be now used to build images for aarch64 (and ppc64le) architectures out of the box
16:31:27 <gema> #link https://blueprints.launchpad.net/kolla/+spec/aarch64-3rd-party-ci-kolla
16:31:30 <inc0> woot, awesome (my Intel persona grinned inside)
16:31:41 <hrw> we merged everything what was needed for that
16:31:57 <hrw> Debian support got improved and moved to current stable release
16:32:22 <hrw> images which do not have support for Debian or !x86-64 got marked as such
16:32:30 <inc0> hmm I can't change status for some reason, gema can you check?
16:32:38 <gema> inc0: I cannot either
16:32:39 <gema> sdake: ?
16:32:53 <hrw> marked as implemented fine
16:33:08 <sdake> gema what was the question?
16:33:09 <inc0> nvm
16:33:13 <inc0> I got it
16:33:17 <inc0> it's complete now
16:33:18 <gema> sdake: he got it :D
16:33:20 <inc0> thanks:)
16:33:20 <gema> inc0: thanks
16:33:39 * inc0 has brain freeze, sorry
16:34:07 <hrw> there will be improvements for kolla still but probably more for kolla-ansible now
16:34:15 <gema> inc0: at PTG we need to learn how to publish images, but that is part of a broader discussion, I think
16:34:27 <inc0> right, we'll spend some time on that for sure
16:34:32 <gema> for now we are building them
16:34:34 <hrw> gema: we probably have to create/open blueprint for aarch64-support-in-kolla-ansible
16:34:45 <gema> hrw: good point, will do taht tomorrow
16:35:25 <Jeffrey4l> should we enable debian gate jobs for kolla now?
16:35:34 <gema> Jeffrey4l: yep, taht was the next point
16:35:37 <hrw> the goal for next Linaro SDI release is to move to Kolla (for building images) and Kolla-ansible (to deploy)
16:35:52 <Jeffrey4l> great. iirc, it is in experimental pipeline now.
16:35:53 <hrw> gema: right, more or less?
16:36:07 <gema> hrw: we are effectively abandoning our packaging in favor of kolla containers
16:36:08 <inc0> Jeffrey4l: I think we should focus on 3rd party arm/arch CI
16:36:10 <gema> :)
16:36:23 <gema> and we'll move our clouds to it also
16:36:29 <inc0> as Debian+amd64 is not supported by anyone really;)
16:36:49 <Jeffrey4l> (we can enable debian + amd64 build), ok, you are right.
16:37:14 <inc0> gema: on PTG we'll discuss technical details of 3rd party CI
16:37:19 <gema> inc0: sounds good
16:37:20 <inc0> we'll have lot of infra people around
16:37:29 <hrw> I think that debian/amd64 may show some contributors that their changes are wrong for debian
16:37:33 <inc0> so we'll get immediate help if something is unclear
16:37:37 <gema> inc0: good, I have a better understanding of our challenges now
16:38:04 <inc0> great stuff:)
16:38:21 <gema> thanks for your help guys, it's been an awesome cycle for us
16:38:25 <gema> I am sure hrw agrees :)
16:38:30 <hrw> o yes!
16:38:32 <hrw> o yes!!
16:38:35 <hrw> o yes!!!
16:38:36 <hrw> ;D
16:38:55 * inc0 cries in Intel
16:38:58 <gema> haha
16:39:07 <hrw> still not a fan of Docker anyway ;d
16:39:17 <inc0> j/k it's great feature;) thanks for all the hard work
16:39:45 <inc0> hrw: trick for me was to understand that it's nothing more than glorified package
16:39:53 <gema> inc0: hrw complains about everything, if he is complaining he is happy
16:39:55 <sdake> hrw i think your stratgic defense initiative (SDI) sounds great :)
16:40:04 <inc0> also that is true: https://twitter.com/mihn/status/899727274077040641
16:40:15 <hrw> Jeffrey4l:  https://da.gd/Hx2S is rebase of your patch for adding Debian gates
16:40:33 <hrw> inc0: overrated D:
16:40:36 <inc0> we start from "this is garbage" and go from there
16:40:48 <gema> hrw: I think inc0 doesn't want to enable them for amd64, we'll do it for arm64 in queens
16:40:52 <inc0> but usually it doesn't go from there and stays there forever
16:40:52 <sdake> inc0 that graphic is missing the canadians :)
16:41:07 <hrw> sdake: canadians froze
16:41:27 <inc0> they trusted garbage tech too much
16:41:33 <hrw> sdake: I am CCO in SDI.
16:41:39 <hrw> Chief Complaining Officer
16:41:48 <gema> in software defined infrastructure :)
16:42:04 <sdake> hrw ;)
16:42:19 <hrw> gema: which runs in Meth lab
16:42:38 <inc0> ok, I think we digress too much;) anything on the topic?
16:42:42 <gema> hrw: you should have stopped one sentence earlier :D
16:42:43 <inc0> left?
16:42:54 <hrw> inc0: open floor?
16:42:54 <gema> nah, we are good I think
16:43:11 <inc0> cool, thanks again, ton of great work gema, hrw and others!
16:43:17 <inc0> #topic open discussion
16:43:20 <inc0> anyone?
16:43:31 * hrw wants european PTG
16:43:45 <spsurya_> +1
16:43:53 <spsurya_> me too
16:44:05 <inc0> trust me I second that
16:44:13 <hrw> btw - would be nice to remove images like grafana/kafka from CI ones
16:44:19 <duonghq> me too,
16:44:29 <inc0> we could do one in Poland, people would get hotels for half free (compared to US)
16:44:33 <hrw> they fail on fetching random files over http(s) so CI fails
16:44:42 <hrw> inc0: Holland?
16:45:11 <duonghq> anybody can give me some insight about this: https://review.openstack.org/#/c/398682/
16:45:22 <duonghq> this too: https://review.openstack.org/#/c/425446/
16:46:01 <hrw> when it comes to ansible I am like Jon Snow - know nothing
16:46:10 <rwellum> I added this for the Hangouts Group Chat: https://etherpad.openstack.org/p/Kolla-On-Tour - and linked on the planning Etherpad.
16:46:29 <inc0> seems like tarballs had issues
16:46:53 <inc0> rwellum: can we do invite link?
16:46:55 <hrw> inc0: imho CI should mirror such files
16:47:00 <egonzalez> yeah, post merge jobs sometimes fail, oracle binary has failed for 2 days
16:47:25 <rwellum> Yes - I'll set up the group and do that in a few inc0
16:47:31 <inc0> cool, thanks
16:47:37 <hrw> second recheck came for https://review.openstack.org/#/c/496706/
16:47:56 <hrw> maybe I get lucky and both grafana and kafka will work this time
16:49:54 <rwellum> duonghq: there's a lot of reviewers on those PS's - what insite you looking for?
16:50:05 <rwellum> Or insight if I could spell
16:50:18 <inc0> gates are red in different fasion:/
16:50:23 <inc0> nothing seems to be related to change
16:50:33 <inc0> tarballs seems to be broken
16:50:44 <duonghq> inc0, yah, I'm finding clues
16:50:46 <inc0> ^ this is almost a haiku
16:51:29 <duonghq> rwellum, I'm finding way to make gates green again
16:51:48 * hrw off
16:51:52 <rwellum> Oh right
16:52:35 <inc0> ok, I'll wrap the meeting
16:52:43 <inc0> we can continue on regular channel
16:52:48 <inc0> thank you all!
16:52:52 <gema> thank you!
16:52:55 <inc0> #endmeeting kolla