openstack/tacker-specs
Code Issues Proposed changes
NFV Orchestration (Tacker) Specifications
142 Commits 1 Branch 0 Tags 21 MiB
Python 100%
8e0097cb79
Go to file
Toshiaki Takahashi 8e0097cb79 VNF Workflows Customization by Action Driver 
ETSI NFV doesn't define Lifecycle Management (LCM) workflow behaviors.
Currently, Tacker has a default LCM workflow, VNF vendors can't change
the default workflow. The default workflow doesn't satisfy some
VNF's LCM requirements.

We want to enable VNF vendor to customize their workflows
by Action Driver.

Change-Id: I49dce1bc2bfded9f69fdea1c1a48636af59d1f8b
Blueprint: action-driver
2020-08-24 17:32:32 +00:00
doc Merge "add Victoria specs directory" 2020-05-01 20:23:41 +00:00
specs VNF Workflows Customization by Action Driver 2020-08-24 17:32:32 +00:00
.gitignore Add base tacker-specs framework 2014-06-03 17:55:27 +09:00
.gitreview OpenDev Migration Patch 2019-04-19 19:35:23 +00:00
.testr.conf Add base tacker-specs framework 2014-06-03 17:55:27 +09:00
.zuul.yaml import zuul job settings from project-config 2018-08-17 20:15:37 +09:00
LICENSE Add base tacker-specs framework 2014-06-03 17:55:27 +09:00
README.rst Change tacker-specs webpage from oslosphinx to openstackdocstheme 2018-03-13 12:41:45 +09:00
setup.cfg Cleanup py27 support 2020-04-10 11:50:37 +02:00
setup.py Add base tacker-specs framework 2014-06-03 17:55:27 +09:00
test-requirements.txt Refactor and clean up specs dir 2018-04-05 15:21:56 +09:00
tox.ini Cleanup py27 support 2020-04-10 11:50:37 +02:00

README.rst

Team and repository tags

image

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/Blueprints

Launchpad blueprints for Tacker can be found at:

https://blueprints.launchpad.net/tacker

For more information about working with gerrit, see:

https://docs.openstack.org/infra/manual/developers.html#development-workflow

To validate that the specification is syntactically correct (i.e. get more confidence in the Jenkins result), please execute the following command:

$ tox

After 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.