We should deprecate the static_physical datasource in Rocky. In the
meantime, remove it from the 'types' list in the documentation.
Also removed nagios, which is still supported but was not tested for a
long time.
Change-Id: Ifa2d3f9b4af9be9ac02cc303acd6074f168a1462
Curly quotes usually input from Chinese input method.
When read from english context, it makes some confusion.
Change-Id: I653631f5eb0d2024d7457d576d7dfd9b38543d20
In order to better support validation and loading of different template
types, a mandatory 'type' property was added to the metadata section
(in version 2)
Change-Id: Iebd3eae2db14266a1cfc9cdd11ad9ee24ab9ff4c
also add guide of how to support processing snmp events
in alarm datasources
Change-Id: I74bb1f292938b42a70de5b22377d646e30802120
Implements: blueprint snmp-support
Signed-off-by: xupeipei <xu.peipei1@zte.com.cn>
Support functions in version 2 of Vitrage templates. The first supported
function is get_attr(entity, attr_name), and it can be used only in
execute_mistral action.
Change-Id: I89ad0c7b7efcd07f1b49fc5603b0854d7f6730e6
Implements: blueprint refactor-execute-mistral-definition
This change contains refactoring of the template validation and loading,
in order to allow different validators and loaders for execute_mistral
action in versions 1 and 2.
* template_versions.py contains all supported versions, including their
validators and loaders (and in the future - functions like get_attr())
* template_version_factory.py allows getting the right template version
instance
* validators and loaders are retrieved only from the template-version
instance, and are no longer created directly
* All content validators and loaders were moved under v1 and v2 packages
In addition, the structure of execute_mistral has changed, so now all
the input parameters of the workflow must reside under an 'input' section.
Change-Id: I8eebc79b0885eab9c013fafdc17ae8378c7bcedf
Added a new "version" field to the metadata section of Vitrage templates, in order to support future enhancements that are not backward-compatible. The default version is 1.
Version 2 will be added in anther change (with execute-mistral changes), together with a mechanism for running the correct validator and loader per-version.
Change-Id: I25a7bf50a2ab7277f5bbdc551bf676c62dfd6fdc
Implements: blueprint refactor-execute-mistral-definition
This commit attempts to move default policies from a policy.json
file into oslo.policy objects. This is an effort to make policy
easier to maintain for operators and is a community-wide goal for
the Queens release.
For more information on this initiative, please see:
https://governance.openstack.org/tc/goals/queens/policy-in-code.html
Co-authored-By: Hieu LE <hieulq@vn.fujitsu.com>
bp policy-and-docs-in-code
Change-Id: I8ce4fc45447b41930736d6fcf85e6d35cfbe9d56
This change contains the code without the tempest test. I will push the tempest test in a different change.
Implements: blueprint integration-with-mistral
Change-Id: Ie892482f1dede7487fbd690aff85febb17d17462
This change is to introduce a new rest api (v1/alarm/count) to
vitrage to provide counts of any alarms present in the system.
- It can optionally provide counts of alarms for all_tenants
similarly to the alarm api
- The rest api doc has been updated
- Unit test were added to test the api with and without
all_tenants as well as noauth
Change-Id: I6061b63c068580dcd25df5c624d9b3bd88f30cca
Implements: blueprint alarm-counts-api
Signed-off-by: Tyler Smith <tyler.smith@windriver.com>
- Added missing documentation of Nova notifier
- Moved osprofiler doc under contributor folder
- Marked the static-physical datasource as obsolete
- Removed a link to Aodh notifier (the document was deleted, as it was just a POC)
Depends-On: Ifcde995130486c859e6a9ce23e47a89910187732
Change-Id: Ib2b7880d65d4c6edd7cfd1f831da9da7af5e114c