Open Stack

On Aug 14, 2014 2:04 AM, "Eoghan Glynn" <eglynn at redhat.com> wrote:
>
>
> > >> Letting the industry field-test a project and feed their experience
> > >> back into the community is a slow process, but that is the best
> > >> measure of a project's success. I seem to recall this being an
> > >> implicit expectation a few years ago, but haven't seen it discussed
in
> > >> a while.
> > >
> > > I think I recall us discussing a "must have feedback that it's
> > > successfully deployed" requirement in the last cycle, but we
recognized
> > > that deployers often wait until a project is integrated.
> >
> > In the early discussions about incubation, we respected the need to
> > officially recognize a project as part of OpenStack just to create the
> > uptick in adoption necessary to mature projects. Similarly, integration
is a
> > recognition of the maturity of a project, but I think we have graduated
> > several projects long before they actually reached that level of
maturity.
> > Actually running a project at scale for a period of time is the only
way to
> > know it is mature enough to run it in production at scale.
> >
> > I'm just going to toss this out there. What if we set the graduation
bar to
> > "is in production in at least two sizeable clouds" (note that I'm not
saying
> > "public clouds"). Trove is the only project that has, to my knowledge,
met
> > that bar prior to graduation, and it's the only project that graduated
since
> > Havana that I can, off hand, point at as clearly successful. Heat and
> > Ceilometer both graduated prior to being in production; a few cycles
later,
> > they're still having adoption problems and looking at large
architectural
> > changes. I think the added cost to OpenStack when we integrate immature
or
> > unstable projects is significant enough at this point to justify a more
> > defensive posture.
> >
> > FWIW, Ironic currently doesn't meet that bar either - it's in
production in
> > only one public cloud. I'm not aware of large private installations yet,
> > though I suspect there are some large private deployments being spun up
> > right now, planning to hit production with the Juno release.
>
> We have some hard data from the user survey presented at the Juno summit,
> with respectively 26 & 53 production deployments of Heat and Ceilometer
> reported.
>
> There's no cross-referencing of deployment size with services in
production
> in those data presented, though it may be possible to mine that out of the
> raw survey responses.

Indeed, and while that would be useful information, I was referring to the
deployment of those services at scale prior to graduation, not post
graduation.

Best,
Devananda
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140814/eb573408/attachment.html>