path: root/net-config-noop.yaml
diff options
authorDan Prince <dprince@redhat.com>2014-10-23 15:17:49 -0400
committerDan Prince <dprince@redhat.com>2014-12-19 21:24:56 -0500
commit9df1991a80724f3179475cb9d561bfadb749822e (patch)
treed57a88ef94033f4e974afcb7925390d61f9003fd /net-config-noop.yaml
parent741df33386b7fd78b0b95e6a9399dd53afc99f62 (diff)
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
Diffstat (limited to 'net-config-noop.yaml')
1 files changed, 18 insertions, 0 deletions
diff --git a/net-config-noop.yaml b/net-config-noop.yaml
new file mode 100644
index 0000000..a3b1d1a
--- /dev/null
+++ b/net-config-noop.yaml
@@ -0,0 +1,18 @@
+heat_template_version: 2014-10-16
+description: >
+ Software Config to no-op for os-net-config. Using this will allow you
+ to use the parameter driven (init-neutron-ovs) configuration instead.
+ OsNetConfigImpl:
+ type: OS::Heat::StructuredConfig
+ properties:
+ group: os-apply-config
+ config:
+ config_id:
+ description: The ID of the OsNetConfigImpl resource.
+ value:
+ {get_resource: OsNetConfigImpl}