62f6a0a1bc
This patch adds a new external event called "power-update" through which ironic will convey all (power_off and power_on) power state changes (running -> shutdown or shutdown -> running will be the only ones handled by nova and the rest will be ignored) on a physical instance to nova. The database will be updated accordingly to reflect the real vm_state and power_state of the instance. This way nova will not be able to enforce an incorrect power state on the physical instance during the periodic "sync_power_states" task. Implements blueprint nova-support-instance-power-update Story: 2004969 Task: 29423 Change-Id: I2b292050cc3ce5ef625659f5a1fe56bb76072496
74 lines
2.0 KiB
ReStructuredText
74 lines
2.0 KiB
ReStructuredText
.. -*- rst -*-
|
|
|
|
====================================================
|
|
Create external events (os-server-external-events)
|
|
====================================================
|
|
|
|
.. warning::
|
|
This is an ``admin`` level service API only designed to be used by
|
|
other OpenStack services. The point of this API is to coordinate
|
|
between Nova and Neutron, Nova and Cinder, Nova and Ironic (and potentially
|
|
future services) on activities they both need to be involved in,
|
|
such as network hotplugging.
|
|
|
|
Unless you are writing Neutron, Cinder or Ironic code you **should not**
|
|
be using this API.
|
|
|
|
Creates one or more external events. The API dispatches each event to a
|
|
server instance.
|
|
|
|
Run Events
|
|
==========
|
|
|
|
.. rest_method:: POST /os-server-external-events
|
|
|
|
Creates one or more external events, which the API dispatches to the
|
|
host a server is assigned to. If the server is not currently assigned
|
|
to a host the event will not be delivered.
|
|
|
|
You will receive back the list of events that you submitted, with an
|
|
updated ``code`` and ``status`` indicating their level of success.
|
|
|
|
Normal response codes: 200, 207
|
|
|
|
A 200 will be returned if all events succeeded, 207 will be returned
|
|
if some events could not be processed. The ``code`` attribute for the
|
|
event will explain further what went wrong.
|
|
|
|
Error response codes: badRequest(400), unauthorized(401), forbidden(403),
|
|
itemNotFound(404)
|
|
|
|
Request
|
|
-------
|
|
|
|
.. rest_parameters:: parameters.yaml
|
|
|
|
|
|
- events: events
|
|
- name: event_name
|
|
- server_uuid: server_uuid
|
|
- status: event_status
|
|
- tag: event_tag
|
|
|
|
**Example Run Events**
|
|
|
|
.. literalinclude:: ../../doc/api_samples/os-server-external-events/event-create-req.json
|
|
:language: javascript
|
|
|
|
Response
|
|
--------
|
|
|
|
.. rest_parameters:: parameters.yaml
|
|
|
|
- events: events
|
|
- code: code
|
|
- name: event_name
|
|
- server_uuid: server_uuid
|
|
- status: event_status
|
|
- tag: event_tag
|
|
|
|
**Example Run Events**
|
|
|
|
.. literalinclude:: ../../doc/api_samples/os-server-external-events/event-create-resp.json
|
|
:language: javascript
|