[cid:[email protected]]Did You Know? OOM uses both readiness and liveness probes to monitor ONAP components health
OOM makes use of kubernetes readiness and liveness probes feature. Note: The detailed description of the kubernetes feature can be found here: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/ Many OOM deployment entities are ready for serving incoming calls when the component process starts listening on its listen port. For instance, one of A&AI internal components is haproxy that routes traffic to other A&AI services (A&AI resources or A&AI traversal). When the haproxy starts listening on the ports specified in its configuration, it is ready to serve incoming requests. The haproxy port for servicing A&AI requests is 8443. This is why the A&AI haproxy deployment manifest includes: aai-deployment.yaml readinessProbe: tcpSocket: port: 8443 initialDelaySeconds: 5 periodSeconds: 10 With the above definition, 5 seconds after the container is started, Kubernetes will start the probes and only after a probe succeeds, kubernetes will start routing traffic to it. This is useful: ? - when starting the pod - container is assumed as fully running when it passed the readiness probe ? - when replacing (e.g. upgrading a pod) - the traffic will be routed to the old pod until the new pod becomes ready. Liveness probe helps to understand when the container is not useful anymore (e.g. fatal error happened) and must be replaced. The liveness probe have same parameters as the readiness probe. For instance, to make sure that the database container is up and running, SDNC component has following definition in its DB deployment manifest: db-statefulset.yaml livenessProbe: exec: command: ["mysqladmin", "ping"] initialDelaySeconds: 30 periodSeconds: 10 timeoutSeconds: 5 If you'd like to learn more about OOM, check out the OOM wiki<https://wiki.onap.org/display/DW/ONAP+Operations+Manager+Project>. Thanks, Yury Novitsky ONAP Operations Manager Team [cid:[email protected]] Amdocs a Platinum member of ONAP<https://www.amdocs.com/open-network/nfv-powered-by-onap> This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer>
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
