yahoo-eng-team team mailing list archive

[Swaminathan Vasudevan <souminathan@xxxxxxxxx>]

Public bug reported:

When unbound ports are associated with floatingIP in DVR, it implements the floatingIP in the dvr_snat node under the snat_namespace.
When the private ports are bound to a specific host, the floatingIPs are not moved or migrated to their respective hosts.

This can be reproduced by 
1. Create a network
2. Create a subnet
3. Create a router and associate the subnet to the router
4. Assign a gateway to the router.
5. Then create a port on the given network with a specific IP.
6. Now create a FloatingIP on the external network.
7. Associate the FloatingIP to the created port.
8. At this point the port is not bound and so the floatingIP gets implemented in the Snat_namespace in the dvr_snat node.
9. Then within a few seconds, we create a VM with the given port-id instead of network-id.
10. Now when the VM is built then the port gets bound.
11. Now the floatingIP is not seen on the host where the VM resides.

Theoretically the FloatingIP should be migrated to the host where it is
currently bound.

** Affects: neutron
     Importance: Undecided
     Assignee: Swaminathan Vasudevan (swaminathan-vasudevan)
         Status: Confirmed


** Tags: l3-dvr-backlog

** Changed in: neutron
       Status: New => Confirmed

** Changed in: neutron
     Assignee: (unassigned) => Swaminathan Vasudevan (swaminathan-vasudevan)

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

Title:
  DVR: Migrate centralized unbound floatingip to the respective host
  when  the port is bound

Status in neutron:
  Confirmed

Bug description:
  When unbound ports are associated with floatingIP in DVR, it implements the floatingIP in the dvr_snat node under the snat_namespace.
  When the private ports are bound to a specific host, the floatingIPs are not moved or migrated to their respective hosts.

  This can be reproduced by 
  1. Create a network
  2. Create a subnet
  3. Create a router and associate the subnet to the router
  4. Assign a gateway to the router.
  5. Then create a port on the given network with a specific IP.
  6. Now create a FloatingIP on the external network.
  7. Associate the FloatingIP to the created port.
  8. At this point the port is not bound and so the floatingIP gets implemented in the Snat_namespace in the dvr_snat node.
  9. Then within a few seconds, we create a VM with the given port-id instead of network-id.
  10. Now when the VM is built then the port gets bound.
  11. Now the floatingIP is not seen on the host where the VM resides.

  Theoretically the FloatingIP should be migrated to the host where it
  is currently bound.

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