Documentation: Eclipse, vCPE, VoLTE, ModTemplate 98/70698/1
authorSaryu Shah <ss3917@att.com>
Thu, 18 Oct 2018 01:19:03 +0000 (01:19 +0000)
committerSaryu Shah <ss3917@att.com>
Thu, 18 Oct 2018 01:31:59 +0000 (01:31 +0000)
Documentation: Eclipse, vCPE, VoLTE, ModTemplate
-------------------------------------------------------------

Issue-ID: POLICY-1169

Change-Id: Id501913db5be23f97e5ea5a635e27511546a042a
Signed-off-by: Saryu Shah <ss3917@att.com>
23 files changed:
docs/platform/RunEcl_telemetry.png
docs/platform/Tut_vCPE_appc_request.JPG
docs/platform/Tut_vCPE_final_memory.JPG
docs/platform/Tut_vCPE_get_facts.JPG
docs/platform/Tut_vCPE_guard_not_queried.JPG
docs/platform/Tut_vCPE_guard_result.JPG
docs/platform/Tut_vCPE_insert_abatement.JPG
docs/platform/Tut_vCPE_insert_onset.JPG
docs/platform/Tut_vCPE_policy_active.JPG
docs/platform/Tut_vCPE_policy_final_success.JPG
docs/platform/Tut_vCPE_policy_operation.JPG
docs/platform/Tut_vCPE_policy_operation_success.JPG
docs/platform/Tut_vCPE_policy_start.JPG
docs/platform/Tut_vCPE_simulated_abatement.JPG
docs/platform/Tut_vCPE_simulated_appc_response.JPG
docs/platform/Tut_vCPE_simulated_onset.JPG
docs/platform/Tut_vCPE_simulators_enabled.JPG
docs/platform/mat_hello_world.JPG
docs/platform/runningEclipse.rst
docs/platform/tutorial_VOLTE.rst
docs/platform/tutorial_VOLTE_1.png
docs/platform/tutorial_VOLTE_2.png
docs/platform/tutorial_vCPE.rst

index 38e361f..ae4f65c 100755 (executable)
Binary files a/docs/platform/RunEcl_telemetry.png and b/docs/platform/RunEcl_telemetry.png differ
index fd9d11e..75d8848 100755 (executable)
Binary files a/docs/platform/Tut_vCPE_appc_request.JPG and b/docs/platform/Tut_vCPE_appc_request.JPG differ
index 2f9661e..f68aac7 100755 (executable)
Binary files a/docs/platform/Tut_vCPE_final_memory.JPG and b/docs/platform/Tut_vCPE_final_memory.JPG differ
index 2b9198e..2763725 100755 (executable)
Binary files a/docs/platform/Tut_vCPE_get_facts.JPG and b/docs/platform/Tut_vCPE_get_facts.JPG differ
index b30a4aa..14e52e7 100755 (executable)
Binary files a/docs/platform/Tut_vCPE_guard_not_queried.JPG and b/docs/platform/Tut_vCPE_guard_not_queried.JPG differ
index 8e32dc0..b1818d3 100755 (executable)
Binary files a/docs/platform/Tut_vCPE_guard_result.JPG and b/docs/platform/Tut_vCPE_guard_result.JPG differ
index f850d12..d0da4d5 100755 (executable)
Binary files a/docs/platform/Tut_vCPE_insert_abatement.JPG and b/docs/platform/Tut_vCPE_insert_abatement.JPG differ
index e0aea9f..0316609 100755 (executable)
Binary files a/docs/platform/Tut_vCPE_insert_onset.JPG and b/docs/platform/Tut_vCPE_insert_onset.JPG differ
index c9ccd9d..02544f4 100755 (executable)
Binary files a/docs/platform/Tut_vCPE_policy_active.JPG and b/docs/platform/Tut_vCPE_policy_active.JPG differ
index ed0e785..f063d09 100755 (executable)
Binary files a/docs/platform/Tut_vCPE_policy_final_success.JPG and b/docs/platform/Tut_vCPE_policy_final_success.JPG differ
index dd41866..1666ea6 100755 (executable)
Binary files a/docs/platform/Tut_vCPE_policy_operation.JPG and b/docs/platform/Tut_vCPE_policy_operation.JPG differ
index 9362cc2..9206847 100755 (executable)
Binary files a/docs/platform/Tut_vCPE_policy_operation_success.JPG and b/docs/platform/Tut_vCPE_policy_operation_success.JPG differ
index a33a24c..91be90e 100755 (executable)
Binary files a/docs/platform/Tut_vCPE_policy_start.JPG and b/docs/platform/Tut_vCPE_policy_start.JPG differ
index 06f173f..2133ff8 100755 (executable)
Binary files a/docs/platform/Tut_vCPE_simulated_abatement.JPG and b/docs/platform/Tut_vCPE_simulated_abatement.JPG differ
index 69699f4..3d90e04 100755 (executable)
Binary files a/docs/platform/Tut_vCPE_simulated_appc_response.JPG and b/docs/platform/Tut_vCPE_simulated_appc_response.JPG differ
index 5ee0901..a50b3c2 100755 (executable)
Binary files a/docs/platform/Tut_vCPE_simulated_onset.JPG and b/docs/platform/Tut_vCPE_simulated_onset.JPG differ
index f350e2c..8cd9902 100755 (executable)
Binary files a/docs/platform/Tut_vCPE_simulators_enabled.JPG and b/docs/platform/Tut_vCPE_simulators_enabled.JPG differ
index 04cf799..d52e4c7 100755 (executable)
Binary files a/docs/platform/mat_hello_world.JPG and b/docs/platform/mat_hello_world.JPG differ
index b2bcd88..136efe7 100644 (file)
@@ -36,7 +36,7 @@ To interact with the PDP-D, the Telemetry API can be used. A simple GET on the e
 
     .. code-block:: bash
 
