yahoo-eng-team team mailing list archive

["Baodong \(Robert\) Li" <baoli@xxxxxxxxx>]

Public bug reported:

investigation on the floatingip API revealed a few issues:
  -- if the external network is associated with multiple subnets, one IP address from each of the subnets is allocated. But the ip address used for the floating ip is picked up randomly. For example, a network could have both an ipv6 and an ipv4 subnet. In my tests, for one of such network, it picked up the ipv4 address; for the other, it picked up the ipv6 address. 
  -- given that one IP is allocated from each subnet, addresses not used for floating ip is wasted.
  -- Most likely, ipv6 floating ip (with the same mechanism as ipv4) won't be supported. But the API allows ipv6 addresses to be used as floating ip.
  -- it allows an IPv4 floating ip to be associated with a port's ipv6 addresses, and vice versa.

In general, the behavior/semantics involved in the floating IP API needs
to be looked at in the context of dual stack or ipv6 only network.

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: ipv6

** Tags added: ipv6

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

Title:
  Incorrect Floating IP behavior  in dual stack or ipv6 only network

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  investigation on the floatingip API revealed a few issues:
    -- if the external network is associated with multiple subnets, one IP address from each of the subnets is allocated. But the ip address used for the floating ip is picked up randomly. For example, a network could have both an ipv6 and an ipv4 subnet. In my tests, for one of such network, it picked up the ipv4 address; for the other, it picked up the ipv6 address. 
    -- given that one IP is allocated from each subnet, addresses not used for floating ip is wasted.
    -- Most likely, ipv6 floating ip (with the same mechanism as ipv4) won't be supported. But the API allows ipv6 addresses to be used as floating ip.
    -- it allows an IPv4 floating ip to be associated with a port's ipv6 addresses, and vice versa.

  In general, the behavior/semantics involved in the floating IP API
  needs to be looked at in the context of dual stack or ipv6 only
  network.

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