On Fri, Aug 30, 2013 at 06:08:10PM +0900, SHIMA Keiichi wrote: > > If I'm not missing, there is no other explanation about how the vmOperState > should behave. Maybe we need more concrete description in the vmOperState > section. Currently, it just says as below. > > "The current operational state of the virtual machine." >
I think this is pretty clear - it is the _current_ _operational_ state and indeed a virtual machine may cycle between states or it may go through a sequence of state changes while carrying out a complex administrative action like migrate from hypervisor A to B. The MIB module is not modeling such administrative actions - its aim is only to report what is actually happening for monitoring or troubleshooting purposes. In other words, if you instruct your hypervisor controller to migrate a virtual machine from hypervisor A to B, then the MIB module allows you to monitor how this migration process is carried out. I see this very similar to process states and process state changes at the operating system level. If you, for example, tell an application to terminate, then the underlying processes still go through a sequence of state changes until they finally (hopefully) disappear. > Also, if we keep the blocked state and the state machine figure, > then it would be better to provide a complete state transition > table. The current figure-style state machine lacks transition > flows between the blocked state and other states. I don't want to > draw that part in the figure, since it will mess up the figure :) > How about adding a separate table in a appendix section? Perhaps we can add an arrow from running to blocked and another from blocked to running. But I would not try to cover all possible transitions since you can transition into the crashed state from many states. /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 <http://www.jacobs-university.de/> _______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
