DVR FIP agent gateway does not pass traffic directed at fixed IP

[Ryan Tidwell]

When using DVR, if traffic is sent to the fixed IP of an instance using the FIP gateway as the next-hop it is dropped by the FIP gateway. The FIP gateway should act as a generic gateway to both fixed IP's and floating IP's. This is an enabler for north-south DVR without using floating IP's. I believe the FIP gateway just needs routes to point to fixed IP's the appropriate qrouter. The address scope of the external network and tenant networks should be the same if direct routing to the fixed IP is to be supported. Once this is fixed, BGP can announce the FIP gateway IP as the next-hop for each fixed IP host route accessible on the given compute node.

[Hirofumi Ichihara (ichihara-hirofumi)]

How do we pass fixed IP traffic to FIP agent gateway? Where from?

[Ryan Tidwell (ryan-tidwell)]

Traffic can be directed at the FIP agent gateway when upstream routers either have static routes for each fixed IP or if upstream routers learn the host route via a routing protocol like BGP. I encountered this issue while doing some development on Neutron BGP. I had written some code that announces a host route for each fixed IP using the FIP gateway as the next-hop. I did not include this code in Mitaka because it was late enough in the cycle that this was not going to get fixed. Leaving that code in Mitaka would effectively push routes into the infrastructure that would cause traffic to black-hole and I was concerned that it would look like buggy. If we can get this fixed it's not a heavy lift to get north-south DVR working with both IPv4 and IPv6.

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: master
Review: https://review.openstack.org/294335

[OpenStack Infra (hudson-openstack)]

Change abandoned by Swaminathan Vasudevan (<email address hidden>) on branch: master
Review: https://review.openstack.org/294335
Reason: I will be pushing a alternate on to this patch.

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: master
Review: https://review.openstack.org/297468

[Carl Baldwin (carl-baldwin)]

I'm not sure this should be an RFE. From one point of view, one would expect this to work since a central router will route the fixed IP. Should it just be a bug? Either way, I think it should be fixed. I'll add the rfe tag to match the subject and we can decide if it should be an rfe.

[Armando Migliaccio (armando-migliaccio)]

Status update:

http://eavesdrop.openstack.org/meetings/neutron_drivers/2016/neutron_drivers.2016-03-31-22.00.log.html#l-277

[Armando Migliaccio (armando-migliaccio)]

Can be treated as regular bug, if in the process we end up documenting some internals for DVR in the form a devref I could only praise the effort.

[OpenStack Infra (hudson-openstack)]

Change abandoned by Armando Migliaccio (<email address hidden>) on branch: master
Review: https://review.openstack.org/297468
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.

[Armando Migliaccio (armando-migliaccio)]

New owner?

[OpenStack Infra (hudson-openstack)]

Change abandoned by Swaminathan Vasudevan (<email address hidden>) on branch: master
Review: https://review.openstack.org/297468
Reason: The parent patch is sufficient to address all the issues, so abandoning this patch.

[Swaminathan Vasudevan (swaminathan-vasudevan)]

This bug can be closed, since this issue is right now addressed by the RFE bug.
https://bugs.launchpad.net/neutron/+bug/1577488

So this is a duplicate.