16:02:18 <inc0> #startmeeting kolla
16:02:19 <openstack> Meeting started Wed Nov 23 16:02:18 2016 UTC and is due to finish in 60 minutes.  The chair is inc0. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:02:20 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:02:22 <openstack> The meeting name has been set to 'kolla'
16:02:37 <inc0> #topic woot for kolla - rollcall
16:02:44 <inc0> w00t everyone!;)
16:02:44 <duonghq> woot
16:02:53 <berendt> woot
16:03:01 <sean-k-mooney> woot
16:03:03 <jascott1> woot
16:03:06 <Jeffrey4l> woot
16:03:10 <zhubingbing> woot
16:03:12 <srwilkers_> woot and such
16:03:13 <duonghq> nice to see you guys
16:03:13 <sdake_> o/
16:03:19 <mgiles> woot
16:03:21 <portdirect> o/
16:03:28 * berendt is only reading, walking to the hotel at the moment, reading on my mobile phone
16:03:32 <sean-k-mooney> sdake_: being a rebel with the o/
16:03:55 <sp__> hi all
16:03:59 <sayantani01> woot :)
16:04:11 <inc0> #topic announcements
16:04:12 <sdake_> sean-k-mooney o/ is standard openstack greeting
16:04:25 <inc0> I don't have anything:)
16:04:34 <inc0> oh, we do have voting gates now
16:04:49 <sean-k-mooney> cool
16:04:50 <inc0> for source builds
16:04:50 <Jeffrey4l> and gate is green ;)
16:05:00 <sdake_> Jeffrey4l ++
16:05:12 <inc0> any announcements from community?
16:05:21 <sdake_> ya i got something
16:05:25 <inc0> go ahead
16:05:34 <sdake_> ryan stepping away from kolla project for awhile
16:05:37 <sdake_> who knows how long
16:05:49 <srwilkers_> :(
16:05:51 <sdake_> in the meantime i'll be handling kolla-kubernetes
16:06:00 <Jeffrey4l> ;(
16:06:05 <sdake_> this project is too big to handle solo
16:06:17 <sdake_> i failed at handling kolla-kubernetes in newton - so busy with ansible
16:06:32 <sdake_> lets make it a winner
16:06:40 <zhubingbing> ;)
16:06:51 <jascott1> woot!
16:06:58 <duonghq> roger
16:06:59 <berendt> Bad news... :-(
16:07:02 <inc0> k, let's start with actual meeting:)
16:07:11 <inc0> we'll talk about k8s later
16:07:16 <sdake_> ya he may come back who knows
16:07:19 <inc0> #topic gates - state of union
16:07:38 <inc0> so, thanks to Jeffrey4l and others we have green gates after repo splut
16:07:53 <inc0> we also have some voting gates, so now we can move forward to make improvements
16:08:19 <inc0> 1 thing is effort to setup docker registry in infra
16:08:45 <Jeffrey4l> inc0, what's the progress on that?
16:08:49 <inc0> https://review.openstack.org/#/c/401003/ https://review.openstack.org/#/c/399221/
16:09:02 <inc0> these reviews + some discussions I keep having on infra
16:09:12 <Jeffrey4l> cool
16:09:16 <inc0> I know how to install registry outside docker, but I could use puppet help
16:09:35 <inc0> so if anyone knows puppet and would like to assist me with this, I'd appreciate it
16:09:49 <inc0> having registry will allow us to have voting deploy gates
16:10:14 <inc0> also few other nice things like proper upgrade gates
16:10:28 <inc0> next item that could be done would be multinode gating
16:10:42 <sean-k-mooney> inc0: is there a reason you are installing the registry with puppet and not using the docker container?
16:10:43 <inc0> kfox1111 already prototyped multinode gate in kolla-k8s, we could do it in kolla too
16:10:47 <inc0> kolla-ansible*
16:11:00 <inc0> sean-k-mooney, they don't have running docker
16:11:07 <inc0> so we'd need to install docker;) arguably harder
16:11:18 <sean-k-mooney> inc0: ah ok makes sense
16:11:51 <inc0> so if someone would like to tackle multinode gating, this is open for volunteers too
16:12:22 <inc0> next in line would be more scenerios, but that's going to grow
16:12:46 <sdake_> inc0 i did you a favor and cleaned up launchpad for kolla itself
16:12:47 <inc0> gates are one of biggest painpoints Kolla has today, and one of priorities for release
16:12:57 <inc0> sdake_, thank you
16:12:58 <sdake_> inc0 recommend blueprints to track that work
16:13:08 <sean-k-mooney> inc0: is tempest run in the gates currently?
16:13:08 <sdake_> then people can sign themselves up
16:13:14 <inc0> sean-k-mooney, nope
16:13:30 <Jeffrey4l> sean-k-mooney, i am trying to set tempest up.
16:13:33 <sdake_> np
16:13:46 <sean-k-mooney> Jeffrey4l: cool useing the tempest contaienr in kolla?
16:13:51 <Jeffrey4l> sean-k-mooney, yep.
16:13:53 <sdake_> rather kolla-ansible
16:13:57 <sdake_> which is where we want the gates
16:14:06 <inc0> sdake_, we want gates everywhere;0
16:14:18 <inc0> but build gates are straightforward and not much more we can do there
16:14:23 <sdake_> right
16:14:31 <inc0> (well, we could use customizations for example)
16:14:43 <inc0> but ansible needs more immediate gate help
16:14:43 <sean-k-mooney> Jeffrey4l: its mising ping which make the scenairo tests fail so that will need to be fixed to make the gates pass when tempest is added
16:16:16 <Jeffrey4l> we also need something like puppet scenario 1/2/3, to test more service.
16:16:30 <inc0> anyway, I'd like to get registry up first, so if anyone would be willing to help me, please speak up now or after meeting
16:17:15 <inc0> anything else about gates?
16:18:09 <Jeffrey4l> need volunteer ;)
16:18:19 <sdake_> need a blueprint
16:18:34 <sdake_> work items in blueprint
16:18:40 <Jeffrey4l> need more guy to notice the gate failure and fix it ;)
16:18:41 <sdake_> volunteers sign up for work items
16:18:45 <sdake_> thats how we have always rolled
16:18:51 <Jeffrey4l> sdake_, yep.
16:19:29 <inc0> kk, I'll subit my blueprints after meeting, Jeffrey4l please do it too if you have anything in mind
16:19:37 <inc0> (also everyone else;))
16:19:40 <inc0> moving on
16:19:49 <inc0> #topic post-repo split cleanups status
16:19:54 <inc0> #link https://etherpad.openstack.org/p/kolla-repo-split
16:20:06 <Jeffrey4l> roger.
16:20:19 <inc0> let's go from top
16:20:25 <inc0> 1. removal of ansible code -> done
16:20:50 <inc0> let's mark what is done and what's not
16:20:58 <inc0> 2. fixing gates
16:21:08 <inc0> can we call it done or still work to be done?
16:21:22 <sean-k-mooney> the ansible code is removed but we still need to remove the non ansible code form kolla-ansible correct?
16:21:46 <Jeffrey4l> fixing gate is done.
16:21:58 <sp__> sdake_: yes we will
16:22:05 <Jeffrey4l> but we need more gate ;), it is another thing.
16:22:12 <sdake_> sp__ huh?
16:22:13 <Jeffrey4l> 3. doc split
16:22:13 <inc0> sean-k-mooney, it seems we already merged docker removal from ansible
16:22:28 <inc0> docs are very outdated and totally not changed
16:22:32 <sp__> sdake_: sign up for work
16:22:41 <inc0> I'd put this as #1 priority
16:22:44 <sdake_> oh right
16:23:04 <Jeffrey4l> inc0, we can not maintain two copy of doc.
16:23:16 <inc0> Jeffrey4l, I'd keep all docs in kolla for now
16:23:27 <inc0> no reason to add to confusion
16:23:34 <Jeffrey4l> so all doc in kolla-ansible should be removed?
16:23:38 <sean-k-mooney> inc0: so going forward all docs reside in kolla. for kolla-ansibel and k8s
16:24:00 <inc0> Jeffrey4l, maybe, that's good discussion to be had, I'll put it into dedicated topic in this meeting
16:24:11 <egonzalez90> i would leave there and link from kolla to kolla-ansible repo, the same for k8s docs
16:24:26 <inc0> egonzalez90, agree, and doc root in Kolla
16:24:30 <Jeffrey4l> sean-k-mooney, kolla-ansible has its own doc right now. if we keep all docs in kolla, including k8s, we need move that doc
16:24:43 <Jeffrey4l> kolla-ansibe/kolla-k8s
16:24:52 <inc0> but for now we need to change quick start guide to work with repo split
16:25:17 <inc0> QSG should be single doc tho
16:25:24 <inc0> it's meant to be simple and easy to follow
16:25:50 <inc0> anyway, docs -> still to be done and #1 priority
16:26:02 <inc0> 7. bugs and blueprints moved out of kolla
16:26:12 <inc0> sdake_, you mentioned you took on that right? what's the status?
16:26:38 <sdake_> actually jeffrey4l moved the bugs and coolsvap moved the blueprints
16:26:44 <sdake_> i got them into an orderly state
16:26:52 <inc0> ok, thank you all then
16:26:53 <sdake_> the blueprints part
16:26:58 <inc0> so can we mark it as done?
16:27:00 <sdake_> didnt' touch the bugs, done triaging for awhile :)
16:27:04 <inc0> so bugs...will be harder
16:27:19 <inc0> as people will keep adding bugs to kolla, and that's ok
16:27:47 <Jeffrey4l> another thing is: how we handle the bp after split. is there any better solution expect for register on each project?
16:27:50 <inc0> as part of triaging we might need to add "moving bugs to appropriate project" part
16:28:09 <sean-k-mooney> inc0: sorry to go back to the split but what about the tools directory and kolla python module. im not sure the build code shoudl be duplicated in kolla-ansible
16:28:15 <Jeffrey4l> inc0, yep.
16:28:18 <sdake_> project^deliverable :)
16:28:20 <inc0> Jeffrey4l, well, blueptints for kolla-ansible will mostly be different than kolla
16:28:44 <inc0> sean-k-mooney, there are tools for kolla and tools for kolla-ansible
16:28:56 <sean-k-mooney> blueprints could be decomposed into parts. one for the container to kolla and then one for each deployment type
16:28:58 <Jeffrey4l> inc0, yep. just wanna to check whether there is a better solution. it is different, but related.
16:28:59 <inc0> I can't think of any overlap
16:29:01 <inc0> liek tools for both
16:29:16 <Jeffrey4l> like `implement nova service`
16:29:21 <sean-k-mooney> inc0: yes but the tools for anible still have the image build code
16:29:50 <inc0> Jeffrey4l, that can be "implement nova container" -> kolla "implement nova ansible role" ->k-ansible "implement nova k8s chart" -> k-k8s
16:30:01 <inc0> sean-k-mooney, why?
16:30:07 <inc0> I mean
16:30:08 <inc0> now for gates
16:30:13 <inc0> but normally, not really
16:30:20 <inc0> build is totally separate
16:30:33 <sean-k-mooney> inc0: well thats my point the repos has that code currently
16:30:45 <inc0> ahh, so add this to cleanup right?
16:30:48 <inc0> good catch
16:30:55 <inc0> I'll make it separate point in etherpad
16:30:56 <sean-k-mooney> inc0: i think we should remove it from kolla ansible and just use the code in kolla
16:30:57 <portdirect> kolla-k8s also currently relys on code that is in kolla-ansible for config gen afaik - gut agai i think this is just transitionary.
16:31:05 <sean-k-mooney> inc0: cool
16:31:07 <portdirect> *but again
16:31:14 <Jeffrey4l> inc0 re bp yep. that works.
16:31:24 <sdake_> portdirect yup transitory
16:31:39 <inc0> well
16:31:45 <inc0> not exactly
16:31:49 <inc0> I mean we want it changed
16:31:54 <Jeffrey4l> portdirect, any idea on improving this?
16:31:54 <inc0> but we don't know how to change it really
16:32:17 <inc0> #link https://review.openstack.org/#/c/399147/
16:32:24 <inc0> Jeffrey4l, ^
16:32:44 * Jeffrey4l is checking
16:32:56 <sdake_> inc0 you were going to write a spec for seperating the default configs?
16:32:59 <portdirect> not really - I'm open to suggestions - but inc0's just pointed to somthing i'd missed
16:33:09 <inc0> sdake_, click da lin
16:33:10 <inc0> k
16:33:29 <sdake_> cool thanks
16:33:32 <inc0> it's still sceleton, but I'll need more people to chime in
16:33:48 <inc0> it's important
16:33:52 <inc0> to be done right
16:34:16 <inc0> as it will affect upgrades/ansible (which *has to work*) and stable releases
16:34:35 <inc0> which means if we want to roll with it, it has to be bulletproof
16:34:59 <inc0> I'd rather keep duplicated configs that break upgrades
16:35:13 <sdake_> yup clearly
16:35:21 <inc0> ok, bottom line, take a look at spec later and let's kick off this discussion
16:35:24 <inc0> moving on
16:35:32 <inc0> #topic documentation after split
16:35:34 <portdirect> inc0: that spec looks logical, I'll look later
16:35:59 <inc0> So Jeffrey4l moved good topic, we need to decide which docs sits where
16:36:25 <inc0> my suggestion: root doc, arch docs and stuff like that (also QSG) in kolla and links to kolla-k8s and kolla-ansible from there
16:36:27 <Jeffrey4l> fyi, kolla-ansible has doc site right now http://docs.openstack.org/developer/kolla-ansible/
16:36:55 <sdake_> i tend to think we should hash that out on the mailing list
16:37:01 <sdake_> the docs are a fragile thing
16:37:11 <sdake_> because we dont have a doc writer writing docs
16:37:18 <inc0> yeah, agree, let's kick off discussion please tho
16:37:41 <sean-k-mooney> i think we are going to find more things that are common between k8s and ansible in the future not just docs and configs.
16:37:49 <inc0> for one, we *need* QSG fixes asap
16:38:04 <inc0> (especially that it still shows that stable branch needs ansible 1.9)
16:38:09 <Jeffrey4l> QSQ? means?
16:38:10 <inc0> (which is not true for newton)
16:38:17 <inc0> QSG - quick start guide
16:38:22 <Jeffrey4l> roger.
16:38:30 <sdake_> nah qsg has two sets of requirements
16:38:33 <sdake_> if you read the docs :)
16:38:51 <Jeffrey4l> we added more thing in QSG, imo.
16:38:54 <sdake_> ansible 2.0 and ansible1.9
16:39:13 <inc0> https://github.com/openstack/kolla/blob/master/doc/quickstart.rst#install-dependencies
16:39:23 <inc0> yes, and 1.9 is dependency *for stable branch*
16:39:28 <inc0> which is no longer true
16:39:37 <sdake_> i see what you mean
16:39:49 <duonghq> iirc there is a ps in review queue fixing this
16:39:50 <sdake_> yup that needs changing
16:39:57 <inc0> also QSG should use bootstrap-servers
16:40:19 <inc0> as it's much easier to handle than manual labor
16:40:23 <Jeffrey4l> we have this line, should mention stable branch thing in master doc http://docs.openstack.org/developer/kolla/newton
16:40:28 <Jeffrey4l> need fix it in stable branch doc.
16:40:58 <inc0> that's also true, we can just link old docs and keep single versions in master
16:41:13 <inc0> bottom line, QSG needs love, lots of it, we should rewrite it tbh now
16:41:49 <inc0> v1k0d3n, also mentioned need to add "hacks to deploy with single interface"
16:41:57 <inc0> also useful
16:42:00 <sdake_> docs are #1 complaint, #2 complaint, and #3 compliant from operators
16:42:12 <sean-k-mooney> inc0: on that i need to extend the kolla-host script to be also able to bootrasp the build host.
16:42:16 <Jeffrey4l> sdake_, lol that's true
16:42:18 <v1k0d3n> ah, yes. been playing with this.
16:42:22 <v1k0d3n> inc0:
16:42:36 <inc0> sean-k-mooney, not really
16:42:39 <inc0> it's all working
16:42:53 <v1k0d3n> started asking questions about some api strangeness (most likely a config error on my end) with sdake_yesterday, but there were too many convo's going on at that time.
16:43:01 <inc0> I mean it can download kolla, but that's a bit over the top imho
16:43:14 <v1k0d3n> if someone can help me understand a little better, i can get this firmed up fairly quickly. over teh weekend perhaps
16:43:15 <v1k0d3n> ?
16:43:27 <inc0> v1k0d3n, sure, after meeting
16:43:33 <portdirect> the kolla-k8s docs are esp bad at the moment; though I think we should discuss that when we get to that part of the meeting?
16:43:40 <sean-k-mooney> inc0: well ill submit a blueprint with what i was thinking and we cans discuss
16:43:50 <inc0> sean-k-mooney, please, thanks
16:44:15 <v1k0d3n> portdirect: sean-k-mooney sdake_ inc0 we are working on adding the pvc to halcyon...which is a big deal.
16:44:29 <inc0> pvc?
16:44:30 <zhubingbing__> i have two  questions about elk
16:44:37 <inc0> as in volume claim?
16:44:46 <v1k0d3n> if that helps? there is a workaround that kolla-k8s should be aware of...we needed a custom kubernetes-controller to make this work.
16:44:49 <portdirect> ^^
16:44:50 <v1k0d3n> yes inc0
16:45:09 <v1k0d3n> btw: https://github.com/att-comdev/dockerfiles/tree/master/kube-controller-manager
16:45:12 <inc0> ok, I think we naturally moved to
16:45:19 <inc0> #topic kolla-kubernetes topics
16:45:22 <v1k0d3n> not sure if in the future workarounds should be kolla provided?
16:45:29 <v1k0d3n> i think this may actually be a good idea...
16:45:41 <v1k0d3n> to prevent broken items in the future.
16:45:50 <v1k0d3n> (reliance on upstream)
16:46:01 <sdake_> #1 complaint I get from all the folks that want to do kolla-kubernetes dev is "how do I develop the thing"
16:46:10 <portdirect> developer env: we need a common one
16:46:19 <portdirect> and the docs to go with it
16:46:22 <inc0> halcyon is promising in this space
16:46:27 <portdirect> +1
16:46:30 <v1k0d3n> source of truth halycon and we can doc?
16:46:36 <v1k0d3n> or if someone wants to help...that's fine too
16:46:44 <v1k0d3n> portdirect:  you've done a lot to help as well.
16:46:49 <portdirect> v1k0d3n: I'd be up for helping there
16:46:58 <inc0> let's start with doc
16:47:00 <sdake_> https://launchpad.net/kolla/ocata
16:47:06 <sdake_> woops wrong link :)
16:47:06 <v1k0d3n> and as i've said before...it doesn't have to stay in this repo. if the source of truth is better in kolla-k8s...by all means!
16:47:11 <inc0> I'd like to have it in gerrit one way or another at some point
16:47:38 <sdake_> https://launchpad.net/kolla-kubernetes/ocata
16:47:43 <inc0> v1k0d3n, or dedicated "satelite" project in openstack
16:47:50 <sdake_> have a look at ocata 2 (the milestone we are in at present)
16:47:54 <inc0> logistics can be dealt with
16:47:57 <v1k0d3n> how can we make this happen?
16:48:13 <v1k0d3n> or should say...what can we do to help?
16:48:14 <portdirect> Ok - leading on from sdake's comment - has anyone got a working deve env from kolla-k8s that they have propped up in the last few weeks?
16:48:15 <sdake_> its easy, just follow the openstack workflow
16:48:16 <inc0> v1k0d3n, 1hr of work really;) creating kolla-halcyon deliverable
16:48:45 <v1k0d3n> the doc is blueprint already.
16:48:47 <sdake_> i think it makes more sense to just link then add a deliverable
16:48:52 <sdake_> v1k0d3n agree
16:48:58 <v1k0d3n> you want halcyon to end up in a dev folder for kolla-k8s?
16:49:04 <sdake_> we want o move fast making a deliverable takes forever
16:49:05 <v1k0d3n> we can make that happen if you want.
16:49:27 <portdirect> that woud be great from my point of view
16:49:33 <mgiles> halcyon is limited to os's that support kube-adm though, right?
16:49:39 <sdake_> v1k0d3n what I'd like is docs in kolla-kubernetes itself that shows how to use halcyon
16:49:43 <inc0> ok, propose a patch then v1k0d3n please
16:49:44 <mgiles> Fine for dev, but might be a problem longer term for us
16:49:53 <inc0> to kolla-k8s with halcyon in it, and docs
16:49:54 <v1k0d3n> currently yes, but i was going to submit an update for some of the CoreOS happening currently.
16:49:59 <v1k0d3n> mgiles: ^^^
16:50:01 <v1k0d3n> my comment
16:50:09 <portdirect> I'm also working on Fedora Atomic support
16:50:19 <sdake_> i think we treat halcyon a an upstream dev environment
16:50:25 <sdake_> rather then somethign we maintain
16:50:38 <srwilkers_> i think thats a better approach
16:50:40 <inc0> well, it's going to be critical for our effort
16:50:43 <portdirect> exactly - it just takes the strain of setting up a k8s cluster
16:50:53 <sdake_> portdirect precisely
16:50:58 <sdake_> then people can develop
16:51:02 <sdake_> that unblocks that
16:51:05 <inc0> ok, I'll shut up now;) I need docs at least
16:51:15 <inc0> where code lives - we can discuss later
16:51:21 <sdake_> ya
16:51:22 <sdake_> so GOAL
16:51:23 <v1k0d3n> inc0: sounds good
16:51:35 <sdake_> 1.0.0 = compute kit based upon spec ryan wrote
16:51:51 <sdake_> its only going to happen with community support
16:51:57 <sdake_> take a look at the blueprints
16:52:01 <sdake_> they are well laid out
16:52:14 <sdake_> sign up for what interests you
16:52:16 <sean-k-mooney> it would be nice if the bootstrap-servers command could bootrap for the k8s enviorment too. even if that is just use halcon after installing docker.
16:52:27 <sdake_> sean-k-mooney oen thing at a time bro :)
16:52:33 <sdake_> lets get it working in a dev env first
16:52:46 <duonghq> I'm thinking I should give kubeadm another chance
16:52:46 <sean-k-mooney> sdake_: sure thing
16:53:03 <sdake_> duonghq whatever works for you
16:53:16 <duonghq> kube-deploy is much better for me than kubeadm
16:53:37 <sdake_> i'd like to thank jascott1 for helping get the blueprints into a state that make sense
16:53:38 <duonghq> I'm not sure if  halcyon does something better
16:53:50 <sdake_> they lead to a logical outcome of 1.0.0
16:53:57 <duonghq> sure
16:54:04 <sdake_> and duonghq helped a bit too :)
16:54:47 <v1k0d3n> duonghq: let's take offline or PM me so we can make it work.
16:54:48 <v1k0d3n> ?
16:55:11 <v1k0d3n> unless we want to talk this now here...
16:55:18 <duonghq> v1k0d3n, sure, it is already working but eat much IOPS
16:55:21 <v1k0d3n> kube-deply meaning?
16:55:25 <sdake_> for folks that are new to openstack
16:55:50 <sdake_> i'll be happy to assist on workflow issues you have
16:55:51 <sdake_> its key to learn the workflow if your a new contrib
16:55:59 <duonghq> v1k0d3n, https://github.com/kubernetes/kube-deploy <- that is, Ryan recommended it for me
16:56:02 <sdake_> that is item #2 of importance
16:56:04 <inc0> sdake_, there is good doc for that in fact
16:56:12 <sdake_> agree there are good docs
16:56:27 <portdirect> these discussions are exactly why I think we should avoid setting up the k8s cluster becoming part of the kolla-k8s scope (at least at this stage) - as there are so many options with pro's and cons to each of them
16:56:35 <sdake_> if you want help, ask for it
16:56:41 <v1k0d3n> so the issue duonghq is with pvc...which you're going to run into.
16:56:44 <inc0> portdirect, agree, minus dev env
16:56:52 <inc0> we want docs for dev env setup
16:56:54 <sdake_> portdirect agree
16:57:03 <inc0> prod - I wouldn't touch it with 1m pole
16:57:03 <sdake_> right we need a dev env 6 months ago
16:57:04 <duonghq> v1k0d3n, I'll pm you after the meeting
16:57:10 <portdirect> inc0: exactly :)
16:57:11 <v1k0d3n> ok
16:57:20 <v1k0d3n> just one thing to note team...
16:57:22 <inc0> or 3ft, if SI is hard
16:57:32 <portdirect> im in europe...
16:57:34 <v1k0d3n> that out of the box there are issues with some of the rdb pvcs
16:57:39 <sdake_> #3, sign up for work that interests you
16:57:50 <v1k0d3n> had to go with 1.5.0beta1
16:57:59 <sdake_> we have a solid core team and need to grow it
16:58:04 <sdake_> #4. need reviews
16:58:22 <portdirect> v1k0d3n: I think targetting 1.5 makes sense at this stage, esp with the changes it brings in
16:58:33 <v1k0d3n> so there are some clear dependancies required. just so devs are aware. however you get there...that's fine. we're planning on making this easier for our kolla dev team internal.
16:58:47 <v1k0d3n> oh my... portdirect absolutely.
16:58:57 <v1k0d3n> for instance, dont put any stock in petsets.
16:58:59 <sdake_> so - those are 4 guidelines i'd provide
16:59:09 <sdake_> and we are out of time :)
16:59:09 <v1k0d3n> that would be tragic without a watchful eye.
16:59:15 <inc0> allright guys, we're out of time
16:59:18 <v1k0d3n> things like that..will burn us
16:59:19 <v1k0d3n> later
16:59:27 <inc0> thank you all for coming!
16:59:32 <duonghq> thank you
16:59:39 <inc0> let's move to #openstack-kolla
16:59:43 <inc0> #endmeeting kolla