Code Review / fuel.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 904183e) | patch
Initial implementation of ONAP scenarios 69/64369/51
authorMartin Klozik <martin.klozik@tieto.com>
Thu, 1 Nov 2018 08:49:45 +0000 (09:49 +0100)
committerMartin Klozik <martin.klozik@tieto.com>
Tue, 4 Dec 2018 10:24:34 +0000 (11:24 +0100)
commit76843c08fd03f41508c9bf86d927c2dca9a97db6
tree62ca6954442ba89d03d64bb552087fb2aeaa9635tree | snapshot
parent904183e275ca6b2aa6cad11a330fc060d5379b3ecommit | diff
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>
mcp/config/scenario/os-nosdn-onap-ha.yaml [new file with mode: 0644] blob
mcp/config/scenario/os-nosdn-onap-noha.yaml [new file with mode: 0644] blob
mcp/config/states/onap [new file with mode: 0755] blob