Tacker: ETSI MANO NFV Orchestrator / VNF Manager. See https://wiki.openstack.org/wiki/Tacker
9e13a55aba
In NFV-SOL003 V2.6.1, the add_resources'id in grant should be same as the vnfc_resource_info'id. However, at present, if you execute heal_grant and scale_grant request, the add_resources's resource_definition_id in grantResponse cannot match the vnfc_resource_info.id. In _scale_grant, to fix this bug, we changed the processing of _scale_grant in openstack._get_grant_resource_scale_out method. Firstly initialize the data of vnfc_resource_info according to the input parameters and the vnfd file, then initialize the add_resources data of grant according to the vnfc_resource_info data. After scaling out, store the data in the stack into vnfc_resource_info in the openstack.scale_resource_update method. In addition, in openstack._get_grant_resource_scale_out, there is also a problem with the placement_constraint rule setting, which is also corrected in this patch. In _heal_grant, if heal entire vnf_instance, we initialize remove_resources used old vnf_instance's info, and then reinitialize vnf_instance's info and use them to initialize add_resources. If heal partial vnf_instance, we just use update_resources in grant. For instantiate, if you need to use the data obtained by instantiate_grant in instantiate_end, the process should execute the post_instantiate_vnf method before instantiate_end, so the vnflcm_driver._instantiate_vnf method has also been modified. Closes-Bug: #1930782 Change-Id: I1008472f5a7104324b61a413052dc44bc84c7ade |
||
---|---|---|
api-ref/source | ||
contrib/tacker-config | ||
devstack | ||
doc | ||
etc | ||
playbooks/devstack | ||
releasenotes | ||
roles | ||
samples | ||
tacker | ||
tools | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.pylintrc | ||
.stestr.conf | ||
.zuul.yaml | ||
bindep.txt | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
lower-constraints.txt | ||
README.rst | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
TESTING.rst | ||
tox.ini |
Tacker
Welcome!
Tacker is an OpenStack based NFV Orchestrator service with built-in general purpose VNF Manager to deploy and operate Virtual Network Functions (VNFs) on an OpenStack based NFV Platform. It is based on ETSI MANO Architectural Framework and provides a fully functional stack to orchestrate VNFs end-to-end.
Installation:
Installation instructions and user guides can be found at: https://docs.openstack.org/tacker/
Tacker code base supports OpenStack master and other releases. Please follow the instructions in the above address for a successful installation of corresponding release.
Code:
Tacker code is available in following repositories:
- Tacker server: https://opendev.org/openstack/tacker
- Tacker Python client: https://opendev.org/openstack/python-tackerclient
- Tacker Horizon UI: https://opendev.org/openstack/tacker-horizon
Bugs:
Please report bugs at: https://bugs.launchpad.net/tacker
External Resources:
- Tacker Wiki: https://wiki.openstack.org/wiki/Tacker
- Tacker Blueprints: https://blueprints.launchpad.net/tacker
- For help on usage and hacking of Tacker, please send an email to OpenStack-dev Mailing List <mailto:openstack-discuss@lists.openstack.org> with [openstack-dev] [Tacker] tag.
- To get release notes: Tacker Release Notes