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

Matt Riedemann mriedemos at gmail.com
Fri Dec 22 00:27:23 UTC 2017

On 12/21/2017 4:37 PM, Joshua Harlow wrote:
> 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).
> https://raw.githubusercontent.com/spotify/luigi/master/doc/visualiser_front_page.png 
> (another example of another projects UI that does something similar).

Seems like something you could build based on consuming the notification 
RPC queue events in an external system. Most operations in nova have a 
start/end/error notification sequence. You can track when there are 
tasks running based on the start events, and when they finish based on 
the end/error events.

So, this is something you could build with what's available, as a 
separate optional dashboard thing. Not everything needs to be baked 
directly into a project as long as that project provides the APIs for 
consumers to build from it. Very similar concept with the zaqar thing 
that was discussed in the -tc channel yesterday.




More information about the OpenStack-dev mailing list