summaryrefslogtreecommitdiffstats
path: root/docs/oom_user_guide.rst
diff options
context:
space:
mode:
authorMike Elliott <mike.elliott@amdocs.com>2018-11-07 15:47:19 -0500
committerMike Elliott <mike.elliott@amdocs.com>2018-11-28 19:15:59 -0500
commited5ff714fac29651318868a65267030e3c31c3ee (patch)
tree8ee15ba869ae4f628a5cdb14f9af25b6efc1f666 /docs/oom_user_guide.rst
parent3e0bad9194cc147028670510588fa5cde194e040 (diff)
Update OOM docs for Casablanca
Updating release notes, Helm and K8s versions and started documenting use of (un)deploy plugins. Change-Id: Ia51db5f1489e8d63fd7e1f10e80174eb9f182f0f Issue-ID: OOM-1497 Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
Diffstat (limited to 'docs/oom_user_guide.rst')
-rw-r--r--docs/oom_user_guide.rst16
1 files changed, 8 insertions, 8 deletions
diff --git a/docs/oom_user_guide.rst b/docs/oom_user_guide.rst
index db410a69aa..cac2710869 100644
--- a/docs/oom_user_guide.rst
+++ b/docs/oom_user_guide.rst
@@ -108,7 +108,7 @@ stable which should be removed to avoid confusion::
To prepare your system for an installation of ONAP, you'll need to::
- > git clone -b beijing http://gerrit.onap.org/r/oom
+ > git clone -b casablanca http://gerrit.onap.org/r/oom
> cd oom/kubernetes
@@ -282,7 +282,7 @@ value for the vnfDeployment/openstack/oam_network_cidr key as shown below.
To deploy ONAP with this environment file, enter::
- > helm install local/onap -n beijing -f environments/onap-production.yaml
+ > helm deploy local/onap -n casablanca -f environments/onap-production.yaml
.. include:: environments_onap_demo.yaml
:code: yaml
@@ -572,14 +572,14 @@ sequence of events described in the previous paragraph would be initiated.
For example, to upgrade a container by changing configuration, specifically an
environment value::
- > helm upgrade beijing onap/so --version 2.0.1 --set enableDebug=true
+ > helm deploy casablanca onap/so --version 2.0.1 --set enableDebug=true
Issuing this command will result in the appropriate container being stopped by
Kubernetes and replaced with a new container with the new environment value.
To upgrade a component to a new version with a new configuration file enter::
- > helm upgrade beijing onap/so --version 2.0.2 -f environments/demo.yaml
+ > helm deploy casablanca onap/so --version 2.0.2 -f environments/demo.yaml
To fetch release history enter::
@@ -672,18 +672,18 @@ from a running deployment the operator perform a 'dry-run' to display exactly
what will happen with a given command prior to actually deleting anything. For
example::
- > helm delete --dry-run beijing
+ > helm undeploy casablanca --dry-run
-will display the outcome of deleting the 'beijing' release from the deployment.
+will display the outcome of deleting the 'casablanca' release from the deployment.
To completely delete a release and remove it from the internal store enter::
- > helm delete --purge beijing
+ > helm undeploy casablanca --purge
One can also remove individual components from a deployment by changing the
ONAP configuration values. For example, to remove `so` from a running
deployment enter::
- > helm upgrade beijing osn/onap --set so.enabled=false
+ > helm undeploy casablanca-so --purge
will remove `so` as the configuration indicates it's no longer part of the
deployment. This might be useful if a one wanted to replace just `so` by