Hi Prakashan, There are different options to control the placement of the VMs.
If you want to manually deploy them, you can hold the VMs (onevm hold <id>). The scheduler won't place these machines, but you can still deploy them with onevm deploy. Or you could start only the OpenNebula daemon without the scheduler (take a look at the 'one' start script, and comment the ONE_SCHEDULER part). The other option is to use the REQUIREMENTS and RANK VM template attributes, see [1]. The scheduler will read them, and place the VM accordingly. You can require the VM to be deployed in a specific host or cluster; or modify the RANK expression to set the hosts priority. Regards, Carlos. [1] http://opennebula.org/documentation:rel2.0:template#placement_section 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 7 February 2011 21:04, Prakashan Korambath <p...@ats.ucla.edu> wrote: > Hi, > > I noticed that by default the scheduler automatically pick the host when > more than one hosts are available to deploy immediately after onevm create > command. The onevm deploy command only works when for some reason the > scheduling goes into pending state for a while. > > I am looking for little more documentation on various options for deploying > the virtual images on the host of our choice. If someone can share the > configuration as to how they deploy OpenNebula in a cluster environment that > would be great. > > I am using CentOS 5.5 64 bit with OpenNebula 2.0.1 and running Xen on the > cluster nodes. > > Thanks, > > Prakashan > _______________________________________________ > Users mailing list > Users@lists.opennebula.org > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org >
_______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org