Provide a way to record why a service has been disabled
Registered by
Phil Day
On a large scale deployment there may be many different reasosn for disabling a service (some specific h/w problem, reserved for specific use, etc) - all of which are normally tracks in some form of incident system. Currently there is no way to link the status of an individual service in Nova with such a system, which makes operating the system difficult.
This change will add a short reason field to the service table so that a reason can be supplied when disabling a service.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Vish Ishaya
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Give a way to save why a service has been disabled.
(?)
