Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1056874 - [RFE][ceilometer]: per domain/project/user quotas on alarms
Summary: [RFE][ceilometer]: per domain/project/user quotas on alarms
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/ceil...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-23 05:04 UTC by RHOS Integration
Modified: 2015-03-19 17:25 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-19 17:25:59 UTC


Attachments (Terms of Use)

Description RHOS Integration 2014-01-23 05:04:16 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/ceilometer/+spec/quotas-on-alarms.

Description:

Currently it is possible to create an unlimited number of alarms in ceilometer. It would be useful to be able to specify a maximum number of alarms allowed per user, project or domain in order to have some control and restraint on the computing power required by ceilometer.

These limits, if enforced, could be specified in ceilometer's configuration file. These limits would be expressed as the maximum number of alarms that can be set for a given user, project and domain. No value in the conf file would mean no limit.

When a user adds an alarm, the following checks would occur:

1. Has the user filled his alarms quota ? If yes, the query is rejected.
2. Is the user's project's alarms quota filled ? If yes, the query is rejected.
3. Is the user's domain's alarms quota filled ? If yes, the query is rejected.
4. Add the alarm.

Quotas don't have to be set at every level. For example, setting a limit only at the project level will allow users to create as many alarms as they want as long as the sum of alarms for their specific tenant is less than the limit.

Specification URL (additional information):

None


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