Add followup to indicator management

Follows up change-Id I43c8dbf485bd54a3617c9193580279a7ffd65fd2

Change-Id: Ib97eed363e10e33edf7d5265a78d71ba1c373183
Story: 2005342
This commit is contained in:
Ilya Etingof 2019-05-24 18:11:46 +02:00
parent bb5d9ddb55
commit 7c1651a948
1 changed files with 7 additions and 4 deletions

View File

@ -68,7 +68,7 @@ Data model impact
None.
Due to the interactive nature of indicator information, it seem that
Due to the interactive nature of indicator information, it seems that
user-indicator link should be as immediate as possible, having it cached by
the database can make indicators confusing.
@ -251,9 +251,12 @@ The following commands will be created:
.. code-block:: bash
openstack baremetal indicator list [component]
openstack baremetal indicator show <component> indicator
openstack baremetal indicator set <component> <indicator> --state {ON,OFF,BLINKING}
openstack baremetal node indicator list <node> [component]
openstack baremetal node indicator show <node> <component> indicator
openstack baremetal node indicator set <node> <component> <indicator> --state {ON,OFF,BLINKING}
The first command lists all indicators for the specified component, or for all
components if specific component is not given.
RPC API impact
--------------