virtual: Add infra/init.yml for each scenario 21/48321/1
authorAlexandru Avadanii <Alexandru.Avadanii@enea.com>
Sat, 2 Dec 2017 23:39:05 +0000 (00:39 +0100)
committerAlexandru Avadanii <Alexandru.Avadanii@enea.com>
Mon, 4 Dec 2017 13:35:01 +0000 (14:35 +0100)
commit3a86be3361346a698f755f4ebdb9c1a55bea7094
tree27f4017a848a78f3d2e100bd7f3459d918bdd200
parentfda7372a1bffe11fc7a199ad3d4344c1b9e57e57
virtual: Add infra/init.yml for each scenario

Align our reclass model for virtual PODs with baremetal, by adding
an infra init file for each scenario, setting up cluster_name via
scenario infra init instead of scenario init.
While at it, reduce redundancy by defining cluster_domain based on
cluster_name via common infra init.

JIRA: FUEL-310

Change-Id: I5e89c883853fa66cb1c1fc69ce5766ee136ac477
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
mcp/reclass/classes/cluster/virtual-mcp-pike-common-noha/infra/init.yml
mcp/reclass/classes/cluster/virtual-mcp-pike-odl-noha/infra/init.yml [new file with mode: 0644]
mcp/reclass/classes/cluster/virtual-mcp-pike-odl-noha/init.yml
mcp/reclass/classes/cluster/virtual-mcp-pike-ovs-dpdk-noha/infra/init.yml [new file with mode: 0644]
mcp/reclass/classes/cluster/virtual-mcp-pike-ovs-dpdk-noha/init.yml
mcp/reclass/classes/cluster/virtual-mcp-pike-ovs-noha/infra/init.yml [new file with mode: 0644]
mcp/reclass/classes/cluster/virtual-mcp-pike-ovs-noha/init.yml