[cid:image001.png@01D38FAC.4D03D500] Did You Know? OOM 'readiness' probes can be customized.
When deploying ONAP with OOM a Kubernetes readiness probe is used determine if it is safe to start the next container in the dependency chain. This 'readiness' probe is usually quite simple (ready.py<https://gerrit.onap.org/r/gitweb?p=oom.git;a=blob;f=kubernetes/readiness/docker/init/ready.py;h=c5b55eef187e02d57536180f0f14e459215ae896;hb=refs/heads/master>) but could be customized to better fit the needs of individual components. For example, if there is a dependency on a database being initialized the simple readiness probe is likely insufficient. However, a custom probe that checks for database content could be used to avoid the need for static timeouts. Custom readiness probes such as these could help ensure the component comes up every time and might also lessen the time to do so. If know where a custom readiness probe would be beneficial, please contact the OOM team. If you'd like to learn more about OOM, check out the OOM wiki<https://wiki.onap.org/display/DW/ONAP+Operations+Manager+Project> or concepts<https://kubernetes.io/docs/concepts/> to find out more about Kubernetes. Cheers, Roger Maitland [amdocs-a] 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 <https://www.amdocs.com/about/email-disclaimer>
_______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
