Creating an "Operations and Administration Guides" section and restructuring chapters

Issue-ID: DOC-543

Signed-off-by: andreasgeissler <andreas-geissler@telekom.de>
Change-Id: Ia06c13cdf4299078c0fa5b133d50fe3d83c0cf59

1 files changed, 94 insertions, 0 deletions

diff --git a/docs/guides/onap-operator/platformoperations.rst b/docs/guides/onap-operator/platformoperations.rst
new file mode 100644
index 000000000..edde9aed8
--- /dev/null
+++ b/docs/guides/onap-operator/platformoperations.rst
@@ -0,0 +1,94 @@
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+.. Copyright 2017 AT&T Intellectual Property.  All rights reserved.
+
+
+Platform Operations
+===================
+
+.. toctree::
+   :maxdepth: 1
+   :titlesonly:
+
+ONAP Operations
+---------------
+
+Configuring, scaling and upgrading ONAP is supported by OOM and can
+be found in:
+
+.. toctree::
+   :maxdepth: 2
+   :titlesonly:
+
+   ../../submodules/oom.git/docs/oom_user_guide.rst
+
+ONAP Testing and Monitoring
+---------------------------
+
+Monitoring of ONAP depends on the deployment scenario.
+Generally the infrastructure monitoring (Openstack, K8S) depends on the
+platform ONAP is installed on.
+
+Additionally ONAP supports the following additional tools to monitor ONAP
+functions
+
+**Basic Healthcheck of ONAP is supported by:**
+
+.. toctree::
+   :maxdepth: 2
+   :titlesonly:
+
+   RobotFramework <../../submodules/integration.git/docs/docs_robot.rst>
+
+**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://<kubernetes IP>:30270/ui/
+
+**ONAP Log collection is provided by the Logging and Analytics Module:**
+
+.. toctree::
+   :maxdepth: 2
+   :titlesonly:
+
+   Logging&Analytics <../../submodules/logging-analytics.git/docs/index.rst>
+
+ONAP Backup and Restore
+-----------------------
+
+To Backup ONAP a solution is described in Wiki (Migration to RTD->TBD):
+
+`Backup and Restore Solution <https://wiki.onap.org/display/DW/Backup+and+Restore+Solution%3A+ONAP-OOM>`_
+
+ONAP Multisite Deployment
+-------------------------
+
+ONAP Multisite deployment, coordination and management is supported by
+the MUSIC component:
+
+.. toctree::
+   :maxdepth: 2
+   :titlesonly:
+
+   Multi-Site State Coordination <../../submodules/music.git/docs/index.rst>
+