We do not need "migrated", that is an internal operation that can not be requested using a Cloud API Regards -- Ignacio M. Llorente, Full Professor (Catedratico): web http://dsa-research.org/llorente and blog http://imllorente.dsa-research.org/ DSA Research Group: web http://dsa-research.org and blog http://blog.dsa-research.org Globus GridWay Metascheduler: http://www.GridWay.org OpenNebula Virtual Infrastructure Engine: http://www.OpenNebula.org On 17/04/2009, at 14:49, Chris Webb wrote:
Thijs Metsch <Thijs.Metsch@Sun.COM> writes:
Installed --> Starting --> Running --> Stopping --> Stopped \---> Suspended --> Starting --> Running \---> Migrated \---> Copied
Hope this nice piece of ASCII arts survives :-)
It did! Could you clarify how 'migrated' and 'copied' differ from 'running'? (Migration of VMs within a cloud for load-balancing is something that should surely be completely user-transparent. Is this intended for some other purpose?)
Also, I don't follow what your 'installed' and 'starting' states are for. Surely our virtual machine is either running or not: we can't distinguish from outside whether a guest OS has fully started or not, even if we believe such a distinction is well-defined.
Cheers,
Chris.
_______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg