Provide a way to log a reason when a 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 nova client to support the new feature.
Blueprint information
- Status:
- Complete
- Approver:
- Russell Bryant
- Priority:
- Low
- Drafter:
- Andrea Rosa
- Direction:
- Approved
- Assignee:
- Andrea Rosa
- Definition:
- Approved
- Series goal:
- Accepted for havana
- Implementation:
- Implemented
- Milestone target:
- 2013.2
- Started by
- Andrea Rosa
- Completed by
- Russell Bryant
Related branches
Related bugs
Sprints
Whiteboard
The idea is to add a new extensions, when this extension is loaded the behaviour of the os-services is going to change.
There will be a new PUT method for the existing os-services API extension:
PUT /v2/{tenant_
when this API is used to disable a service it's mandatory to specify a reason. That value will be saved in the table services.
If a service is already disabled and another call PUT /v2/{tenant_
When the new extension is loaded the GET /v2/{tenant_
Gerrit topic: https:/
Addressed by: https:/
Give a way to save why a service has been disabled.
Work Items
Work items:
[andrea-rosa-m] New field in services table: DONE
[andrea-rosa-m] Modify os-services API extensions: DONE
[andrea-rosa-m] Add nova client support for the new extension: DONE