0dc8390e11
Currently, Cinder couldn't report backend state to service, operators only know that cinder-volume process is up, but isn't aware of if the backend storage device is ok. Users still can create volume and go to fail over and over again. This bp propose to get the backend state from driver directly, operators or management system could query this via service list. This function will improve the maintenance ability for Cinder. Change-Id: I561dca3ef7c1901401621bc112389dbd178a907e Implements: blueprint report-backend-state-in-service-list
21 lines
810 B
ReStructuredText
21 lines
810 B
ReStructuredText
====================================
|
|
Report backend state in service list
|
|
====================================
|
|
|
|
Currently, Cinder couldn't report backend state to service, operators only
|
|
know that cinder-volume process is up, but isn't aware of whether the backend
|
|
storage device is ok. Users still can create volume and go to fail over and
|
|
over again. To make maintenance easier, operator could query storage device
|
|
state via service list and fix the problem more quickly. If device state is
|
|
*down*, that means volume creation will fail.
|
|
|
|
To do so, use the Block Storage API: service list to get the backend state.
|
|
Run this command:
|
|
|
|
.. code-block:: console
|
|
|
|
$ openstack volume service list
|
|
|
|
Add backend_state: up/down into response body of service list. This feature
|
|
is supported after microversion 3.49.
|