diff options
| author |   thmsdt <thomas.kulik@telekom.de> | 2021-09-27 16:40:27 +0200 |
|---|---|---|
| committer | thmsdt <thomas.kulik@telekom.de> | 2021-09-27 16:41:23 +0200 |
| commit | e5d983ed01b59241c5186a51d120fed48e52af64 (patch) | |
| tree | 15ec83ea5a040284b119baa3c2a996a3080fdb47 | |
| parent | a27216d5220d3380f62bd1bfda7c4d8fed76da36 (diff) | |
fix broken link error in vfwcl-deployment-tutorial/index.rst
Issue-ID: DOC-766
Signed-off-by: thmsdt <thomas.kulik@telekom.de>
Change-Id: I66fec192450480ae285f265d985d35b9e2804f87
| -rw-r--r-- | docs/guides/onap-user/vfwcl-deployment-tutorial/index.rst | 7 |
1 files changed, 5 insertions, 2 deletions
diff --git a/docs/guides/onap-user/vfwcl-deployment-tutorial/index.rst b/docs/guides/onap-user/vfwcl-deployment-tutorial/index.rst index f10a13a88..a91eaea75 100644 --- a/docs/guides/onap-user/vfwcl-deployment-tutorial/index.rst +++ b/docs/guides/onap-user/vfwcl-deployment-tutorial/index.rst @@ -1290,9 +1290,12 @@ The below instructions can be used for this configuration # sudo ip route add 169.254.169.254 via 10.10.10.11 dev eth3 - Verify that the metadata service is accessible by issuing the following command - - curl http://169.254.169.254 + .. code-block:: + + curl http://169.254.169.254 + -3. The events generated from this program will trigger the vFW CL flow. +1. The events generated from this program will trigger the vFW CL flow. In a successful deployment of the vFW CL, the graphs look as in the screenshot below. We can see that the bars are shorter and more uniform as compared to vFW deployment without the CL |