Thanks, I will try that 2011/11/8 Carlos Martín Sánchez <cmar...@opennebula.org>
> Hi, > > OpenNebula names the VMs, meaning the hypervisor instances, as one-<id>. > You will probably have collisions. > > You can use this workaround: modify the pool_control table in the DB and > set the last_oid for VMs to 1000 in one of the two front-ends. > That will make one OpenNebula create VMs starting with one-1001, > one-1002... > > Regards. > -- > Carlos Martín, MSc > Project Engineer > OpenNebula - The Open Source Toolkit for Data Center Virtualization > www.OpenNebula.org | cmar...@opennebula.org | > @OpenNebula<http://twitter.com/opennebula> > > > On Mon, Nov 7, 2011 at 9:59 AM, Humberto N. Castejon Martinez < > humca...@gmail.com> wrote: > >> Hi, >> >> I know that sharing a worker node between two front-ends (i.e. having a >> worker as part of two clouds) sounds strange, and I am not thinking on >> doing it for production. I am just performing some experiments and would >> like to use the same worker from different front-ends. Provided that I use >> different VM_DIR and SCRIPTS_REMOTE_DIR for each front-end, would I >> experiment any problem. >> >> Cheers, >> Humberto >> >> _______________________________________________ >> 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