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>

1 files changed, 14 insertions, 0 deletions

diff --git a/mcp/reclass/classes/cluster/virtual-mcp-pike-ovs-dpdk-noha/infra/init.yml b/mcp/reclass/classes/cluster/virtual-mcp-pike-ovs-dpdk-noha/infra/init.yml
new file mode 100644
index 000000000..50676fc2c
--- /dev/null
+++ b/mcp/reclass/classes/cluster/virtual-mcp-pike-ovs-dpdk-noha/infra/init.yml
@@ -0,0 +1,14 @@
+##############################################################################
+# Copyright (c) 2017 Mirantis Inc., Enea AB and others.
+# All rights reserved. This program and the accompanying materials
+# are made available under the terms of the Apache License, Version 2.0
+# which accompanies this distribution, and is available at
+# http://www.apache.org/licenses/LICENSE-2.0
+##############################################################################
+---
+classes:
+  - cluster.virtual-mcp-pike-common-noha.infra
+
+parameters:
+  _param:
+    cluster_name: virtual-mcp-pike-ovs-dpdk-noha