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 [yun...@gmail.com] Sent: Thursday, May 17, 2012 10:16 AM To: openstack@lists.launchpad.net Subject: [Openstack] nova state machine simplification and clarification ... _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
