aboutsummaryrefslogtreecommitdiffstats
path: root/docs/platform/tutorial_vFW.rst
diff options
context:
space:
mode:
authorSaryu Shah <ss3917@att.com>2017-11-10 17:02:32 +0000
committerSaryu Shah <ss3917@att.com>2017-11-10 18:39:47 +0000
commit355b5793d028807145115d8a67cf3efc33cdc89d (patch)
tree46183dcaff3c8c20bcab1b5d72c8d5db8268ba2d /docs/platform/tutorial_vFW.rst
parentf8732acc618b1772040704fc881da360979953db (diff)
Documentation for vCPE and State Mgmt
Documentation for vCPE and State Mgmt. Removed release notes from index ------------------------------------------------------------- Issue-Id: POLICY-335 Change-Id: If8c39261ad1e6cee41fa065943e06f5325aefba2 Signed-off-by: Saryu Shah <ss3917@att.com>
Diffstat (limited to 'docs/platform/tutorial_vFW.rst')
-rw-r--r--docs/platform/tutorial_vFW.rst9
1 files changed, 3 insertions, 6 deletions
diff --git a/docs/platform/tutorial_vFW.rst b/docs/platform/tutorial_vFW.rst
index 639b632ca..4b402d017 100644
--- a/docs/platform/tutorial_vFW.rst
+++ b/docs/platform/tutorial_vFW.rst
@@ -17,10 +17,7 @@ The vFW flow begins with an onset message that is sent from DCAE notifying the P
Initial Setup
^^^^^^^^^^^^^
-For this tutorial, a feature for simulating components involved in the flow outside of Policy will be turned on. Run "features enable controlloop-utils".
-
-
-The first step is to access the docker container of name *drools*.
+For this tutorial, a feature for simulating components involved in the flow outside of Policy will be turned on. Run "*features enable controlloop-utils*".
.. image:: Tut_vFW_simulators_enabled.JPG
@@ -53,11 +50,11 @@ Inject the onset using the Telemetry API.
.. image:: Tut_vFW_onset_injected.JPG
-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 assciated 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 VNF that is currently processing.
+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 VNF that is currently processing.
.. image:: Tut_vFW_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.
+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.
.. image:: Tut_vFW_policy_active.JPG