consistent implementation of liveness and readiness probes accross all openstack helm charts

Registered by Matthias Omisore on 2018-07-12

Although openstack helm supports the implementation of liveness and readiness probes. There is currently no coherent way of implementing them. This proposes a blueprint for determining the kind of probe (tcpSocket, httpGet or command) to implement based on the service/container being probed, whether its a local Service, API or Port. . The probes fields (periodSeconds, InitialDelaySeconds, timeoutSeconds, successThreshold and failureThreshold) should also be configured taking into consideration container bootup time and its general responsiveness.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
Matthias Omisore
Direction:
Needs approval
Assignee:
Matthias Omisore
Definition:
Discussion
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

patches:
https://review.openstack.org/#/c/580448/ - Readiness Probe for glance, horizon, keystone and rabbitmq
https://review.openstack.org/#/c/577293/n - cinder readiness check

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.