Hi, OpenNebula has the objects cached in memory, so you cannot simply inject new data into the DB. Besides, the (live)migration operation is not only a change in the VM hostname, it involves history records, accounting, and Host capacity.
The ideal solution would be to make that load balancer ask opennebula to do the migration. If that's not possible, you could perform a dummy migration, with the following flow: - The load balancer migrates a VM - You somehow detect this migration, and execute a 'onevm livemigrate vm_id target_host' - OpenNebula will try to migrate the VM, calling the driver script /var/lib/one/remotes/vmm/<vmm_driver>/migrate This migrate script must be able to detect if the migration was already performed by the load balancer, maybe looking for a VM with the same name in the target host, and return success directly. Do you have any plans to release these new drivers? Best regards -- Carlos Martín, MSc Project Engineer OpenNebula - The Open-source Solution for Data Center Virtualization www.OpenNebula.org | [email protected] | @OpenNebula<http://twitter.com/opennebula><[email protected]> On Tue, Sep 4, 2012 at 1:57 PM, Nicolas AGIUS <[email protected]>wrote: > Hi, > > I'm currently writing a new VMM to use openNebula with a clustered xen > manager responsible of failover and loadbalancing. > > This system, put between xen and opennebula will automatically move vm by > its own. > > Is there any way to inform oned that the vm has been migrated ? > > I tried to inject this information in the database, but it did'nt work, > the update is'nt taked in account. And there is nothing about a such things > in the API. > > > Thanks, > Nicolas AGIUS > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > >
_______________________________________________ Users mailing list [email protected] http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
