Updated openstack/openstack
Project: openstack/neutron  f350f1a6c9d6fb1e572654d4f4ecdd50f92141b3
null
allow delete_port to work when there are multiple floating ips

It is possible to associate multiple floating ip addresses with a single
port through the use of multiple *fixed* ip addresses, e.g.:

    nova boot ... --nic net-id=my-net-id myserver
    nova add-fixed-ip myserver my-net-id
    nova add-floating-ip --fixed-address x.x.x.1 myserver y.y.y.y.1
    nova add-floating-ip --fixed-address x.x.x.2 myserver y.y.y.y.2

In this situation, neutron.db.l3_db.disassociate_floatingips would throw
an exception:

    Exception: Multiple floating IPs found for port <port-id>

This would prevent someone from deleting an instance that was associated
with multiple floating ips.

This patch corrects disassociate_floatingips so that it will
disassociate all floating ips associated with the port, allowing the
delete operation to proceed correctly.

Change-Id: I68a2131fa8ee80828354c9db4ac405c3f77c3b90
Closes-bug: 1302701
Updated openstack/openstack
Project: openstack/nova  d98eddc467f15c5a268a13136cdf279a41aa7658
null
Ensure info cache updates don't overwhelm cells

Cells does its own healing of the info cache outside
of get_instance_nw_info, so we have double healing
happening if info_cache_cells_update is called for every
get_instance_nw_info. This also overwhelms cells'
ability to keep the global db updated at scale. Similar
functionality exists in nova/network/api.py.

Change-Id: I58f681f3674d826e3dce4fa956e2eb0e4c60f82b