Build an interface class to allow services talking back to init.d scripts or systemd to provide status

Registered by Miguel Angel Ajo on 2014-06-02

I'm some situations it's necessary to provide extended service/daemon status to the service
manager. This would allow the service manager to take action in certain situations: an agent has
lost message broker connectivity, the child processes are dying or the system is starving for
resources, etc..

This feature is specially interesting when running services from pacemaker or equivalent
for high availability.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
Miguel Angel Ajo
Direction:
Needs approval
Assignee:
Miguel Angel Ajo
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/service-status-interface,n,z

Addressed by: https://review.openstack.org/97748
    Add service-status-interface spec

You should not set a milestone target unless the blueprint has been properly prioritized by the project drivers.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.