aboutsummaryrefslogtreecommitdiffstats
path: root/docs/onap-oom-heat.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/onap-oom-heat.rst')
-rw-r--r--docs/onap-oom-heat.rst8
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/onap-oom-heat.rst b/docs/onap-oom-heat.rst
index 8bccec796..288ef770b 100644
--- a/docs/onap-oom-heat.rst
+++ b/docs/onap-oom-heat.rst
@@ -1,4 +1,4 @@
-Integration Environement Installation
+Integration Environment Installation
-------------------------------------
ONAP is deployed on top of kubernetes through the OOM installer.
@@ -14,7 +14,7 @@ are provided, they correspond to files used on windriver environment.
This environment is used by the integration team to validate the installation,
perform tests and troubleshoot.
-If you intend to deploy your own environement, they can be used as reference but
+If you intend to deploy your own environment, they can be used as reference but
must be adapted according to your context.
Source files
@@ -22,7 +22,7 @@ Source files
- HEAT template files: https://git.onap.org/integration/tree/deployment/heat/onap-rke?h=elalto
- Sample OpenStack RC file: https://git.onap.org/integration/tree/deployment/heat/onap-rke/env/windriver/Integration-SB-00-openrc?h=elalto
-- Sample environment file: https://git.onap.org/integration/tree/deployment/heat/onap-rke/env/windriver/onap-oom.env?h=elatlo
+- Sample environment file: https://git.onap.org/integration/tree/deployment/heat/onap-rke/env/windriver/onap-oom.env?h=elalto
- Deployment script: https://git.onap.org/integration/tree/deployment/heat/onap-rke/scripts/deploy.sh?h=elalto
@@ -31,7 +31,7 @@ Heat Template Description
The ONAP Integration Project provides a sample HEAT template that
fully automates the deployment of ONAP using OOM as described in
-:ref:`ONAP Operations Manager (OOM) over Kubernetes<installing-onap>`.
+OOM documentation (https://docs.onap.org/en/elalto/guides/onap-developer/settingup/index.html#installing-onap).
The ONAP OOM HEAT template deploys the entire ONAP platform. It spins
up an HA-enabled Kubernetes cluster, and deploys ONAP using OOM onto