yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #39043
[Bug 1468007] Re: Delete the FloatingIP Agent Gateway Port only when External Network is deleted and also delete the port based on Agents decision.
** Changed in: neutron
Status: Fix Committed => Fix Released
** Changed in: neutron
Milestone: None => liberty-rc1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1468007
Title:
Delete the FloatingIP Agent Gateway Port only when External Network is
deleted and also delete the port based on Agents decision.
Status in neutron:
Fix Released
Bug description:
FloatingIP Agent Gateway port is created on the nodes to substitute for the Gateway port, since gateway port is currently residing on the Network Node.
So it makes sense for the server to delete the FloatingIP Agent Gateway Port only when the External Gateway Port is deleted for the Router.
This would reduce the complexity in the Server side.
We should introduce an RPC call for the Floatingip Agent Gateway
ports to be removed. The Agent should take necessary action to delete
the FloatingIP Agent Gateway Port when the "last_fip_count" comes down
to 1 in the agent.
So this will be completely maintained by the agent.
This would improve the control plane performance significantly for the
Floatingip addition and deletion.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1468007/+subscriptions
References