[tc][kolla][kayobe] Feedback request: kayobe seeking official status

gmann at ghanshyammann.com gmann at ghanshyammann.com
Thu Jun 6 13:37:26 UTC 2019

 ---- On Thu, 06 Jun 2019 17:49:44 +0900 Mark Goddard <mark at stackhpc.com> wrote ----
 > On Thu, 6 Jun 2019 at 09:27, Thierry Carrez <thierry at openstack.org> wrote: 
 > > 
 > > Mark Goddard wrote: 
 > > > [...] 
 > > > We see two options for becoming an official OpenStack project: 
 > > > 
 > > > 1. become a deliverable of the Kolla project 
 > > > 2. become an official top level OpenStack project 
 > > > 
 > > > Given the affinity with the Kolla project I feel that option 1 seems 
 > > > natural. However, I do not want to use influence as PTL to force this 
 > > > approach. 
 > > > [...] 
 > > 
 > >  From a governance perspective, the two options are definitely possible. 
 > > 
 > > Kayobe can be seen as one of the Kolla-derived deployment tools, or it 
 > > can be seen as a new deployment tool combining two existing projects 
 > > (Kolla and Bifrost). Project teams are cheap: the best solution is the 
 > > one that best aligns to the social reality. 
 > > 
 > > So I'd say the decision depends on how much independence Kayobe wants to 
 > > have from Kolla. Having a separate project team will for example make it 
 > > easier to have separate meetings, but harder to have common meetings. 
 > > How much of a separate team is Kayobe from Kolla? How much do you want 
 > > it to stay that way? 
 > Right now the intersection of the core teams is only me. While all 
 > Kayobe contributors are familiar with Kolla projects, the reverse is 
 > not true. This is partly because Kolla and/or Kolla Ansible can be 
 > used without Kayobe, and partly because Kayobe is a newer project 
 > which typically gets adopted at the beginning of a cloud deployment. 
 > It certainly seems to make sense from the Kayobe community perspective 
 > to join these communities. I think the question the Kolla team needs 
 > to ask is whether the benefit of a more complete set of tooling is 
 > worth the overhead of adding a new deliverable that may not be used by 
 > all contributors or in all deployments. 

With my quick read on technical relation between Kolla-ansible and Kayobe,
options1 make much sense to me too. It can give more benefits of working more closely
and handle the dependencies and future roadmap etc.

And having a completely separate team (in Kayobe case you have some overlap
too even only you but that can increase in future) for repo under the same project is not
new. We have a lot of existing projects which maintain the separate team for their different
repo/deliverables without overlap. 

There are more extra work you need to consider if you go with a separate Project.
For example, PTL things and its responsibility. I would say we can avoid that in Kayobe case
because of its technical mission/relation to Kolla-ansible.


 > > 
 > > -- 
 > > Thierry Carrez (ttx) 
 > > 

More information about the openstack-discuss mailing list