openstack
/
ironic-specs
Code Issues Proposed changes

Update CRUD and node states notification spec 

Add new "console_restore" action for node console notifications.
This action will be used when console for node is already enabled
in the DB but restart via driver is required due to dead or
restarted conductor process.

Change-Id: I80eddf508f61646f84d0e74fe3578b8d26cde151
Partial-Bug: #1606520
This commit is contained in:
Yuriy Zveryanskyy 2016-11-15 17:08:42 +02:00
parent 114471d95b
commit 27d9e8fd88
1 changed files with 14 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
specs/approved/crud-and-state-notifications.rst
View File

@ -163,11 +163,21 @@ The following event types will be added:
* "baremetal.node.console_set.end";
* "baremetal.node.console_set.error".
* "baremetal.node.console_set.error";
Priority level - INFO or ERROR (for "error" status). Payload contains all
fields from base ``NodePayload``. All these notifications will be implemented
in the ironic-conductor, because setting of a node's console is an asynchronous
* "baremetal.node.console_restore.start";
* "baremetal.node.console_restore.end";
* "baremetal.node.console_restore.error".
``console_set`` action is used when start or stop console is initiated via API
request, ``console_restore`` action is used when ``console_enabled`` flag is
already enabled in the DB for node and console restart via driver is required
(due to dead or restarted ironic-conductor process). Priority level - INFO or
ERROR (for "error" status). Payload contains all fields from base
``NodePayload``. All these notifications will be implemented in the
ironic-conductor, because setting of a node's console is an asynchronous
request, so ironic-conductor can easily emit notifications for the start/end of
the change.