openstack team mailing list archive

[Narayan Desai <narayan.desai@xxxxxxxxx>]

On Sat, Jun 30, 2012 at 3:06 AM, Christian Parpart <trapni@xxxxxxxxx> wrote:
> Hm, Pacemaker/Corosync *inside* the VM will add the Service-IP to the local
> ethernet
> interface, and thus, the outside OpenStack components do not know about.
>
> Using a dedicated floating IP pool for service IPs might feel like a great
> solution, but
> OpenStack is not the one to manage who gets what IP - but Corosync/Pacemaker
> inside
> the KVM instances. :-)
>
> Anyone an idea how to solve this?

It sounds like you want to add explicit support to pacemaker to deal
with openstack fixed addresses. Then you could run with rfc1918
floating addresses, and then have pacemaker/corosync reassign the
(external) fixed address when consensus changes.

Think of the openstack fixed address control plane in a similar way to
ifconfig. You should even be able to script it up yourself; you'd need
to add your openstack creds to the HA images though.
 -nld