Comment 7 for bug 1040956

The workaround for this particular error message in Nova is trivial:

diff --git a/nova/network/quantumv2/api.py b/nova/network/quantumv2/api.py
index 990af4c..7db4525 100644
--- a/nova/network/quantumv2/api.py
+++ b/nova/network/quantumv2/api.py
@@ -254,7 +254,7 @@ class API(base.Base):
         raise NotImplementedError()

     def get_floating_ips_by_project(self, context):
- raise NotImplementedError()
+ return []

     def get_floating_ips_by_fixed_address(self, context, fixed_address):
         raise NotImplementedError()

However, after thinking about this more, I think its really that we either need to:

1) actually proxy Nova Floating IP calls to Quantum
2) prevent Horizon from calling Nova floating IP calls (here and elsewhere) when Quantum is enabled.

The reason is that it doesn't seem right for Horizon to suggest that there are working floating IPs when there are not.

Our original plan was to do #1 as part of F-3 but this bug wasn't finished then and working on it as an FFE stalled and the current author seems to not actively be doing anything (https://bugs.launchpad.net/quantum/+bug/1031119).

Akihiro has volunteered to do this work. I think it would be great for him to do this, and I think it would be pretty straightforward. That said, this is a change in Nova and is definitely non-trivial, so its not clear that it should be added for Folsom. That call is up to the Nova folks. It can definitely be put in Grizzly though.