cinder need support REST API cinder service-delete
Currently, use cinder service-list can list all cinder volume backend.
[root@2C5_10_DELL05 glance(
+------
| Binary | Host | Zone | Status | State | Updated_at | Disabled Reason |
+------
| cinder-scheduler | 2C5_10_DELL05 | nova | enabled | up | 2016-05-
| cinder-volume | 2C5-10_
| cinder-volume | 2C5-10_DELL01@lvm | nova | disabled | down | 2016-05-
| cinder-volume | 2C5_10_DELL05 | nova | enabled | down | 2016-05-
| cinder-volume | 2C5_10_
| cinder-volume | 2C5_10_
| cinder-volume | 2C5_10_
| cinder-volume | 2C5_10_
| cinder-volume | 2C5_10_DELL05@lvm | nova | enabled | up | 2016-05-
+------
If you are configured to remove a backend, but this service will remain in the database.
when the user run cinder service-list CLI command, he'll be able to see the service and
the service state is down. This will cause the user to trouble.
Therefore, we maybe need to provide a REST API that can delete the service that is not used.
Now, we only have a command "cinder-manage service remove" to delete the service, but users can not call through the REST API. So, I suggest we provide a REST API interface.
Blueprint information
- Status:
- Not started
- Approver:
- Sean McGinnis
- Priority:
- Low
- Drafter:
- YaoZheng_ZTE
- Direction:
- Needs approval
- Assignee:
- YaoZheng_ZTE
- Definition:
- Discussion
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
So it does seem like a useful feature, though it would need some safe-guards, like checking that this doesn't leave any unreachable volumes in the database - you can provide a --force option to delete them too if you like.
Please submit a spec with more detail so the community can review and comment.