Provide a way to log a reason when a cinder service has been disabled

Registered by Guangya Liu (Jay Lau) on 2013-11-01

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://blueprints.launchpad.net/nova/+spec/record-reason-for-disabling-service

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:
milestone icon 2014.1
Started by
Guangya Liu (Jay Lau) on 2013-12-08
Completed by
Guangya Liu (Jay Lau) on 2014-03-02

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/record-reason-for-disabling-service,n,z

Addressed by: https://review.openstack.org/60700
    Add disabled_reason field to services table

Addressed by: https://review.openstack.org/62216
    Give a way to save why a service has been disabled

Addressed by: https://review.openstack.org/62170
    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

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.