[openstack-dev] [all] Switching to longer development cycles

Joshua Harlow harlowja at fastmail.com
Thu Dec 21 22:37:54 UTC 2017

My 3 cents are that this isn't something that u get asked to put in from 
operators, it's something that is built in from the start. Just look at 
other workflow systems (which is really what nova/cinder/neutron... 
are); they don't try to add this functionality in later (or they 
shouldn't at least) but c'est la vie...

With that stated I would agree this is a community-wide goal (and a very 
very hard one since every single project 'forgot' to build this in from 
the start).

(another example of another projects UI that does something similar).

Matt Riedemann wrote:
> On 12/19/2017 2:29 PM, Joshua Harlow wrote:
>> * Clear workflow state (and transition) 'machine' that is followed in
>> code and can be used by operators/others such as UI developers to get
>> a view on what nova is or is not doing (may fit under the broad topic
>> of observability?)
>> Take for example
>> http://flower.readthedocs.io/en/latest/screenshots.html and ask
>> yourself why nova-compute (or nova-conductor or nova-scheduler...)
>> doesn't have an equivalent kind of 'viewer' (and no it doesn't need to
>> be flower, that's just an example...)
> OK...first I've heard of this too. Is this something that the majority
> of people deploying, operating and/or using Nova are asking for as a
> priority?
> Also, this doesn't just seem like a nova thing - this smells like a
> community-wide goal.

More information about the OpenStack-dev mailing list