diff options
author | 2016-02-11 14:48:21 +0100 | |
---|---|---|
committer | 2016-02-18 06:46:45 +0100 | |
commit | 340ef7ca817317e17ebbc66973202d4134638614 (patch) | |
tree | 78d42650b769ead3f2dc2d8cd94059749d807ab3 /deploy/deploy_env.py | |
parent | ef0b33dcc34ee38d090487eabba122ae018980a0 (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>
Diffstat (limited to 'deploy/deploy_env.py')
0 files changed, 0 insertions, 0 deletions