9599ffe65d
Move existing content around based on the doc-migration specification. Replace :doc: markup with :ref: to have sphinx keep track of where the files move and generate valid hyperlinks. Add a few toctrees and index pages for the new directories. Depends-On: Ia750cb049c0f53a234ea70ce1f2bbbb7a2aa9454 Change-Id: I253ee8f89d3ec40e39310c18bb87ed1d3d5de330 Signed-off-by: Doug Hellmann <doug@doughellmann.com>
46 lines
850 B
ReStructuredText
46 lines
850 B
ReStructuredText
============
|
|
server event
|
|
============
|
|
|
|
Server event is the event record that had been done on a server, include: event
|
|
type(create, delete, reboot and so on), event result(success, error), start
|
|
time, finish time and so on. These are important information for server
|
|
maintains.
|
|
|
|
Compute v2
|
|
|
|
server event list
|
|
-----------------
|
|
|
|
List recent events of a server
|
|
|
|
.. program:: server event list
|
|
.. code:: bash
|
|
|
|
openstack server event list
|
|
<server>
|
|
|
|
.. describe:: <server>
|
|
|
|
Server to list events (name or ID)
|
|
|
|
server event show
|
|
-----------------
|
|
|
|
Show server event details
|
|
|
|
.. program:: server event show
|
|
.. code:: bash
|
|
|
|
openstack server event show
|
|
<server>
|
|
<request-id>
|
|
|
|
.. describe:: <server>
|
|
|
|
Server to show event details (name or ID)
|
|
|
|
.. describe:: <request-id>
|
|
|
|
Request ID of the event to show (ID only)
|