2f959940bc
This specification describes implements of fine-grained access control based on user and VNF information for API resources. It will extend user information to include role, VIM information, VNF instance information, and implement the policy enforcer that uses not only roles, but also user and VNF information. The following items will be supported. 1. Add additional attributes to resources when be created. 2. Change the API process to support Tacker policy checker. 3. Add the Tacker policy filter to the list API processes. 4. Convert special roles to API attributes in context. 5. Add a configuration option and policy samples. Implements: blueprint enhance-api-policy Change-Id: Ib8f1c83be1bec3644f0fbead46ccd6ab7c2d4e83
Team and repository tags
OpenStack Tacker Specifications
This git repository is used to hold approved design specifications for additions to the Tacker project. Reviews of the specs are done in gerrit, using a similar workflow to how we review and merge changes to the code itself.
The layout of this repository is:
specs/<release>/You can find an example spec in specs/template.rst.
Specifications are proposed for a given release by adding them to the specs/<release> directory and posting it for review. The implementation status of a blueprint for a given release can be found by looking at the blueprint in launchpad. Not all approved blueprints will get fully implemented.
Specifications have to be re-proposed for every release. The review may be quick, but even if something was previously approved, it should be re-reviewed to make sure it still makes sense as written.
Please note, Launchpad blueprints are still used for tracking the current status of blueprints. For more information, see:
https://wiki.openstack.org/wiki/BlueprintsLaunchpad blueprints for Tacker can be found at:
For more information about working with gerrit, see:
https://docs.openstack.org/infra/manual/developers.html#development-workflowTo validate that the specification is syntactically correct (i.e. get more confidence in the Jenkins result), please execute the following command:
$ toxAfter running tox, the documentation will be available
for viewing in HTML format in the doc/build/ directory.
Please do not checkin the generated HTML files as a part of your
commit.