Update Spec: Add support for VNF packages
The node template name of type tosca.nodes.nfv.Vdu.Compute fulfills the purpose of the "SwImageDescId" attribute of the SwImageDesc information element in ETSI GS NFV-IFA 011  and hence it will be used in APIs to identify the software image id from the VNFD perspective. Please refer to clauses 22.214.171.124 and 126.96.36.199 of ETSI GS NFV-SOL 001 V2.6.1 . During processing of vnf package, we can read the software images and set software_image_id with the name of the node template name. For example: VDU1: type: tosca.nodes.nfv.Vdu.Compute properties: .. sw_image_data: name: Software of VDU1 version: '0.4.0' checksum: algorithm: sha-256 hash:
|1 month ago|
|doc||8 months ago|
|specs||1 month ago|
|.gitignore||5 years ago|
|.gitreview||6 months ago|
|.testr.conf||5 years ago|
|.zuul.yaml||1 year ago|
|LICENSE||5 years ago|
|README.rst||1 year ago|
|setup.cfg||10 months ago|
|setup.py||5 years ago|
|test-requirements.txt||1 year ago|
|tox.ini||1 year ago|
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:
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:
Launchpad blueprints for Tacker can be found at:
For more information about working with gerrit, see:
To validate that the specification is syntactically correct (i.e. get more confidence in the Jenkins result), please execute the following command:
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.