-        curl --silent --user @1b3rt:31nst31n -X GET http://localhost:9696/policy/pdp/engine/ | python -m json.tool
+        curl -k --silent --user @1b3rt:31nst31n -X GET https://localhost:9696/policy/pdp/engine/ | python -m json.tool
 
     .. image:: RunEcl_telemetry.png
 
index 3ccb027..2dc8462 100644 (file)
@@ -58,28 +58,27 @@ Next, we're going to create a file named *dcae.volte.onset.json* and edit it to
 Here are the contents of the VOLTE ONSET message. Copy/paste this into dcae.volte.onset.json:
 
     .. code-block:: json
-    
+
         {
+            "closedLoopControlName": "ControlLoop-VOLTE-2179b738-fd36-4843-a71a-a8c24c70c55b",
+            "closedLoopAlarmStart": 1484677482204798,
             "closedLoopEventClient": "DCAE.HolmesInstance",
-            "policyVersion": "1.0.0.5",
-            "policyName": "vVOLTE",
-            "policyScope": "resource=volte,service=VolteSErvice,type=SampleType,closedLoopControlName=CL-VOLTE-SIG-d925ed73-8231-4d02-9545-db4e101f88f8",
+            "closedLoopEventStatus": "ONSET",
+            "requestID": "97964e10-686e-4790-8c45-bdfa61df770f",
             "target_type": "VM",
+            "target": "vserver.vserver-name",
             "AAI": {
+                "vserver.is-closed-loop-disabled": "false",
+                "vserver.prov-status": "ACTIVE",
                 "vserver.vserver-name": "dfw1lb01lb01",
-                "service-instance.service-instance-id" : "TBD",
-                "generic-vnf.vnf-id" : "TBD",
-                "generic-vnf.vnf-name" : "TBD"
+                "service-instance.service-instance-id" : "vserver-name-16102016-aai3255-data-11-1",
+                "generic-vnf.vnf-id" : "vnf-id-16102016-aai3255-data-11-1",
+                "generic-vnf.vnf-name" : "vnf-name-16102016-aai3255-data-11-1"
             },
-            "closedLoopAlarmStart": 1484677482204798,
-            "closedLoopEventStatus": "ONSET",
-            "closedLoopControlName": "ControlLoop-VOLTE-2179b738-fd36-4843-a71a-a8c24c70c55b",
-            "version": "1.0.2",
-            "target": "vserver.vserver-name",
-            "requestID": "97964e10-686e-4790-8c45-bdfa61df770f",
-            "from": "DCAE"
+            "from": "DCAE",
+            "version": "1.0.2"
         }
-
+        
 
 Enabling the VFC Simulator
 ^^^^^^^^^^^^^^^^^^^^^^^^^^ 
@@ -101,7 +100,7 @@ We are now ready to inject an ONSET message to trigger the VOLTE flow. Simply na
 
     .. code-block:: bash
     
-        http -a @1b3rt:31nst31n PUT :9696/policy/pdp/engine/topics/sources/ueb/unauthenticated.DCAE_CL_OUTPUT/events @dcae.volte.onset.json Content-Type:"text/plain"
+        http --verify=no --default-scheme=https -a @1b3rt:31nst31n PUT :9696/policy/pdp/engine/topics/sources/ueb/unauthenticated.DCAE_CL_OUTPUT/events @dcae.volte.onset.json Content-Type:"text/plain"
 
 You should see some output similar to this:
 
index c1ce8e4..938604d 100755 (executable)
Binary files a/docs/platform/tutorial_VOLTE_1.png and b/docs/platform/tutorial_VOLTE_1.png differ
index 51f7e7a..53ee780 100755 (executable)
Binary files a/docs/platform/tutorial_VOLTE_2.png and b/docs/platform/tutorial_VOLTE_2.png differ
index 7c6c9fb..8c65aab 100644 (file)
@@ -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