aboutsummaryrefslogtreecommitdiffstats
path: root/docs/docs_vCPE.rst
diff options
context:
space:
mode:
authorBartek Grzybowski <b.grzybowski@partner.samsung.com>2019-10-07 14:25:30 +0200
committerBartek Grzybowski <b.grzybowski@partner.samsung.com>2019-10-07 14:25:30 +0200
commit92b3cd11dbd906f9304a2436498c6109f8d9a0f5 (patch)
treea20d99a1d14be7a140da9f754044ebadc0d4ba05 /docs/docs_vCPE.rst
parent383a3e820a83c7c526aee35312a94a923a53022c (diff)
Automate curl installation in sdnc container (vCPE)
Curl package will be automatically installed be the healthcheck-k8s.py script. Change-Id: I7fc5579524c7519f6153b02d0de0000dc0138992 Signed-off-by: Bartek Grzybowski <b.grzybowski@partner.samsung.com> Issue-ID: INT-1313
Diffstat (limited to 'docs/docs_vCPE.rst')
-rw-r--r--docs/docs_vCPE.rst16
1 files changed, 5 insertions, 11 deletions
diff --git a/docs/docs_vCPE.rst b/docs/docs_vCPE.rst
index 48b56c253..25c4647c2 100644
--- a/docs/docs_vCPE.rst
+++ b/docs/docs_vCPE.rst
@@ -136,33 +136,27 @@ Here are the main steps to run the use case in Integration lab environment, wher
vcpe.py infra
-13. Install curl command on sdnc container inside sdnc-sdnc-0 pod
-
-::
-
- sudo apk add curl
-
-14. From Rancher node run vcpe healthcheck command to check connectivity from sdnc to brg and gmux, and vpp configuration of brg and gmux. Write down BRG MAC address printed out at the last line
+13. From Rancher node run vcpe healthcheck command to check connectivity from sdnc to brg and gmux, and vpp configuration of brg and gmux. Write down BRG MAC address printed out at the last line
::
healthcheck-k8s.py --namespace <namespace name> --environment <env name>
-15. Instantiate vCPE customer service. Input the BRG MAC when prompt
+14. Instantiate vCPE customer service. Input the BRG MAC when prompt
::
vcpe.py customer
-16. Update libevel.so in vGMUX VM and restart the VM. This allows vGMUX to send events to VES collector in close loop test. See tutorial wiki for details
+15. Update libevel.so in vGMUX VM and restart the VM. This allows vGMUX to send events to VES collector in close loop test. See tutorial wiki for details
-17. Run heatbridge. The heatbridge command usage: demo-k8s.sh <namespace> heatbridge <stack_name> <service_instance_id> <service> <oam-ip-address>, please refer to vCPE tutorial page on how to fill in those paraemters. See an example as following:
+16. Run heatbridge. The heatbridge command usage: demo-k8s.sh <namespace> heatbridge <stack_name> <service_instance_id> <service> <oam-ip-address>, please refer to vCPE tutorial page on how to fill in those paraemters. See an example as following:
::
~/integration/test/vcpe# ~/oom/kubernetes/robot/demo-k8s.sh onap heatbridge vcpe_vfmodule_e2744f48729e4072b20b_201811262136 d8914ef3-3fdb-4401-adfe-823ee75dc604 vCPEvGMUX 10.0.101.21
-18. Start closed loop test by triggering packet drop VES event, and monitor if vGMUX is restarting. You may need to run the command twice if the first run fails
+17. Start closed loop test by triggering packet drop VES event, and monitor if vGMUX is restarting. You may need to run the command twice if the first run fails
::