Expose bridge_mappings in the overcloud.
authorRobert Collins <rbtcollins@hp.com>
Fri, 17 Jan 2014 10:16:06 +0000 (23:16 +1300)
committerRobert Collins <rbtcollins@hp.com>
Thu, 23 Jan 2014 05:04:29 +0000 (18:04 +1300)
Some overclouds will want physical networks to be accessible by VMs,
and this is a component of that.

Change-Id: I5f65c040526f785b4e976f87980d94588b3fb63c

overcloud-source.yaml

index ba05e28..1128b79 100644 (file)
@@ -39,6 +39,10 @@ Parameters:
     Default: default
     Description: Name of an existing EC2 KeyPair to enable SSH access to the instances
     Type: String
+  NeutronBridgeMappings:
+    Description: The OVS logical->physical bridge mappings to use.
+    Type: String
+    Default: ''
   NeutronPassword:
     Default: unset
     Description: The password for the neutron service account, used by neutron agents.
@@ -149,7 +153,8 @@ Resources:
         NeutronNetworkType: "gre"
         NeutronEnableTunnelling: "True"
         NeutronNetworkVLANRanges: ""
-        NeutronBridgeMappings: ""
+        NeutronBridgeMappings:
+            Ref: NeutronBridgeMappings
         RabbitPassword: "guest"
   NovaCompute0:
     Type: FileInclude
@@ -284,6 +289,7 @@ Resources:
                 - Fn::GetAtt:
                   - notcompute
                   - networks
+          bridge_mappings: {Ref: NeutronBridgeMappings}
           public_interface:
             Ref: NeutronPublicInterface
           public_interface_raw_device: