X-Git-Url: https://gerrit.onap.org/r/gitweb?a=blobdiff_plain;f=docs%2Foom_quickstart_guide.rst;h=9672a0e55f20f4664a666a7266fe2a02782df124;hb=8476bbe028eaad92b8bde62347fe2eb275c8850a;hp=655736f0fa96b6e7ef55c47d73cc3f1bf7a9dd36;hpb=114736eb5119b023bc5f166a3b42aaf933b0b223;p=oom.git

diff --git a/docs/oom_quickstart_guide.rst b/docs/oom_quickstart_guide.rst
index 655736f0fa..9672a0e55f 100644
--- a/docs/oom_quickstart_guide.rst
+++ b/docs/oom_quickstart_guide.rst
@@ -16,8 +16,8 @@ available), follow the following instructions to deploy ONAP.
 
 **Step 1.** Clone the OOM repository from ONAP gerrit::
 
-  > git clone http://gerrit.onap.org/r/oom
-  > cd kubernetes
+  > git clone -b beijing http://gerrit.onap.org/r/oom
+  > cd oom/kubernetes
 
 
 **Step 2.** Customize the onap/values.yaml file to suit your deployment. You
@@ -61,41 +61,41 @@ may want to selectively enable or disable ONAP components by changing the
   # to customize the ONAP deployment.
   #################################################################
   aaf:
-    enabled: false
+    enabled: true
   aai:
-    enabled: false
+    enabled: true
   appc:
-    enabled: false
+    enabled: true
   clamp:
-    enabled: false
+    enabled: true
   cli:
-    enabled: false
+    enabled: true
   consul: # Consul Health Check Monitoring
-    enabled: false
+    enabled: true
   dcaegen2:
-    enabled: false
+    enabled: true
   esr:
-    enabled: false
+    enabled: true
   log:
-    enabled: false
+    enabled: true
   message-router:
-    enabled: false
+    enabled: true
   mock:
-    enabled: false
+    enabled: true
   msb:
-    enabled: false
+    enabled: true
   multicloud:
-    enabled: false
+    enabled: true
   policy:
-    enabled: false
+    enabled: true
   portal:
-    enabled: false
+    enabled: true
   robot: # Robot Health Check
     enabled: true
   sdc:
-    enabled: false
+    enabled: true
   sdnc:
-    enabled: false
+    enabled: true
   so: # Service Orchestrator
     enabled: true
 
@@ -122,19 +122,15 @@ may want to selectively enable or disable ONAP components by changing the
       config:
         mariadbRootPassword: password
   uui:
-    enabled: false
+    enabled: true
   vfc:
-    enabled: false
+    enabled: true
   vid:
-    enabled: false
+    enabled: true
   vnfsdk:
-    enabled: false
-
-**Step 3.** Build a local Helm repository (from the kubernetes directory)::
-
-  > make all
+    enabled: true
 
-**Step 4.** To setup a local Helm server to server up the ONAP charts::
+**Step 3.** To setup a local Helm server to server up the ONAP charts::
 
   > helm serve &
 
@@ -143,12 +139,16 @@ follows::
 
   > helm repo add local http://127.0.0.1:8879
 
-**Step 5.** Verify your Helm repository setup with::
+**Step 4.** Verify your Helm repository setup with::
 
   > helm repo list
   NAME   URL
   local  http://127.0.0.1:8879
 
+**Step 5.** Build a local Helm repository (from the kubernetes directory)::
+
+  > make all
+
 **Step 6.** Display the charts that available to be deployed::
 
   > helm search -l
@@ -161,12 +161,15 @@ follows::
   local/so                2.0.0      ONAP Service Orchestrator
 
 .. note::
-  The of this Helm repository setup is a one time activity. If you make changes to your deployment charts or values be sure to use `make` to update your local Helm repository.
+  The setup of the Helm repository is a one time activity. If you make changes to your deployment charts or values be sure to use `make` to update your local Helm repository.
 
 **Step 7.** 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 -n dev --namespace onap
+
+.. note::
+  The requirement for the use of the `onap` namespace will be lifted once the OOM team completes their Beijing deveivers.
 
 Use the following to monitor your deployment and determine when ONAP is ready for use::