Provide a way to log a reason when a cinder service has been disabled
I'd like to be able to define a way to log a reason when I disable a service.
This is really usefull on large deployment when you need to deal with a lot of nodes and you need a way to track why a specific service has been disabled (for example, maintenance, hw failures, and so on).
The idea is to add a column (String 255) in the services table to store a reason field.
Then we will add a new API extension to disable a service indicating a reason for that.
Then we are going to change the cinder client to support the new feature.
This feature was already handled in nova and it is better that we can port it cinder to improve debug-ability: https:/
Blueprint information
- Status:
- Complete
- Approver:
- John Griffith
- Priority:
- Low
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- Guangya Liu (Jay Lau)
- Definition:
- Approved
- Series goal:
- Accepted for icehouse
- Implementation:
-
Implemented
- Milestone target:
-
2014.1
- Started by
- Guangya Liu (Jay Lau)
- Completed by
- Guangya Liu (Jay Lau)
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Add disabled_reason field to services table
Addressed by: https:/
Give a way to save why a service has been disabled
Addressed by: https:/
Adjust import order according to PEP8 imports rule
Work Items
Work items:
Add disabled_reason field to services table: DONE
Give a way to save why a service has been disabled: DONE
