8f4e803634
This completes the verification for the diagnostics API. As the
response is still dumping out raw hypervisor stats (for compatibility
7529b94f4a/nova/api/openstack/compute/server_diagnostics.py (L38-L44))
the best we can say about the response is it's hypervisor specific and
don't use it.
In future we should use the standardized format that was defined
during the v3 effort.
Part of bp:api-ref-in-rst
Change-Id: Id2cca6a2f79542bec17a34aa3d31924e8ed7b9e5
45 lines
1.1 KiB
ReStructuredText
45 lines
1.1 KiB
ReStructuredText
.. -*- rst -*-
|
|
|
|
============================================
|
|
Servers diagnostics (servers, diagnostics)
|
|
============================================
|
|
|
|
Shows the usage data for a server.
|
|
|
|
Show Server Diagnostics
|
|
=======================
|
|
|
|
.. rest_method:: GET /v2.1/{tenant_id}/servers/{server_id}/diagnostics
|
|
|
|
Shows basic usage data for a server.
|
|
|
|
Policy defaults enable only users with the administrative role. Cloud
|
|
providers can change these permissions through the ``policy.json``
|
|
file.
|
|
|
|
Normal response codes: 200
|
|
|
|
Error response codes: unauthorized(401), forbidden(403), notfound(404), conflict(409), notimplemented(501)
|
|
|
|
Request
|
|
-------
|
|
|
|
.. rest_parameters:: parameters.yaml
|
|
|
|
- tenant_id: tenant_id
|
|
- server_id: server_id
|
|
|
|
Response
|
|
--------
|
|
|
|
The response format for diagnostics is backend hypervisor specific,
|
|
and not well defined. This should be considered a debug interface
|
|
only, and not relied upon by programmatic tools.
|
|
|
|
**Example Server diagnostics**
|
|
|
|
Below is an example of diagnostics for a libvirt based server instance.
|
|
|
|
.. literalinclude:: ../../doc/api_samples/os-server-diagnostics/server-diagnostics-get-resp.json
|
|
:language: javascript
|