Open Stack

Re: "One OpenStack" product

Is vim, less, awk, sed, and emacs one product? Are the bolt and nut of same
size (and produced by same manufacturer) sitting in a hardware store a
single product? A vote or edict does not automatically make things one
product - it only conveys a desire. I would argue that OpenStack is closer
to being a single, very large toolkit (instead of a product) that can be
configured and used in many different ways. For those that do consider it a
single product -- have you tried watching someone brand new to OpenStack
try to roll it out (not devstack)? If you still consider it a product, what
are the competing products and how easy are they to use?

In my view, a 'product' has a certain level of integration and common-ness
about it (still vague, I know). Some may argue that a product is
indivisible (or not readily indivisible).

-paul

On Fri, Sep 9, 2016 at 5:22 AM, John Davidge <John.Davidge at rackspace.com>
wrote:

> Thierry Carrez wrote:
>
> >[...]
> >In the last years there were a lot of "questions" asked by random
> >contributors, especially around the "One OpenStack" principle (which
> >seems to fuel most of the reaction here). Remarks like "we should really
> >decide once and for all if OpenStack is a collection of independent
> >projects, or one thing".
> >
> >A lot of people actually ignore that this question was already asked,
> >pretty early on (by John Dickinson in June 2011). Back then it was
> >settled by the PPB (the ancestor to the TC). You can read it all
> >here[1]. It was never brought again as a proposed change to the TC, so
> >that decision from June 2011 is still defining how we should think about
> >OpenStack.
> >
> >Most of the TC members know the governance history and know those
> >principles. That is, after all, one of the reasons you elect them for.
> >But we realized that the people asking those questions again and again
> >were not at fault. It was our failure to *document* this history
> >properly which caused the issue. Took us some time to gather the courage
> >to write it, then finally Monty wrote a draft, and I turned it into a
> >change.
>
> To provide a counter point, I think the reason this question is asked so
> often is not because the TC has failed to *document* this policy, but that
> it has failed to *comply* with it.
>
> I¹m of course referring to the introduction of The Big Tent. This is the
> moment that OpenStack stopped being: ³A single product made of a lot of
> independent, but cooperating, components.² And became: ³A collection of
> independent projects that work together for some level of integration and
> releases.²
>
> This is in direct contradiction to the stated and collectively understood
> goal of the project, and has left many scratching their heads.
>
> The principles as written in the review do not accurately describe the
> current state of the project. To make it so that they do, we either need
> to change the principles or change the project. As I see it, our options
> are:
>
> 1. Adjust the project to reflect the principles by abolishing The Big Tent.
> 2. Adjust the principles to reflect the project by redefining it as: ³A
> collection of independent projects that work together for some level of
> integration and releases.²
>
> Personally, my vote is for option 1.
>
> John
>
>
> ________________________________
> Rackspace Limited is a company registered in England & Wales (company
> registered number 03897010) whose registered office is at 5 Millington
> Road, Hyde Park Hayes, Middlesex UB3 4AZ. Rackspace Limited privacy policy
> can be viewed at www.rackspace.co.uk/legal/privacy-policy - This e-mail
> message may contain confidential or privileged information intended for the
> recipient. Any dissemination, distribution or copying of the enclosed
> material is prohibited. If you receive this transmission in error, please
> notify us immediately by e-mail at abuse at rackspace.com and delete the
> original message. Your cooperation is appreciated.
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160909/83d540eb/attachment.html>