manila/api-ref/source/scheduler-stats.inc
Goutham Pacha Ravi de29398128 [doc] remove project_id from api endpoints
As of API version 2.60, a project_id is no
longer needed in the API URLs.

Fix the docs to indicate that.

Also fix up a few quota parameters that use
project_id in a different place in the API path.

Change-Id: I24b32c8521805a7d67d512d36d644c0f07c532ea
Implements: bp remove-project-id-from-urls
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
2021-02-09 21:59:07 -08:00

124 lines
3.0 KiB
ReStructuredText

.. -*- rst -*-
===============================
Scheduler Stats - Storage Pools
===============================
An administrator can list all back-end storage pools that are known
to the scheduler service.
List back-end storage pools
===========================
.. rest_method:: GET /v2/scheduler-stats/pools?pool={pool_name}&host={host_name}&backend={backend_name}&capabilities={capabilities}&share_type={share_type}
Lists all back-end storage pools. If search options are provided, the pool
list that is returned is filtered with these options.
Response codes
--------------
.. rest_status_code:: success status.yaml
- 200
.. rest_status_code:: error status.yaml
- 400
- 401
- 403
Request
-------
.. rest_parameters:: parameters.yaml
- project_id: project_id_path
- pool_name: backend_pool_query
- host_name: backend_host_query
- backend_name: backend_query
- capabilities: backend_capabilities_query
- share_type: share_type_query
Response parameters
-------------------
.. rest_parameters:: parameters.yaml
- backend: backend
- host: backend_host
- pool: pool
- name: backend_name
Response example
----------------
.. literalinclude:: samples/pools-list-response.json
:language: javascript
List back-end storage pools with details
========================================
.. rest_method:: GET /v2/scheduler-stats/pools/detail?pool={pool_name}&host={host_name}&backend={backend_name}&capabilities={capabilities}&share_type={share_type}
Lists all back-end storage pools with details. If search options are provided,
the pool list that is returned is filtered with these options.
Response codes
--------------
.. rest_status_code:: success status.yaml
- 200
.. rest_status_code:: error status.yaml
- 400
- 401
- 403
Request
-------
.. rest_parameters:: parameters.yaml
- project_id: project_id_path
- pool_name: backend_pool_query
- host_name: backend_host_query
- backend_name: backend_query
- capabilities: backend_capabilities_query
- share_type: share_type_query
Response parameters
-------------------
.. rest_parameters:: parameters.yaml
- pools: pools
- name: backend_name
- backend: backend
- pool: pool
- host: backend_host
- capabilities: capabilities
- qos: capability_qos
- timestamp: timestamp
- share_backend_name: capability_share_backend_name
- server_pools_mapping: capability_server_pools_mapping
- driver_handles_share_servers: capability_driver_handles_share_servers
- driver_version: capability_driver_version
- total_capacity_gb: capability_total_capacity_gb
- free_capacity_gb: capability_free_capacity_gb
- reserved_percentage: capability_reserved_percentage
- vendor_name: capability_vendor_name
- snapshot_support: capability_snapshot_support
- replication_domain: capability_replication_domain
- storage_protocol: capability_storage_protocol
Response example
----------------
.. literalinclude:: samples/pools-list-detailed-response.json
:language: javascript