c3444e384d
Configure tox+content to fetch event and convert alarms and logs
to rst for use in build.
Handle non-existant tmp dir in zuul builds
Add static events.yaml for CI/CD testingx
Generalize label construction to prevent namespace conflicts
Consume events directly from fm repo (required changes merged)
Update logs template for legibility.
Add clean up for temporary rst files.
Point parser at dynamically downloaded events file
Restore logs template
Note: This review deletes static alarm and log files
Note: This review excludes alarm files from git as they are now
build-time temp files.
Note: This review uses a static copy of events.yaml to pass tox
until the dep. below is met. It will need reconfiguration
at that time.
Depends-On: https://review.opendev.org/c/starlingx/fault/+/863574
Signed-off-by: Ron Stone <ronald.stone@windriver.com>
Change-Id: I0bb8d0a77b9d3cf22b33f8930c569b3e70b7291c
19 lines
610 B
ReStructuredText
19 lines
610 B
ReStructuredText
The system inventory and maintenance service reports system changes with
|
|
different degrees of severity. Use the reported alarms to monitor the overall
|
|
health of the system.
|
|
|
|
Alarm messages are numerically coded by the type of alarm.
|
|
|
|
A management-affecting alarm is one that cannot be ignored at the indicated
|
|
severity level or higher by using relaxed alarm rules during an orchestrated
|
|
patch or upgrade operation.
|
|
|
|
For more information, see :ref:`fault-management-overview`.
|
|
|
|
.. note::
|
|
|
|
**Degrade Affecting Severity**: Critical indicates a node will be degraded if
|
|
the alarm reaches a critical level.
|
|
|
|
|