[kolla][kayobe] vote: kayobe as a kolla deliverable

Michał Nasiadka mnasiadka at gmail.com
Tue Jun 25 11:53:45 UTC 2019


Thanks for clarifications Mark

Let's try - +1 for including it as Kolla deliverable.

Michal

wt., 25 cze 2019 o 13:19 Mark Goddard <mark at stackhpc.com> napisał(a):
>
> On Tue, 25 Jun 2019 at 10:09, Michał Nasiadka <mnasiadka at gmail.com> wrote:
> >
> > Hi Mark,
> >
> > Before I will vote - I would like to understand the future of Kayobe.
> >
> > Is the plan for it to stay as it is currently (Kolla on Bifrost)? Or
> > rather to evolve and fill the place of kolla-cli?
>
> I think it has potential to fill a kolla-cli like role. There are
> deployments of kayobe that do not use the bare metal deployment
> features. In that case you can still use the host configuration
> features (networking, local storage, etc). There are also some
> configuration patterns encouraged by kayobe such as version controlled
> configuration (e.g.
> https://github.com/SKA-ScienceDataProcessor/alaska-kayobe-config), and
> we intend to add support for multiple environments (dev/staging/prod)
> or regions within a single configuration repo. This does add some
> complexity on top of kolla-ansible, so there is a trade off here.
>
> >
> > If we include it as a kolla deliverable - will it not have impact on
> > it's current developers and cores?
> > We already had a kolla-cli project, and when the creators left, nobody
> > was there to pick it up...
>
> I think the main impact on existing kolla developers will be increased
> noise, due to covering kayobe topics in meetings and IRC. I wouldn't
> expect kolla cores to start working on kayobe unless they wish to. We
> already have contributors with interest only in kolla or
> kolla-ansible.
>
> I do understand your concern given the recent experience with
> kolla-cli. In that case the contributors left the community shortly
> after the project became official and we did not really integrate it
> well. It also did not see much adoption, for whatever reason. Of
> course I can't predict the future, but I would say that kayobe is
> quite different. It has been open source from the beginning, and now
> has a significant user base. The kayobe team isn't going anywhere. We
> hope that including the project as a kolla deliverable would allow it
> to continue to grow.
>
> >
> > Thanks,
> > Michal
> >
> > czw., 20 cze 2019 o 15:51 Mark Goddard <mark at stackhpc.com> napisał(a):
> > >
> > > Hi,
> > >
> > > In the most recent kolla meeting [1] we discussed the possibility of
> > > kayobe becoming a deliverable of the kolla project. This follows on
> > > from discussion at the PTG and then on here [3].
> > >
> > > The two options discussed are:
> > >
> > > 1. become a deliverable of the Kolla project
> > > 2. become an official top level OpenStack project
> > >
> > > There has been some positive feedback about option 1 and no negative
> > > feedback that I am aware of. I would therefore like to ask the kolla
> > > community to vote on whether to include kayobe as a deliverable of the
> > > kolla project. The electorate is the kolla-core and kolla-ansible core
> > > teams, excluding me. The opinion of others in the community is also
> > > welcome.
> > >
> > > If you have questions or feedback, please respond to this email.
> > >
> > > Once you have made a decision, please respond with your answer to the
> > > following question:
> > >
> > > "Should kayobe become a deliverable of the kolla project?" (yes/no)
> > >
> > > Thanks,
> > > Mark
> > >
> > > [1] http://eavesdrop.openstack.org/meetings/kolla/2019/kolla.2019-06-19-15.00.log.html#l-120
> > > [2] https://etherpad.openstack.org/p/kolla-train-ptg
> > > [3] http://lists.openstack.org/pipermail/openstack-discuss/2019-June/006901.html
> > >
> >
> >
> > --
> > Michał Nasiadka
> > mnasiadka at gmail.com



-- 
Michał Nasiadka
mnasiadka at gmail.com



More information about the openstack-discuss mailing list