yahoo-eng-team team mailing list archive

[Abhishek Chanda <abhishek@xxxxxxxxxxxxxxxx>]

Public bug reported:

I am running two neutron L3 agents on two physical machines. Once
neutron is up and running, and HA routers are created, I was hoping to
get the allocated VIP and route to it from another network (external to
my cloud). This would allow my VMs to reach the external network.
However, I have two problems:

1. The parent VIP range seems hardcoded in
https://github.com/openstack/neutron/blob/6bd91060f1d6db1d33c810deb9feefcb0258bde5/neutron/agent/linux/keepalived.py#L160
and this is a link local range. Thus, there is no easy way to route the
link local VIP out to another network.

2. There is no API that exposes the VIP

It seems the VIP range should be configurable.
Is there an easy way to do what I need to do here? Or is it not a supported use case?

** Affects: neutron
     Importance: Undecided
         Status: New

** Summary changed:

- Cannot expose VIP from neutron L3 HA
+ Cannot expose VIP for neutron L3 HA

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1450882

Title:
  Cannot expose VIP for neutron L3 HA

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  I am running two neutron L3 agents on two physical machines. Once
  neutron is up and running, and HA routers are created, I was hoping to
  get the allocated VIP and route to it from another network (external
  to my cloud). This would allow my VMs to reach the external network.
  However, I have two problems:

  1. The parent VIP range seems hardcoded in
  https://github.com/openstack/neutron/blob/6bd91060f1d6db1d33c810deb9feefcb0258bde5/neutron/agent/linux/keepalived.py#L160
  and this is a link local range. Thus, there is no easy way to route
  the link local VIP out to another network.

  2. There is no API that exposes the VIP

  It seems the VIP range should be configurable.
  Is there an easy way to do what I need to do here? Or is it not a supported use case?

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1450882/+subscriptions