[one-users] Placement section

[Carlos Martín Sánchez]

Hi Rubén,

The PLACEMENT attribute you are using is ignored by the scheduler (take a
look at the examples in the link you provided). Try with
REQUIREMENTS = "HYPERVISOR   = \"kvm\""

If you are using the development version, you may want to try the new host
clustering feature [1] instead of using the hypervisor attribute.

Regards,
Carlos

[1] http://www.opennebula.org/documentation:rel2.0:cluster_guide

Carlos Martín, Cloud Technology Engineer/Researcher
DSA Research Group: web http://dsa-research.org and blog
http://blog.dsa-research.org
OpenNebula Open Source Toolkit for Cloud Computing:
http://www.OpenNebula.org


On 20 September 2010 10:18, Ruben Diez <rdiez at cesga.es> wrote:

> Hello:
>
> We are watching for a xen/kvm mixed set of nodes. For do this, we create
> the hosts in the following manner:
>
> - For xen nodes: onehost create  84.21.173.28 im_xen vmm_xen tm_ssh
> - For kvm nodes: onehost create  84.21.173.36 im_kvm vmm_kvm tm_ssh
>
> So, for select to run a VM in a kvm or xen node type we are using the
> "PLACEMENT" section in the following manner:
>
> PLACEMENT = [
>  REQUIREMENTS = "HYPERVISOR   = \"kvm\""
>  ]
>
> According with http://www.opennebula.org/documentation:rel2.0:template the
> "HYPERVISOR" variable is defined by default....
>
>
> But it don work: the scheduler deploy the VM in a xen node....
>
> Where are the error?? Any other manner to force a VM to be deployed in a
> xen or kvm node???
>
> Regards.
>
> _______________________________________________
> 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/20100920/84a3f504/attachment-0002.htm>