From f0e61d11fc949cb9ebc3d2b875fdb79335ed0d33 Mon Sep 17 00:00:00 2001 From: Robert Collins Date: Fri, 7 Feb 2014 15:37:45 +1300 Subject: Make it possible to do physical networks for VMs. This patch makes it possible to setup physical networks for VMs, separate to the control plane configuration which is needed for routed/natted access to physical networks. Future work is needed to automate ci-overcloud configuration of the control plane where we need two distinct bridges, but this is enough to stop folk dying of boredom setting up a sizeable ci-overcloud. Change-Id: I6ac7129f22bb797467adb0408638781d20081f19 --- overcloud-source.yaml | 12 ++++++++++++ 1 file changed, 12 insertions(+) (limited to 'overcloud-source.yaml') diff --git a/overcloud-source.yaml b/overcloud-source.yaml index bdbf7219..7fd7505f 100644 --- a/overcloud-source.yaml +++ b/overcloud-source.yaml @@ -81,6 +81,14 @@ Parameters: Type: String Default: '' Description: If set, flat networks to configure in neutron plugins. + HypervisorNeutronPhysicalBridge: + Default: '' + Description: An OVS bridge to create on each hypervisor. + Type: String + HypervisorNeutronPublicInterface: + Default: '' + Description: What interface to add to the HypervisorNeutronPhysicalBridge. + Type: String NeutronPublicInterface: Default: eth0 Description: What interface to bridge onto br-ex for network nodes. @@ -165,6 +173,10 @@ Resources: NeutronFlatNetworks: Ref: NeutronFlatNetworks NeutronNetworkVLANRanges: "" + NeutronPhysicalBridge: + Ref: HypervisorNeutronPhysicalBridge + NeutronPublicInterface: + Ref: HypervisorNeutronPublicInterface NeutronBridgeMappings: Ref: NeutronBridgeMappings RabbitPassword: "guest" -- cgit 1.2.3-korg