Merge "[AAI] Make aai log level configurable"

[oom.git] / docs / sections / oom_project_description.rst

diff --git a/docs/sections/oom_project_description.rst b/docs/sections/oom_project_description.rst
index 404a410..7742379 100644 (file)
--- a/docs/sections/oom_project_description.rst
+++ b/docs/sections/oom_project_description.rst
@@ -11,7 +11,7 @@ ONAP Operations Manager Project
 
 .. warning::
 
-    THIS PAGE PROB NEEDS A REWRITE ALSO
+    THIS PAGE PROB NEEDS A REWRITE AS IT IS OUTDATED
 
 The ONAP Operations Manager (OOM) is responsible for life-cycle management of
 the ONAP platform itself; components such as SO, SDNC, etc. It is not
@@ -38,21 +38,19 @@ In summary OOM provides the following capabilities:
   service impact
 - **Delete** - cleanup individual containers or entire deployments
 
-OOM supports a wide variety of Kubernetes private clouds - built with Rancher,
-Kubeadm or Cloudify - and public cloud infrastructures such as: Microsoft
+OOM supports a wide variety of Kubernetes private clouds - built with ClusterAPI,
+Kubespray - and public cloud infrastructures such as: Microsoft
 Azure, Amazon AWS, Google GCD, VMware VIO, and OpenStack.
 
 The OOM documentation is broken into four different areas each targeted at a
 different user:
 
 - :ref:`oom_dev_guide` - a guide for developers of OOM
-- :ref:`oom_infra_setup_guide` - a guide for those setting up the environments that OOM will use
+- :ref:`oom_infra_guide` - a guide for those setting up the environments that OOM will use
 - :ref:`oom_deploy_guide` - a guide for those deploying OOM on an existing cloud
 - :ref:`oom_user_guide` - a guide for operators of an OOM instance
 - :ref:`oom_access_info_guide` - a guide for operators who require access to OOM applications
 
-
-
 The :ref:`release_notes` for OOM describe the incremental features per release.
 
 Component Orchestration Overview