diff options
author | Bartek Grzybowski <b.grzybowski@partner.samsung.com> | 2019-09-25 11:21:42 +0200 |
---|---|---|
committer | Bartek Grzybowski <b.grzybowski@partner.samsung.com> | 2019-09-25 11:47:40 +0200 |
commit | dbb3ba15b358043f9e45d8dd211ce1bd970fb08e (patch) | |
tree | 8c87b23a5d5bafeacd1d7fb147eeeb2399ec7381 /docs/docs_vCPE.rst | |
parent | 43fdf7b1938877fec2a10022a533c0491b6e8c95 (diff) |
Automate vCPE closed loop policy pushing
Added a library routine to set up CL policy
in an idempotent fashion.
Description of CL pushing related manual step
was removed from documentation.
Change-Id: I1fad5d71481252ce803dd58c6ccbbcfa0a4d246f
Signed-off-by: Bartek Grzybowski <b.grzybowski@partner.samsung.com>
Issue-ID: INT-1267
Diffstat (limited to 'docs/docs_vCPE.rst')
-rw-r--r-- | docs/docs_vCPE.rst | 9 |
1 files changed, 1 insertions, 8 deletions
diff --git a/docs/docs_vCPE.rst b/docs/docs_vCPE.rst index c6534b821..48b56c253 100644 --- a/docs/docs_vCPE.rst +++ b/docs/docs_vCPE.rst @@ -162,14 +162,7 @@ Here are the main steps to run the use case in Integration lab environment, wher ~/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. Push vCPE closed loop Policy. Copy the two operational policy from vcpe/preload_templates to Robot container and then run the following two commands inside Robot container. You can find more details in JIRA INT-1089 - Create vCPE closed loop policy and push to policy engine - -:: - - curl -k --silent --user 'healthcheck:zb!XztG34' -X POST "https://policy-api:6969/policy/api/v1/policytypes/onap.policies.controlloop.Operational/versions/1.0.0/policies" -H "Accept: application/json" -H "Content-Type: application/json" -d @operational.vcpe.json.txt - curl --silent -k --user 'healthcheck:zb!XztG34' -X POST "https://policy-pap:6969/policy/pap/v1/pdps/policies" -H "Accept: application/json" -H "Content-Type: application/json" -d @operational.vcpe.pap.json.txt - -19. 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 +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 :: |