Bug 1041644

Summary: [RFE][cinder]: Provide a way to log a reason when a cinder service has been disabled
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: openstack-cinderAssignee: RHOS Maint <rhos-maint>
Status: CLOSED UPSTREAM QA Contact: Yogev Rabl <yrabl>
Severity: low Docs Contact:
Priority: medium    
Version: unspecifiedCC: eharney, markmc, scohen, yeylon
Target Milestone: Upstream M3Keywords: FutureFeature, Triaged
Target Release: 5.0 (RHEL 7)   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/cinder/+spec/record-reason-for-disabling-service
Whiteboard: upstream_milestone_icehouse-3 upstream_status_implemented upstream_definition_approved
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-03-20 16:20:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description RHOS Integration 2013-12-12 18:27:51 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/cinder/+spec/record-reason-for-disabling-service.

Description:

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

Specification URL (additional information):

None