ceilometer-api as pacemaker resource
Registered by
Ivan Berezovskiy
Currently we are having three ceilometer api services running in ha mode (one per controller). All of them are working simultaneously. Load even of one ceilometer-api service is really small because it can process a lot of requests that can be becoming only from admin users. That's why we need to run ceilometer-api services as a corosync resoruce (one per cluster).
Blueprint information
- Status:
- Complete
- Approver:
- Fuel Library (Deprecated)
- Priority:
- Undefined
- Drafter:
- Ivan Berezovskiy
- Direction:
- Needs approval
- Assignee:
- Ivan Berezovskiy
- Definition:
- Obsolete
- Series goal:
- Accepted for 6.1.x
- Implementation:
- Deferred
- Milestone target:
- None
- Started by
- Completed by
- Ivan Berezovskiy
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Implementing ceilometer-api as pacemaker resource
Addressed by: https:/
Blueprint: ceilometer-
(?)