summaryrefslogtreecommitdiffstats
path: root/mcp/reclass/classes/cluster/mcp-common-ha/infra/kvm_novcp.yml.j2
diff options
context:
space:
mode:
authorferenc Cserepkei <ferenc.cserepkei@ericsson.com>2016-02-11 14:48:21 +0100
committerJonas Bjurel <jonas.bjurel@ericsson.com>2016-02-18 13:35:01 +0000
commit39bb57e174481eb657d0465806a904e85e45722c (patch)
tree2101ee9e99eb28e7f637acef5c28584facd2792c /mcp/reclass/classes/cluster/mcp-common-ha/infra/kvm_novcp.yml.j2
parentb8549becb6ac0785af5d88c7bea5447981334499 (diff)
Adding Tacker service with POC orchestration to OPNFV cluster
The SFC subproject has been developed Tacker service orchestration for OPNFV+Apex. There was a hint that the same feature should exist in OPNFV/Fuel too. Since We had not enough time and resource the given implementation is proof-of-concept, a shell script based deployment + orchestration is given. The script designed being idempotent but lacks error handling. For Brahmaputra SR-1 a more reliable fuel-plugin implementation will be given. The script (poc.tacker-up.sh) is loosely integrated: the user should transfer it to the primary controller, where the OpenDayLight service is deoloyed and should execute the script manually. Note that adding Tacker service to OPNFV assumes that the cluster has fuel-plugin-ovs (with NSH support) and OpenDayLight SDN controller (fuel-plugin-opendaylight with GBP anf SFC fearures enabled) plugins enabled during deployment. Change-Id: Icb582c545e163816df14fa06411aa62d0c66cd5d Signed-off-by: ferenc Cserepkei <ferenc.cserepkei@ericsson.com> (cherry picked from commit 340ef7ca817317e17ebbc66973202d4134638614)
Diffstat (limited to 'mcp/reclass/classes/cluster/mcp-common-ha/infra/kvm_novcp.yml.j2')
0 files changed, 0 insertions, 0 deletions