Initial implementation of ONAP scenarios

Patch introduces a new specific scenarios os-nosdn-onap-*ha
for automatic ONAP deployment on top of the OPNFV installation.
Deployment and configuration of ONAP is managed by OPNFV Auto project.

New scenarios are based on generic os-nosdn-nofeature-*ha scenarios.

Auto project is responsible for os-nosdn-onap-*ha development
and maintenance.

JIRA: AUTO-71

Change-Id: I8b177668d856f30b62d1d135b80a95c32ebb9937
Signed-off-by: Martin Klozik <martin.klozik@tieto.com>

1 files changed, 39 insertions, 0 deletions

diff --git a/mcp/config/scenario/os-nosdn-onap-noha.yaml b/mcp/config/scenario/os-nosdn-onap-noha.yaml
new file mode 100644
index 000000000..ae6255436
--- /dev/null
+++ b/mcp/config/scenario/os-nosdn-onap-noha.yaml
@@ -0,0 +1,39 @@
+##############################################################################
+# Copyright (c) 2017-2018 Mirantis Inc., Enea AB, Tieto 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
+##############################################################################
+# Scenario details:
+#   Specific scenario for ONAP deployment on top of OPNFV
+#   Scenario is based on generic os-nosdn-nofeature-noha scenario
+# Responsible: Auto project
+---
+cluster:
+  domain: mcp-ovs-noha.local
+  states:
+    - openstack_noha
+    - neutron_gateway
+    - networks
+    - onap
+virtual:
+  nodes:
+    control:
+      - ctl01
+      - gtw01
+    compute:
+      - cmp001
+      - cmp002
+  # Below values are only used for each node if said node is virtual
+  ctl01:
+    vcpus: 4
+    ram: 16384
+  gtw01:
+    ram: 2048
+  cmp001:
+    vcpus: 36
+    ram: 122880
+  cmp002:
+    vcpus: 36
+    ram: 122880