Compute: drive NW configuration via software conf
authorDan Prince <dprince@redhat.com>
Thu, 23 Oct 2014 19:17:49 +0000 (15:17 -0400)
committerDan Prince <dprince@redhat.com>
Sat, 20 Dec 2014 02:24:56 +0000 (21:24 -0500)
commit9df1991a80724f3179475cb9d561bfadb749822e
treed57a88ef94033f4e974afcb7925390d61f9003fd
parent741df33386b7fd78b0b95e6a9399dd53afc99f62
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
net-config-bond.yaml [new file with mode: 0644]
net-config-bridge.yaml [new file with mode: 0644]
net-config-noop.yaml [new file with mode: 0644]
overcloud-resource-registry.yaml