summaryrefslogtreecommitdiffstats
path: root/docs/oom_user_guide.rst
diff options
context:
space:
mode:
authorRoger Maitland <Roger.Maitland@amdocs.com>2018-04-09 10:06:07 -0400
committerRoger Maitland <Roger.Maitland@amdocs.com>2018-04-09 10:06:07 -0400
commitd96413f48c8a5709a54bdb22a565035313ecef02 (patch)
tree1f3a4552c7761745ae8e4e46515d9bd4ee922b10 /docs/oom_user_guide.rst
parent6cfff80ec93d4a4fa3bdeb5289a70c4296560db1 (diff)
Fix User Guide: '-name' -> '--name'
Change-Id: Iba1597938fbaa9a9252b8bcec49b000118ce472f Signed-off-by: Roger Maitland <Roger.Maitland@amdocs.com> Issue-ID: OOM-822
Diffstat (limited to 'docs/oom_user_guide.rst')
-rw-r--r--docs/oom_user_guide.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/oom_user_guide.rst b/docs/oom_user_guide.rst
index 1b9a3eaef3..a71c4e3a13 100644
--- a/docs/oom_user_guide.rst
+++ b/docs/oom_user_guide.rst
@@ -147,13 +147,13 @@ In any case, setup of the Helm repository is a one time activity.
Once the repo is setup, installation of ONAP can be done with a single command::
- > helm install local/onap -name development
+ > helm install local/onap --name development
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 install local/onap --name development -f onap-development.yaml
To get a summary of the status of all of the pods (containers) running in your
deployment::
@@ -170,7 +170,7 @@ deployment::
was created for each of the ONAP components.
.. note::
- The Helm `-name` option refers to a release name and not a Kubernetes namespace.
+ The Helm `--name` option refers to a release name and not a Kubernetes namespace.
To install a specific version of a single ONAP component (`so` in this example)