Tacker: ETSI MANO NFV Orchestrator / VNF Manager. See https://wiki.openstack.org/wiki/Tacker
f421f25d65
oslo.policy introduced the scope_type feature which can control the access level at system-level and project-level. - https://docs.openstack.org/oslo.policy/latest/user/usage.html#setting-scope As per the SRBAC design, OpenStack does not support system scope so we need to make scope type of each policy rule to project. - https://governance.openstack.org/tc/goals/selected/consistent-and-secure-rbac.html#phase-1 The policy with 'project' scope means user with 'project-scoped' token have permission to access which is nothing but the current case so no change in permission level. By adding the scope_type to project explicitly gives benefit of better error message. For example, if any user with system scope token try to access tacker APIs then oslo policy will fail early (instead of failing in lower layer at DB or VIM level) and give clear error message of invalid scope. This commit adds project scope in VNF LCM policies and its tests also. Partial implement blueprint implement-project-personas Change-Id: Iead7f82b8c22c0c67981f5a7ae3a86016ee64734 |
||
|---|---|---|
| api-ref/source | ||
| contrib/tacker-config | ||
| devstack | ||
| doc | ||
| etc | ||
| playbooks/devstack | ||
| releasenotes | ||
| roles | ||
| samples | ||
| tacker | ||
| tools | ||
| vagrant/devstack | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .mailmap | ||
| .pylintrc | ||
| .stestr.conf | ||
| .zuul.yaml | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| README.rst | ||
| TESTING.rst | ||
| bindep.txt | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
README.rst
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