Cisco Openstack

No floating IP addresses even though they're defined in the site.pp?

Bug #1089706 reported by Robert Starmer
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cisco Openstack
Fix Committed
High
Unassigned
Folsom
Fix Released
High
Chris Ricker
Cisco Openstack 2012.2.2

Bug Description

System deploys, and we've defined a floating IP range in site.pp, but there are no "pools" available in Horizon.

Revision history for this message
Daneyon Hansen (danehans) wrote :

This is related to: https://bugs.launchpad.net/openstack-cisco/+bug/1087359

The variable needs to be removed from the site manifest. In our model, Quantum manages floating IP's and not Nova.

Revision history for this message
Mark T. Voelker (mvoelker) wrote :

Per discussion at today's meeting: if you're deploying Quantum in Folsom, you can't manage floating IP's via Horizon. This is documented in the Quantum admin guide.

http://docs.openstack.org/folsom/openstack-network/admin/content/ch_limitations.html

"* Horizon does not support Routers/Floating IPs with Quantum: Horizon support is limited to operations on Quantum Networks, Subnets, and Ports. Routers and Floating IPs must be configured via CLI."

Revision history for this message
Chris Ricker (chris-ricker) wrote :

Changing status to fix committed. In line with floating IPs not being handled by Nova when using Quantum, the variable has been removed from our configuration

Changed in openstack-cisco:
status: New → Fix Committed
Mark T. Voelker (mvoelker)
Changed in openstack-cisco:
milestone: none → 2012.2.2
Mark T. Voelker (mvoelker)
Changed in openstack-cisco:
milestone: 2012.2.2 → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.