The Nova/Quantum integration in Folsom does not yet proxy Nova
floating IP calls to Quantum. However, Horizon automatically
makes calls to Nova to list floating IPs, which prior to this
patch resulted in a Horizon error message due to the fact that
the Quantum integration code in Nova would raise an Unimplemented
error. This patch changes that behavior to instead return an
empty list.
This is a workaround for Folsom. The correct long-term behavior
is either to:
1) have Nova proxy all floating-ip calls to Quantum when quantum
is enabled.
2) have Horizon use the Quantum floating-ip API when Quantum
is enabled.
Reviewed: https:/ /review. openstack. org/12820 github. com/openstack/ nova/commit/ c0709bdd82c83e1 6cab6ed854d2ef8 73eb775473
Committed: http://
Submitter: Jenkins
Branch: master
commit c0709bdd82c83e1 6cab6ed854d2ef8 73eb775473
Author: Dan Wendlandt <email address hidden>
Date: Tue Sep 11 12:22:23 2012 -0700
workaround lack of quantum/nova floatingip integration
bug 1040956
The Nova/Quantum integration in Folsom does not yet proxy Nova
floating IP calls to Quantum. However, Horizon automatically
makes calls to Nova to list floating IPs, which prior to this
patch resulted in a Horizon error message due to the fact that
the Quantum integration code in Nova would raise an Unimplemented
error. This patch changes that behavior to instead return an
empty list.
This is a workaround for Folsom. The correct long-term behavior
is either to:
1) have Nova proxy all floating-ip calls to Quantum when quantum
is enabled.
2) have Horizon use the Quantum floating-ip API when Quantum
is enabled.
Change-Id: I5414d935e872a9 da108511b50e705 45d82b73347