On Wed, Mar 06, 2013 at 11:44:48PM -0800, Michael MacFaden wrote: > > mrm wrote: > > > http://www.ietf.org/internet-drafts/draft-asai-vmm-mib-02.txt > > > > > > Think we need to clarify the concept of 'pause' in both admin > > > and operational states. > > juergen wrote: > > So are we all talking about the same state here and all you are looking > > for is more text? If so, what about a concerete proposal we can word > > smith? > > Sure, here's a proposed update: > > VirtualMachineAdminState ::= TEXTUAL-CONVENTION > STATUS current > DESCRIPTION > "The administrative state of a virtual machine (VM): > > on(1) The administrative state of the > virtual machine indicating the VM should > be brought online. > > off(2) The administrative state of the > virtual machine indicating the VM > should be taken offline. > > suspend(3) The administrative state of the > virtual machine where its memory and cpu execution > state has been saved to persistent store and will > be > restored at next power on(1). > > pause(4) The administrative state indicating > the virtual machine is resident in memory > but is no longer scheduled to execute by the > hypervisor." > > > SYNTAX INTEGER { > on(1), > off(2), > suspend(3) > pause(4) > }
OK. If we add an administrative suspend state, we likely also need a corresponding operational state, no? /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
