summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorBorislav Glozman <Borislav.Glozman@amdocs.com>2019-01-24 13:12:23 +0000
committerGerrit Code Review <gerrit@onap.org>2019-01-24 13:12:23 +0000
commit336c439ac769acba7a9e6531d7de577b9cec79b5 (patch)
treef604b401438bcfd8bcda2899daa2bfef01530fd5
parentbcf0459649e8ef50af4b747723941366ed174d2b (diff)
parent1d4b96fbc74243b089ac428e5ca03acde8a9ccf4 (diff)
Merge "docs: Replace Helm "install" using "deploy" plugin"
-rw-r--r--docs/oom_user_guide.rst12
1 files changed, 8 insertions, 4 deletions
diff --git a/docs/oom_user_guide.rst b/docs/oom_user_guide.rst
index ea658f0893..99a9a474d1 100644
--- a/docs/oom_user_guide.rst
+++ b/docs/oom_user_guide.rst
@@ -145,15 +145,19 @@ system, and looks for matches::
In any case, setup of the Helm repository is a one time activity.
+Next, install Helm Plugins required to deploy the ONAP Casablanca release::
+
+ > cp -R helm/plugins/ ~/.helm
+
Once the repo is setup, installation of ONAP can be done with a single command::
- > helm install local/onap --name development
+ > helm deploy development local/onap --namespace onap
This will install ONAP from a local repository in a 'development' Helm release.
As described below, to override the default configuration values provided by
OOM, an environment file can be provided on the command line as follows::
- > helm install local/onap --name development -f onap-development.yaml
+ > helm deploy development local/onap --namespace onap -f overrides.yaml
To get a summary of the status of all of the pods (containers) running in your
deployment::
@@ -174,9 +178,9 @@ deployment::
To install a specific version of a single ONAP component (`so` in this example)
-with the given name enter::
+with the given release name enter::
- > helm install onap/so --version 2.0.1 -n so
+ > helm deploy so onap/so --version 3.0.1
To display details of a specific resource or group of resources type::