summaryrefslogtreecommitdiffstats
path: root/docs/platform/tutorial_vCPE.rst
diff options
context:
space:
mode:
authorJorge Hernandez <jorge.hernandez-herrero@att.com>2018-10-18 16:09:12 +0000
committerGerrit Code Review <gerrit@onap.org>2018-10-18 16:09:12 +0000
commit1f7c3ab5d60f4e25ef5a184b65322082a9c538ce (patch)
treeb4813cd76e1b8d06b05bf22c40001d7464f66e99 /docs/platform/tutorial_vCPE.rst
parentf52148aea35d7450004385fe190a6dedb9fba1d8 (diff)
parent65640a2968358a74033451ea65efd8987cf2ee55 (diff)
Merge "Documentation: Eclipse, vCPE, VoLTE, ModTemplate"
Diffstat (limited to 'docs/platform/tutorial_vCPE.rst')
-rw-r--r--docs/platform/tutorial_vCPE.rst9
1 files changed, 4 insertions, 5 deletions
diff --git a/docs/platform/tutorial_vCPE.rst b/docs/platform/tutorial_vCPE.rst
index 7c6c9fb05..8c65aabc3 100644
--- a/docs/platform/tutorial_vCPE.rst
+++ b/docs/platform/tutorial_vCPE.rst
@@ -32,7 +32,7 @@ The telemetry API is used to see what is in memory. There should only be 1 fact,
.. code-block:: bash
- curl --silent --user @1b3rt:31nst31n -X GET http://localhost:9696/policy/pdp/engine/controllers/amsterdam/drools/facts/amsterdam | python -m json.tool
+ curl -k --silent --user @1b3rt:31nst31n -X GET https://localhost:9696/policy/pdp/engine/controllers/amsterdam/drools/facts/amsterdam | python -m json.tool
.. image:: Tut_vCPE_get_facts.JPG
@@ -47,7 +47,7 @@ Inject the onset using the Telemetry API.
.. code-block:: bash
- curl --silent --user @1b3rt:31nst31n --header "Content-Type: text/plain" --data @dcae.vcpe.onset.json -X PUT http://localhost:9696/policy/pdp/engine/topics/sources/ueb/unauthenticated.DCAE_EVENT_OUTPUT/events | python -m json.tool
+ curl -k --silent --user @1b3rt:31nst31n --header "Content-Type: text/plain" --data @dcae.vcpe.onset.json -X PUT https://localhost:9696/policy/pdp/engine/topics/sources/ueb/unauthenticated.DCAE_EVENT_OUTPUT/events | python -m json.tool
.. image:: Tut_vCPE_insert_onset.JPG
@@ -55,7 +55,6 @@ Inject the onset using the Telemetry API.
Now check the facts in memory, there should be 7 objects present. Two timers exist to put a time limit on the operation and on the overall control loop (in the case of retries or policy chaining). The event and it's associated manager and operation manager are also present in memory. A lock on the target entity is inserted to ensure no other events try to take action on the VM/VNF that is currently processing.
-
.. image:: Tut_vCPE_get_facts_2.JPG
The network log will be used to monitor the activity coming in and out of the PDP-D. This log is located at *$POLICY_HOME/logs/network.log*. This will show the notifications that the PDP-D sends out at different stages of processing. The order of successful processing begins with an ACTIVE notification to show that the onset was acknowledged and the operation is beginning transit.
@@ -82,7 +81,7 @@ Inject the response using the Telemetry API.
.. code-block:: bash
- curl --silent --user @1b3rt:31nst31n --header "Content-Type: text/plain" --data @appc.lcm.success.json -X PUT http://localhost:9696/policy/pdp/engine/topics/sources/ueb/APPC-LCM-WRITE/events | python -m json.tool
+ curl -k --silent --user @1b3rt:31nst31n --header "Content-Type: text/plain" --data @appc.lcm.success.json -X PUT https://localhost:9696/policy/pdp/engine/topics/sources/ueb/APPC-LCM-WRITE/events | python -m json.tool
.. image:: Tut_vCPE_inject_appc_response.JPG
@@ -98,7 +97,7 @@ Inject the abatement message using the Telemetry API.
.. code-block:: bash
- curl --silent --user @1b3rt:31nst31n --header "Content-Type: text/plain" --data @dcae.vcpe.abatement.json -X PUT http://localhost:9696/policy/pdp/engine/topics/sources/ueb/unauthenticated.DCAE_EVENT_OUTPUT/events | python -m json.tool
+ curl -k --silent --user @1b3rt:31nst31n --header "Content-Type: text/plain" --data @dcae.vcpe.abatement.json -X PUT https://localhost:9696/policy/pdp/engine/topics/sources/ueb/unauthenticated.DCAE_EVENT_OUTPUT/events | python -m json.tool
.. image:: Tut_vCPE_insert_abatement.JPG