Go to file

Yuta Kazato 278ccb8bd0 Support Thresholds resource in PM Interface

This specification provides implementations of "Thresholds"
resource for supporting Performance Management interface
with external monitoring tools such as Prometheus.

Tacker Zed release has supported ETSI NFV-SOL
based Fault Management and Performance Management interfaces,
but Thresholds resource is not implemented.

The following items will be supported.
1. Add support Thresholds resource for PM interface.
2. Enhance notification to Client.
3. Add support of RESTful API for communications between
   Tacker and External Monitoring Tool.
4. Add new unit and functional tests.

Implements: blueprint support-auto-lcm
Change-Id: I7bc8af96e3e2a3290891f42821597184d5f77a25

2022-12-27 11:31:38 +09:00

doc

Add 2023.1 specs directory

2022-10-05 14:22:04 +00:00

specs

Support Thresholds resource in PM Interface

2022-12-27 11:31:38 +09:00

.gitignore

Remove testr

2021-06-30 23:53:16 +05:30

.gitreview

OpenDev Migration Patch

2019-04-19 19:35:23 +00: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

setup.cfg: Replace dashes with underscores

2021-05-18 13:16:39 +05:30

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

Update min version of tox

2021-05-10 16:51:07 +05:30

README.rst

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