Bug 1041644 - [RFE][cinder]: Provide a way to log a reason when a cinder service has been disabled
Summary: [RFE][cinder]: Provide a way to log a reason when a cinder service has been d...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-cinder
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: Upstream M3
: 5.0 (RHEL 7)
Assignee: RHOS Maint
QA Contact: Yogev Rabl
URL: https://blueprints.launchpad.net/cind...
Whiteboard: upstream_milestone_icehouse-3 upstrea...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 18:27 UTC by RHOS Integration
Modified: 2016-04-26 19:42 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-03-20 16:20:30 UTC
Target Upstream Version:


Attachments (Terms of Use)

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


Note You need to log in before you can comment on or make changes to this bug.