openstack/nova
Code Issues Proposed changes

api-ref: touch up the os-services docs

Browse Source 
Make it clear that the first GET /os-services response sample
is for 2.11 and make the version suffix format for the 2.69
example match the other response examples, i.e. "(v2.x)".

Also mention that PUT /os-services/{service_id} only allows
nova-compute services. Before Pike it was possible to update
non-nova-compute services though it didn't really make sense.

Change-Id: I585582710884a53d91f4453011d3407a94efe1e3
This commit is contained in:
Matt Riedemann 2019-07-24 13:52:36 -04:00
parent 9afaa5aa81
commit af2e5a5755
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
api-ref/source/os-services.inc
View File

@ -58,12 +58,12 @@ Response
- zone: OS-EXT-AZ:availability_zone
- forced_down: forced_down_2_11
**Example List Compute Services**
**Example List Compute Services (v2.11)**
.. literalinclude:: ../../doc/api_samples/os-services/v2.11/services-list-get-resp.json
:language: javascript
**Example List Compute Services (2.69)**
**Example List Compute Services (v2.69)**
This is a sample response for the services from the non-responsive part of the
deployment. The responses for the available service records will be normal
@ -272,7 +272,8 @@ Update Compute Service
Update a compute service to enable or disable scheduling, including recording a
reason why a compute service was disabled from scheduling. Set or unset the
``forced_down`` flag for the service.
``forced_down`` flag for the service. This operation is only allowed on
services whose ``binary`` is ``nova-compute``.
This API is available starting with microversion 2.53.