[one-users] Deploy VM on hold state

[Manuel Peuster]

Hello Antonio,

I also tried to hold a VM directly after it is allocated to prevent it from scheduling. But this dosen't work very good for me.

I have used a trick to keep VMs in "pending" state to perform the deployment action manually. So no hold is needed.

Just add 'REQUIREMENTS = "FALSE"' to a VM template that should not automatically be deployed. This will cause the scheduler to ignore it.

But for this solution you will unfortunately need different templates for your  different "groups" of VMs .

Regards, Manuel


On 02.04.2012, at 23:21, Antonio Carlos Salzvedel Furtado Junior wrote:

> Hello Opennebula users,
> 
> I was reading the OpenNebula documentation, and there is the following statement about the Hold state:
> "The owner has held the VM and it will not be scheduled until it is released. It can be, however, deployed manually."
> 
> 
> I'm trying to deploy a VM on hold, but I get the message "[VirtualMachineDeploy] Wrong state to perform action".
> Currently, I'm only being able to deploy pending VMs. I don't have a RANK policy because I just want the manual deployment.
> 
> I'm also a bit confused because the documentation refers to this diagram: http://opennebula.org/_detail/documentation:rel3.0:states-complete.png
> It does not show that it is possible to deploy from Hold.
> 
> There is only a group of VMs that I don't want to be scheduled, so I'm using the same template for them. If I don't hold them, will the scheduler try to deploy?
> 
> 
> 
> 
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20120403/5f457515/attachment-0002.htm>