Open Stack

On 04/24/2015 05:06 AM, loy wolfe wrote:
> It's already away from the original thread, so I start this new one,
> also with some extra tag because I think it touch some corss-project
> area.
> 
> Original discuss and reference:
> http://lists.openstack.org/pipermail/openstack-dev/2015-April/062384.html
> https://review.openstack.org/#/c/176501/1/specs/liberty/reference-split.rst
> 
> Background summary:
> All in-tree implementation would be splitted from Openstack
> networking, leaving Neutron as a naked "API/DB" platform, with a list
> of out-tree implementation git repos, which are not maintained by core
> team any more, but may be given a nominal "big tent" under the
> Openstack umbrella.
> 
> Motivation: a) Smaller core team only focus on the in-tree API/DB
> definition, released from concrete controlling function
> implementation; b) If there is official implementation inside Neutron,
> 3rd external SDN controller would face the competition.
> 
> I'm not sure whether it's exactly what cloud operators want the
> Openstack to deliver. Do they want a off-the-shelf package, or just a
> framework and have to take the responsibility of integrating with
> other external controlling projects? A analogy with Linux that only
> kernel without any device driver has no use at all.

>From my perspective, the repo split is really just an implementation
detail and not so much about what's being delivered.  It happened to one
easy way with our current tooling to create separate review teams for
different parts of the code.  It may also mean that things are split up
into more packages.  I would suggest looking at what the project
produces and delivers as the collection of these things.  When you look
at the collection, what is being developed and delivered is generally
the same (the common API, etc code, and various backends).

-- 
Russell Bryant