[openstack-dev] [all] Switching to longer development cycles
jazeltq at gmail.com
Thu Dec 14 08:20:11 UTC 2017
Thanks a lot to open this topic. I want to open this topic like this
some times, but i thought, may be myself is too sensitive?
To me, i found as Openstack mature, the developer is less valuable.
The devs can install it then teach user to
use it, then ok the deal is done. The Openstack in many companies is
just maintained, not develop forward.
No attractive feature is include in.
One reason is the IaaS does not need too much feature. If the vm is
ok, and can be
connected, It is ok. Let other people to develop it.
One reason is as public cloud goes popular, users have multiple
choices. Openstack is just one, and the less attractive one.
Only the company do not want, or not allowed, to use public cloud
may be want to use Openstack.
One reason is the time changed, right now every body talks about AI. I
attend one storage reference, all people talks about AI,
they said, we will make storage more intelligent, if we do not do
this, we will be eliminated.
May be we should give new mission to Openstack to refresh it ?
Thanks a lot again.....
2017-12-14 15:39 GMT+08:00 Blair Bethwaite <blair.bethwaite at gmail.com>:
> The former - we're running Cells so only have a single region currently
> (except for Swift where we have multiple proxy endpoints around the country,
> all backed by a global cluster, but they have to be different regions to put
> them all in the service catalog). See
> https://trello.com/b/9fkuT1eU/nectar-openstack-versions for the current
> version snapshot.
> On 14 Dec. 2017 18:00, "Clint Byrum" <clint at fewbar.com> wrote:
>> Excerpts from Blair Bethwaite's message of 2017-12-14 17:44:53 +1100:
>> > On 14 December 2017 at 17:36, Clint Byrum <clint at fewbar.com> wrote:
>> > > The batch size for "upgrade the whole cloud" is too big. Let's help
>> > > our
>> > > users advance components one at a time, and then we won't have to
>> > > worry
>> > > so much about doing the whole integrated release dance so often.
>> > Is there any data about how operators approach this currently? Nectar
>> > (and I presume other large and/or loosely coordinated OpenStack
>> > clouds) has been running different projects across multiple versions
>> > for quite a while, sometimes 3 or 4 different versions. Coordinating
>> > upgrades in a federated cloud with distributed operations requires
>> > that we do this, e.g., our current Nova Newton upgrade has probably
>> > been in-train for a couple of months now.
>> That's interesting. Can you share what you mean by running 3 or 4
>> different versions?
>> Do you mean you mix versions in a single region, like, Pike keystone,
>> Ocata Nova, and Newton Neutron? Or do you mean you might have a region
>> running Pike, and another running Ocata, and another running Newton?
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev