[one-users] option to prevent a VM instance from being deployed

[Carlos Martín Sánchez]

Hi,

That is what the command 'onevm hold' [1] does. But that command requires
you to instantiate the template, and then quickly hold the new VM.
For the next version we will add the option to create the new VMs directly
on hold instead of pending [2].

Meanwhile, if you don't want to instantiate & hold, you can also use this
workaround: Add an imposible requirement [3], such as REQUIREMENTS="NAME =
NONEXISTENTHOST". The scheduler won't be able to find a suitable host, but
you can still deploy that VMs manually.

Regards

[1]
http://opennebula.org/documentation:rel3.8:vm_guide_2#life-cycle_operations
[2] http://dev.opennebula.org/issues/1103
[3]
http://opennebula.org/documentation:rel3.8:template#requirement_expression_syntax

--
Carlos Martín, MSc
Project Engineer
OpenNebula - The Open-source Solution for Data Center Virtualization
www.OpenNebula.org | cmartin at opennebula.org |
@OpenNebula<http://twitter.com/opennebula><cmartin at opennebula.org>


On Wed, Dec 19, 2012 at 10:22 PM, Hyun Woo Kim <hyunwoo at fnal.gov> wrote:

>  Hi Open Nebula developers and users,
>
>  Is it possible to prevent a VM instance from being deployed
> automatically after a couple of seconds?
> When we do "onetemplate instantiate N",
> the new VM will stay at "PEND" briefly and go to "PROL" in just a few
> seconds, right?
>
>  For a certain types of templates, we would like to make
> the virtual machines (in the PEND state) to wait for admin's
> command "onevm deploy"
> (to be sent to a specific set of hosts)..
>
>  Hyunwoo
> FermiCloud Project
>
>
> _______________________________________________
> 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/20121220/3a50f682/attachment-0002.htm>