Better document $controller_node_internal and $controller_node_public

Bug #1097065 reported by Michael DeHaan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cisco Openstack
Fix Released
Medium
Pradeep Kilambi
Grizzly
Fix Released
Medium
Pradeep Kilambi

Bug Description

These two settings in site.pp are somewhat confusing and don't really explain what they do. You have to grep through the puppet modules to get there.

Controller node public should say "This is the interface that you will use to connect to the Horizon GUI" or similar

Controller node internal should say "This is the interface that will be used for external backend communication" or similar

Michael DeHaan (mdehaan)
Changed in openstack-cisco:
importance: Undecided → Medium
Revision history for this message
Daneyon Hansen (danehans) wrote :

nd now we also have a cross_talk_ip. We need to remove the overlap of these variables.

Revision history for this message
Ian Wells (ijw-ubuntu) wrote :

They do technically serve separate functions (crosstalk_ip is where the GRE tunnels terminate and as you might want your Openstack-internal network not to be flooded by customer traffic you might want to separate the two) but for 99% of people I don't think the separation is important.

Revision history for this message
Ian Wells (ijw-ubuntu) wrote :

We agreed that, in the event that a client wants separate IPs, that's quite a technical decision and it can still be implemented in the manifest file anyway (rather than the modules) so it's acceptable to simplify to manifests for the far more common case.

Revision history for this message
Pradeep Kilambi (pkilambi) wrote :
no longer affects: openstack-cisco/folsom
Changed in openstack-cisco:
status: In Progress → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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