Open Stack

I don't think so. .../nova/etc seems to be where the conf files are living.

Look forward to it!

-S

 
________________________________________
From: Yun Mao [yunmao at gmail.com]
Sent: Thursday, May 24, 2012 11:46 AM
To: Sandy Walsh
Cc: openstack at lists.launchpad.net
Subject: Re: [Openstack] nova state machine simplification and clarification

Sandy,

I like the suggestion of graphvis, although I haven't used it for a
while. Is there a dir in nova appropriate to put .dot files? I was
hoping to get the proposal discussed a few round, and while it's
getting stabilized, we can work on the graphvis representation.
Thanks,

Yun

On Wed, May 23, 2012 at 11:28 AM, Sandy Walsh <sandy.walsh at rackspace.com> wrote:
> Hi Yun,
>
> I like the direction you're going with this. Unifying these three enums would be a great change. Honestly it's really just combing two enums (vm & task) and using power state as a tool for reconciliation (actual != reality).
>
> Might I suggest using graphvis instead of a spreadsheet? That way we can keep it under version control, have funky pictures and there are libraries for parsing .dot files in Python. Also we can use the graphvis doc to actually drive the state machine (via attributes on nodes/edges)
>
> I'd like to see more discussion on how reconciliation will be handled in the event of a conflict.
>
> Cheers!
> -S
>
> ________________________________________
> From:  Yun Mao [yunmao at gmail.com]
> Sent: Thursday, May 17, 2012 10:16 AM
> To: openstack at lists.launchpad.net
> Subject: [Openstack] nova state machine simplification and clarification
>
> ...