From 9df1991a80724f3179475cb9d561bfadb749822e Mon Sep 17 00:00:00 2001
From: Dan Prince <dprince@redhat.com>
Date: Thu, 23 Oct 2014 15:17:49 -0400
Subject: Compute: drive NW configuration via software conf

This example extends the compute software configuration
so that heat metadata is used to model the os-net-config
YAML (ultimately JSON) directly. The existing
os-net-config element already supports this format.

Configuring the physical network layer in this manner
would supplant the ever growing list of Heat parameters
that we have and is something that could be automatically
generated via tuskar.

The default is to use net-config-noop.yaml which
will pass no config metadata into the os-net-config
element which will essentially disable it in favor
of using parameters w/ init-neutron-ovs.

Change-Id: I30f325b1751caaef5624537e63ee27c2e418d5c8
---
 compute.yaml | 13 +++++++++++++
 1 file changed, 13 insertions(+)

(limited to 'compute.yaml')

diff --git a/compute.yaml b/compute.yaml
index ae02fef5..145b61c3 100644
--- a/compute.yaml
+++ b/compute.yaml
@@ -246,6 +246,19 @@ resources:
         - network: ctlplane
       user_data_format: SOFTWARE_CONFIG
 
+  NetworkConfig:
+    type: OS::TripleO::Net::SoftwareConfig
+
+  NetworkDeployment:
+    type: OS::TripleO::SoftwareDeployment
+    properties:
+      signal_transport: NO_SIGNAL
+      config: {get_attr: [NetworkConfig, config_id]}
+      server: {get_resource: NovaCompute}
+      input_values:
+        bridge_name: {get_param: NeutronPhysicalBridge}
+        interface_name: {get_param: NeutronPublicInterface}
+
   NovaComputeConfig:
     type: OS::TripleO::Compute::SoftwareConfig
 
-- 
cgit 1.2.3-korg