X-Git-Url: https://gerrit.onap.org/r/gitweb?a=blobdiff_plain;f=docs%2Fplatform%2Ftutorial_vDNS.rst;h=330bb64efff0218729017b001c9e72849207fe00;hb=62e5a4a553e00d979d17e169c505acf624b11d5e;hp=d9a2b6d5c124baeacb2ffaf3b938caa0cab47c0f;hpb=90a680cc3e09f9aeedbe430416ce93b5cdbdc8e6;p=policy%2Fengine.git diff --git a/docs/platform/tutorial_vDNS.rst b/docs/platform/tutorial_vDNS.rst index d9a2b6d5c..330bb64ef 100644 --- a/docs/platform/tutorial_vDNS.rst +++ b/docs/platform/tutorial_vDNS.rst @@ -53,13 +53,29 @@ Next, we're going to create a file named *dcae.vdns.onset.json* and edit it to p .. code-block:: bash touch dcae.vdns.onset.json - vi dcae.vdns.onset json + vi dcae.vdns.onset.json Here are the contents of the vDNS ONSET message. Copy/paste this into dcae.vdns.onset.json: - .. code-block:: bash + .. code-block:: json - { "closedLoopEventClient": "DCAE_INSTANCE_ID.dcae-tca", "target_type": "VNF", "AAI": { "vserver.vserver-name": "vlb-lb-32c8", "vserver.is-closed-loop-disabled": "false" }, "closedLoopAlarmStart": 1484677482204798, "closedLoopEventStatus": "ONSET", "closedLoopControlName": "ControlLoop-vDNS-6f37f56d-a87d-4b85-b6a9-cc953cf779b3", "version": "1.0.2", "target": "vserver.vserver-name", "requestID": "99999999-686e-4790-8c45-bdfa61df770f", "from": "DCAE" } + { + "closedLoopControlName": "ControlLoop-vDNS-6f37f56d-a87d-4b85-b6a9-cc953cf779b3", + "closedLoopAlarmStart": 1484677482204798, + "closedLoopEventClient": "DCAE_INSTANCE_ID.dcae-tca", + "closedLoopEventStatus": "ONSET", + "requestID": "e4f95e0c-a013-4530-8e59-c5c5f9e539b6", + "target_type": "VNF", + "target": "vserver.vserver-name", + "AAI": { + "vserver.is-closed-loop-disabled": "false", + "vserver.prov-status": "ACTIVE", + "vserver.vserver-name": "dfw1lb01lb01" + }, + "from": "DCAE", + "version": "1.0.2" + } + Enabling the AAI and SO Simulators @@ -82,11 +98,11 @@ We are now ready to inject an ONSET message to trigger the vDNS flow. Simply nav .. code-block:: bash - http -a @1b3rt:31nst31n PUT :9696/policy/pdp/engine/topics/sources/ueb/unauthenticated.DCAE_CL_OUTPUT/events @dcae.vdns.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.vdns.onset.json Content-Type:"text/plain" You should see some output similar to this: -.. image:: tutorial_vDNS_1.png + .. image:: tutorial_vDNS_1.png You can view the logs to see the network activity or find any errors that may have occurred. Logs are located in */opt/app/policy/logs*. @@ -95,9 +111,9 @@ Reading the logs Once you've injected the onset message, this should appear in the network.log: -.. image:: tutorial_vDNS_2.png + .. image:: tutorial_vDNS_2.png End of Document -.. SSNote: Wiki page ref. https://wiki.onap.org/display/DW/Using+guard+in+the+PDP-D +.. SSNote: Wiki page ref. https://wiki.onap.org/display/DW/Tutorial%3A+Testing+the+vDNS+Use+Case+in+a+standalone+PDP-D