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
Completed by
Ivan Berezovskiy

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/ceilometer-api-as-pacemaker-resource,n,z

Addressed by: https://review.openstack.org/143858
    Implementing ceilometer-api as pacemaker resource

Addressed by: https://review.openstack.org/147438
    Blueprint: ceilometer-api-as-pacemaker-resource

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.