[one-users] Update hostname after a migration

[Carlos Martín Sánchez]

Hi,

That sounds very promising, let us know if you run into any other problems.
Once it is finished, you may want to contribute the project to the
ecosystem [1].

Cheers

[1] http://opennebula.org/community:ecosystem
--
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, Sep 5, 2012 at 1:05 PM, Nicolas AGIUS <nicolas.agius at lps-it.fr>wrote:

> Hi,
>
> Thanks for the answer. The second solution sounds good, will try this.
>
> The first one is not possible. This sytem also handle failover and have to
> react to a failure within a few seconds. For example, if a node crashes,
> lost vm are immediately respawned on a healthy node. This is why it's
> running as closer as possible from the hypervisor and can't rely on any
> external component.
>
>
> This drivers and the complete cluster stack will be released soon.
>
> Regards,
> Nicolas AGIUS
>
> --- En date de : *Mar 4.9.12, Carlos Martín Sánchez <
> cmartin at opennebula.org>* a écrit :
>
>
> De: Carlos Martín Sánchez <cmartin at opennebula.org>
> Objet: Re: [one-users] Update hostname after a migration
> À: nicolas.agius at lps-it.fr
> Cc: users at lists.opennebula.org
> Date: Mardi 4 septembre 2012, 16h03
>
>
> 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 | cmartin at opennebula.org<http://mc/compose?to=cmartin@opennebula.org>|
> @OpenNebula <http://twitter.com/opennebula><http://mc/compose?to=cmartin@opennebula.org>
>
>
>
> On Tue, Sep 4, 2012 at 1:57 PM, Nicolas AGIUS <nicolas.agius at lps-it.fr<http://mc/compose?to=nicolas.agius@lps-it.fr>
> > 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
> Users at lists.opennebula.org<http://mc/compose?to=Users@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/20120905/f38f3779/attachment-0002.htm>