15:59:21 <inc0> #startmeeting kolla
15:59:21 <openstack> Meeting started Wed Oct 11 15:59:21 2017 UTC and is due to finish in 60 minutes.  The chair is inc0. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:59:22 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:59:24 <openstack> The meeting name has been set to 'kolla'
15:59:25 <inc0> #topic w00t!
15:59:26 <duonghq> o/
15:59:27 <inc0> o/
15:59:36 <chason> o/
15:59:42 <inc0> still no agenda;)
16:00:09 <spsurya__> w00t ! 0/
16:00:21 <spsurya__> i added below one
16:00:24 <vhosakot> o/
16:00:26 <egonzalez> woot!
16:02:19 <hrw> o/
16:03:57 <chason> Hello guys, I have registered one bp here https://blueprints.launchpad.net/kolla/+spec/optimize-the-documentation-format. How about to discuss it? :D
16:04:39 <inc0> chason: yeah sure
16:04:48 <inc0> #topic announcements
16:04:58 <inc0> 1. Zuul v3 is rolling soon (again)
16:05:10 <inc0> was suppoised to roll today but infra folk deal with other issues
16:05:43 <inc0> anyway, when it rolls, we're going back to code freeze till gates are fixed. We're close, but that'll take some time, hopefully less than a day
16:06:04 <hrw> thanks for info
16:06:38 <inc0> 2. I learned last week that I'm not going to summit (:() so please, if someone is going, let me know - we need to take care of Kolla stuff there and I'll need your help with this
16:07:14 <inc0> ok let's move on to meeting
16:07:17 <vhosakot> inc0: I'm going and will do the forum session to collect feedback about kolla form users/ops.
16:07:22 <gema> o/
16:07:25 <inc0> #topic docs format
16:07:27 <coolsvap> o/
16:07:30 <inc0> chason: go ahead
16:09:01 <krtaylor> o/
16:09:30 <inc0> #link https://blueprints.launchpad.net/kolla/+spec/optimize-the-documentation-format
16:09:37 <inc0> well ok I think it's self explanatory
16:10:05 <egonzalez> Isn't our docs in rst format?
16:10:14 <inc0> I think they are
16:10:21 <inc0> I can't recall any non-rst piece
16:10:23 <chason> egonzalez nop.
16:10:30 <inc0> really?
16:10:53 <hrw> and how it correlates with krtaylor doc changes?
16:11:02 <inc0> not that much hrw
16:11:04 <chason> egonzalez the current rst format is just looks old.
16:11:05 <krtaylor> so, we have a bp for reworking the documentation in queens to fit the new format
16:11:09 <egonzalez> They are but not follow all standards
16:12:33 <inc0> chason: can we test new approach with our docs somehow?
16:14:58 <chason> egonzalez Exactly
16:16:25 <egonzalez> Is the new sphinx/docstheme version changed?
16:16:29 <gema> shouldn't we just have one BP to do both things?
16:16:41 <gema> i.e. create the new documentation on the new format and deprecate the old doc?
16:16:48 <gema> instead of reworking what we have?
16:16:56 <krtaylor> yep, thats what we have :)
16:17:04 <gema> ah, good, sorry catching up here :D
16:17:25 <krtaylor> chason, what makes this different?
16:18:52 <chason> I think we need to update our doc format following all standards before we can rework them.
16:19:13 <egonzalez> +1 to a single blueprint, this can be a work item on the main doc rework
16:19:23 <hrw> +1 too
16:19:57 <duonghq> +1 too
16:20:20 <hrw> and then I would give decision to krtaylor as he knows where we are with rework
16:20:47 <inc0> chason: when do you upgrade theme?
16:20:58 <krtaylor> so the idea was to move to the new layout, then have contributors rework individual docs rewriting/refreshing
16:21:45 <chason> I will start it tomorrow.
16:21:47 <krtaylor> we have 2 ToC layout patchsets proposed kolla, kolla-ansible
16:22:08 <egonzalez> One was merged yesterday iirc
16:22:32 <krtaylor> chason, it would be good for you to jump on the etherpad and pick a doc you want to rewrite and go for it
16:22:37 <egonzalez> chason, will docs gate break if docs style dont match?
16:23:29 <krtaylor> no, AIUI projects can override as they see fit, it is a recommendation
16:23:46 <chason> egonzalez never mind.
16:25:03 <krtaylor> #link https://blueprints.launchpad.net/kolla/+spec/queens-doc-restructure
16:25:06 <chason> I will upgrade them strictly following by documentation contributor guide.
16:26:04 <krtaylor> #link https://etherpad.openstack.org/p/kolla-queens-doc-restructure
16:26:45 <krtaylor> this is the etherpad for keeping track of which individual docs are being worked on, just put (chason) infront of one and go
16:27:22 <inc0> thank you chason for help
16:27:37 <krtaylor> just list the doc you are working on under ToDo
16:27:53 <krtaylor> so noone else works on it, please
16:28:08 <krtaylor> we all dont have enough bandwidth to duplicate efforts
16:28:27 <chason> krtaylor Roger. :D
16:29:12 <chason> inc0 No matter. :p
16:29:46 <krtaylor> egonzalez, you had a question about whether the kolla docs should be under admin or user?
16:30:05 <krtaylor> I thought we agreed under admin, inc0 ?
16:31:34 <inc0> yeah
16:32:03 <inc0> no particular reason for it, but let's do just admin
16:32:41 <krtaylor> so, let's pick one of the ToC patchsets and merge it, so we can start working on docs
16:32:54 <krtaylor> I don't care which
16:34:02 <inc0> ok, anything else in this topic?
16:37:10 <inc0> guess not
16:37:15 <rwellum> A very late WooT -sorry!
16:37:24 <inc0> #topic open discussion
16:37:25 <inc0> anyone?
16:37:29 <spsurya__> hi rwellum
16:37:46 <spsurya__> inc0: yes
16:37:55 <mgoddard> hi folks
16:38:03 <inc0> spsurya__: shoot
16:38:14 <spsurya__> https://launchpad.net/kolla-ansible/+milestone/queens-1
16:38:14 <spsurya__> https://launchpad.net/kolla/+milestone/queens-1
16:38:14 <spsurya__> https://launchpad.net/kolla-kubernetes/+milestone/0.7.0
16:38:34 <spsurya__> inc0: we need target the feature for release
16:38:48 <spsurya__> in fact for every release
16:38:55 <spsurya__> based PTG discussion
16:39:12 <spsurya__> so that review can be prioritize
16:39:40 <inc0> well, we never really done it
16:39:42 <rwellum> spsurya__: we also have the etherpad of kolla-k8s 1.0
16:40:02 <spsurya__> rwellum: yes we have
16:40:22 <spsurya__> some of them need to be converted to BPs
16:40:28 <rwellum> Yes
16:41:03 <spsurya__> rwellum: we need the revise the target too
16:41:13 <rwellum> https://etherpad.openstack.org/p/kolla-queens-ptg-k8s-release-roadmap
16:41:18 <spsurya__> if I think correctly
16:41:27 <rwellum> Target? As in release?
16:41:51 <spsurya__> i mean for release 0.8.0
16:41:58 <rwellum> Oh right
16:42:19 <spsurya__> then for 0.9.0 for finally 1.0.0
16:43:15 <spsurya__> rwellum: inc0: just for better track
16:43:32 <inc0> well we're very light on process
16:43:51 <inc0> we barely use blueprints really;)
16:44:00 <spsurya__> yeah
16:44:19 <inc0> I'd start by moving to storyboard if we want it
16:46:01 <spsurya__> would be good :)
16:47:18 <spsurya__> thanks that is all from my side
16:47:35 <inc0> ok, mgoddard you wanted to say something too?
16:47:37 <mgoddard> I have an item for open discussion: future of kayobe & kolla-ansible. It would be good to discuss how these projects will coexist going forward, whether there is any interest in picking up kayobe in some form as a kolla deliverable, or alternatively pushing some kayobe functionality into kolla-ansible
16:47:39 <inc0> thank you Surya
16:48:13 <mgoddard> inc0 sensed my finger hovering over the return key
16:48:37 <inc0> mgoddard: I think we should discuss this on ML, that's going to be big increase in scope of kolla-ansibe
16:48:47 <inc0> another deliverable on the other hand is lighter
16:49:22 <inc0> yet another option would be to have kayobe as full fledged openstack project that consumes kolla + kolla-ansible
16:49:33 <inc0> that would give biggest flexibility for you to grow
16:50:08 <inc0> tripleo already consume Kolla images
16:50:09 <mgoddard> inc0 that's a good idea. I'll try to put together my thoughts in an email
16:50:24 <inc0> please do, and add [tc] tag to it too
16:50:36 <inc0> as these guys can provide awesome feedback too
16:51:02 <mgoddard> good thinking.
16:51:16 <inc0> thanks Mark, your work is totally awesome:)
16:52:20 <inc0> anything else?
16:52:23 <inc0> anyone?
16:52:27 <duonghq> me
16:52:33 <inc0> go ahead
16:52:38 <duonghq> #link https://review.openstack.org/#/c/425446/
16:52:40 <mgoddard> I think in any outcome there are some kayobe features which might be better placed in kolla-ansible, and it would be nice to push them down. I'll try to think about what these are - I guess that's a more narrowly scoped kolla conversation
16:53:01 <duonghq> it's keystone zero-downtime upgrade ps, may somebody test and review it?
16:53:04 <inc0> yeah, we can break this apart too and push some stuff to k-ans
16:53:15 <duonghq> ah, sorry mgoddard
16:53:33 <mgoddard> duonghq, my bad! go ahead :)
16:54:27 <duonghq> that's all from me, I only want to re-raise the ks patchset, then I or somebody can work on other services upgrade logic
16:54:37 <inc0> thanks
16:54:47 <inc0> we're at the time, so thank you all for coming!
16:54:58 <inc0> #endmeeting kolla