Multi-interface Controller support

Bug #1090447 reported by Daneyon Hansen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cisco Openstack
Critical
Daneyon Hansen
Folsom
Medium
Robert Starmer

Bug Description

We must setup 2 interfaces on the controller for the environment to work.

Changed in openstack-cisco:
status: New → Confirmed
Revision history for this message
Daneyon Hansen (danehans) wrote :

Controllers need 2 interfaces for our networking model to function properly. One interface is used for API/GRE endpoints and the other is configured for bridging and is used by Quantum/OVS for VM external connectivity. See this commit for details:

https://github.com/danehans/folsom-manifests/commit/f82ebc46fe993453151c07a268cddbae4019a8a5#commitcomment-2320125

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

Daneyon has the aforementioned patch included in a pull request:

https://github.com/CiscoSystems/folsom-manifests/pull/21

However per the review it looks like this pull request needs more work to get it in shape for merging.

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

Assigning over to Ian to verify whether this got fixed in the recent repo swap.

Revision history for this message
Robert Starmer (starmer) wrote :

Current model still (and in the near future) will require multiple interfaces. A single interface model (for those customers that can / want to use this) is being investigated.

This is only important if nova is expected to provide/manage metadata/dhcp services.

Revision history for this message
Robert Starmer (starmer) wrote :

Single interface support can be addressed in a future release. The goal would be to allow the external interface (API) and public network to be the same for some use cases (development environments for example).

A fix that's been evaluated, but not tested to scale is to migrate the external network address onto the external bridge interface, and using the same address for both public and external networks. This still requires a route for metadata, but that route then can reside on the control node.

I recommend reducing this to medium or high for the next release.

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

Reducing sev for now per Robert's note.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers