Re: [Openstack] HA inside VMs (via Corosync/Pacemaker)

2012-06-30 Thread Steven Dake
On 06/30/2012 06:32 AM, Christian Parpart wrote: > On Sat, Jun 30, 2012 at 1:51 PM, Narayan Desai > wrote: > > On Sat, Jun 30, 2012 at 3:06 AM, Christian Parpart > wrote: > > Hm, Pacemaker/Corosync *inside* the VM will add the

Re: [Openstack] HA inside VMs (via Corosync/Pacemaker)

2012-06-30 Thread Christian Parpart
On Sat, Jun 30, 2012 at 1:51 PM, Narayan Desai wrote: > On Sat, Jun 30, 2012 at 3:06 AM, Christian Parpart > 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. > > > > U

Re: [Openstack] HA inside VMs (via Corosync/Pacemaker)

2012-06-30 Thread Narayan Desai
On Sat, Jun 30, 2012 at 3:06 AM, Christian Parpart 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 gre

Re: [Openstack] HA inside VMs (via Corosync/Pacemaker)

2012-06-30 Thread Christian Parpart
Oh, no. I use floating IPs for actually "real" public IPs. But now, that you mention the pools, well, I would have to assign one "floating IP" to at least TWO KVM instances. Hm, Pacemaker/Corosync *inside* the VM will add the Service-IP to the local ethernet interface, and thus, the outside OpenSt

Re: [Openstack] HA inside VMs (via Corosync/Pacemaker)

2012-06-29 Thread Vishvananda Ishaya
Seems like you could use a floating ip for this. You can define a range for internal floating ips by using a separate floating ip pool. On Jun 29, 2012 7:06 PM, "Christian Parpart" wrote: > Hey all, > > I would like to setup a highly available service *inside* two KVM > instances, > so I have cre