From 7228e76c9a16e9aea8f125d79b3e50eb7e3a6505 Mon Sep 17 00:00:00 2001 From: Andreas Geissler Date: Thu, 17 Nov 2022 10:23:10 +0100 Subject: [OPERATION GUIDE] Remove outdated consul description Remove description for Consul usage from Operation Guide, as it is not maintained by OOM. In the future new ONAP Monitoring options will be provided Issue-ID: DOC-798 Signed-off-by: Andreas Geissler Change-Id: I51bae191f817a9aaaaf4e444e77056cf91f621d9 --- docs/guides/onap-operator/platformoperations.rst | 24 ------------------------ 1 file changed, 24 deletions(-) (limited to 'docs/guides/onap-operator/platformoperations.rst') diff --git a/docs/guides/onap-operator/platformoperations.rst b/docs/guides/onap-operator/platformoperations.rst index 666d0e835..8064383d0 100644 --- a/docs/guides/onap-operator/platformoperations.rst +++ b/docs/guides/onap-operator/platformoperations.rst @@ -40,30 +40,6 @@ functions :doc:`RobotFramework` -**Interface Health can be checked via Consul:** - - OOM provides two mechanisms to monitor the real-time health of an ONAP - deployment - - * a Consul GUI for a human operator or downstream monitoring systems - and Kubernetes liveness probes that enable automatic healing of - failed containers, and - * a set of liveness probes which feed into the Kubernetes manager - - Within ONAP, Consul is the monitoring system of choice and deployed - by OOM in two parts: - - * a three-way, centralized Consul server cluster is deployed as a - highly available monitor of all of the ONAP components, and a number - of Consul agents. - - The Consul server provides a user interface that allows a user to - graphically view the current health status of all of the ONAP components - for which agents have been created - - The Consul GUI can be accessed via http AT - - :30270/ui/ ONAP Backup and Restore ----------------------- -- cgit 1.2.3-korg