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 OpenStack
On Sat, Jun 30, 2012 at 3:06 AM, Christian Parpart tra...@gmail.com 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
On Sat, Jun 30, 2012 at 1:51 PM, Narayan Desai narayan.de...@gmail.comwrote:
On Sat, Jun 30, 2012 at 3:06 AM, Christian Parpart tra...@gmail.com
wrote:
Hm, Pacemaker/Corosync *inside* the VM will add the Service-IP to the
local
ethernet
interface, and thus, the outside OpenStack
On 06/30/2012 06:32 AM, Christian Parpart wrote:
On Sat, Jun 30, 2012 at 1:51 PM, Narayan Desai narayan.de...@gmail.com
mailto:narayan.de...@gmail.com wrote:
On Sat, Jun 30, 2012 at 3:06 AM, Christian Parpart tra...@gmail.com
mailto:tra...@gmail.com wrote:
Hm,
Hey all,
I would like to setup a highly available service *inside* two KVM instances,
so I have created a security group to contain all required service ports,
so clients can connect to either VM and that works.
And both instances have their own designated IP address, provided by
nova itself.
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 tra...@gmail.com wrote:
Hey all,
I would like to setup a highly available service *inside* two KVM
instances,
so
6 matches
Mail list logo
