summaryrefslogtreecommitdiff
path: root/api-ref/source/v1/services.inc
blob: 67b344cd5bdf54e23da614f0282a6b0221326601 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
.. -*- rst -*-

==============
Manage service
==============

Show orchestration engine status
================================

.. rest_method::  GET /v1/{tenant_id}/services

Enables administrative users to view details for all orchestration engines.

Orchestration engine details include engine id, binary, topic name, host, 
report interval, last updated time, health status, and host name.

Response Codes
--------------

.. rest_status_code:: success status.yaml

   - 200

.. rest_status_code:: error status.yaml

   - 403
   - 503

Troubleshooting

- A ``503`` error code indicates that the heat engines are not operational.
  Run the ``heat-manage service list`` command or contact your cloud provider
  to determine why the heat engines are not operational.

Request Parameters
------------------

.. rest_parameters:: parameters.yaml

   - tenant_id: tenant_id

Response Parameters
-------------------

.. rest_parameters:: parameters.yaml

   - X-Openstack-Request-Id: request_id
   - services: services
   - binary: binary
   - created_at: created_at
   - deleted_at: deleted_at
   - engine_id: engine_id
   - host: host
   - hostname: hostname
   - id: engine_record_id
   - report_interval: report_interval
   - status: engine_status
   - topic: topic
   - updated_at: updated_at

Response Example
----------------

.. literalinclude:: samples/services-list-response.json
   :language: javascript