summaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/files/Dovetail.rst11
-rw-r--r--docs/files/VNFSDK-LFN-CVC.rst17
2 files changed, 6 insertions, 22 deletions
diff --git a/docs/files/Dovetail.rst b/docs/files/Dovetail.rst
index 1205786..422832b 100644
--- a/docs/files/Dovetail.rst
+++ b/docs/files/Dovetail.rst
@@ -8,18 +8,9 @@
Welcome to Dovetail Integration's documentation!
=================================================
-Contents:
-
.. toctree::
:maxdepth: 2
-
-
-Indices and tables
-==================
-
-* :ref:`genindex`
-* :ref:`search`
-
+
User Stories
============
diff --git a/docs/files/VNFSDK-LFN-CVC.rst b/docs/files/VNFSDK-LFN-CVC.rst
index c9304cf..ee11015 100644
--- a/docs/files/VNFSDK-LFN-CVC.rst
+++ b/docs/files/VNFSDK-LFN-CVC.rst
@@ -37,8 +37,7 @@ Objectives
----------
* LFN/ONAP wants test platform where VNF packages could be certified using ONAP requirements to drive industry adoption
* Provide an platform where vendor/operator can develop, deploy, run test cases and query the results
-* Test cases, test results and VNF should be manageable .i,e with authorization, so only user with given roles is allowed to perform operation like
-VNF package upload/download, run compliance verification tests, allow only specific VIM for specific users, etc.
+* Test cases, test results and VNF should be manageable .i,e with authorization, so only user with given roles is allowed to perform operation like VNF package upload/download, run compliance verification tests, allow only specific VIM for specific users, etc.
* Test results should be persisted and should be available for human analysis later via LFN infrastructure.
* Provides test flow where author make flow across different test cases for a given program like compliance verification and VNFREQS/SOL0004.
* Provide integration with OPNFV dovetail to run test cases across dovetail and VNFSDK.
@@ -48,7 +47,7 @@ VNF package upload/download, run compliance verification tests, allow only speci
.. |image0| image:: VTP.png
:height: 600px
- :width: 600px
+ :width: 900px
Architecture
------------
@@ -57,15 +56,15 @@ Architecture
.. |image1| image:: VTParch.png
:height: 600px
- :width: 600px
+ :width: 900px
CVC Structures
==============
-|image0|
+|image2|
-.. |image0| image:: cvc.png
+.. |image2| image:: cvc.png
:height: 600px
:width: 600px
@@ -92,14 +91,8 @@ Casablanca Implemented requriements
* - R-35851
- The VNF Package MUST include VNF topology that describes basic network and application connectivity internal and external to the VNF including Link type, KPIs, Bandwidth, latency, jitter, QoS (if applicable) for each interface.
- * - R-43958
- - The VNF Package MUST include documentation describing the tests that were conducted by the VNF provider and the test results.
-
* - R-66070
- The VNF Package MUST include VNF Identification Data to uniquely identify the resource for a given VNF provider. The identification data must include: an identifier for the VNF, the name of the VNF as was given by the VNF provider, VNF description, VNF provider, and version.
* - R-77707
- The VNF provider MUST include a Manifest File that contains a list of all the components in the VNF package.
-
- * - R-77786
- - The VNF Package MUST include all relevant cookbooks to be loaded on the ONAP Chef Server.