Merge "Migration of Service Design from Wiki to Readthedocs User guide small changes...

diff --git a/docs/guides/onap-user/pre-onboarding/index.rst b/docs/guides/onap-user/pre-onboarding/index.rst
new file mode 100644 (file)
index 0000000..155ec56
--- /dev/null
+++ b/docs/guides/onap-user/pre-onboarding/index.rst
@@ -0,0 +1,126 @@
+.. This work is licensed under a Creative Commons Attribution 4.0
+.. International License. http://creativecommons.org/licenses/by/4.0
+.. Copyright 2019 ONAP Contributors. All rights reserved.
+
+Pre-Onboarding
+==============
+
+    * `Create a Tenant`_
+    * `Validate VFs (Virtual Functions)`_
+    * `Generate Manifest and Package Artifacts`_
+
+Create a Tenant
+---------------
+
+Each service requires a tenant_ (a group of users who share a common access)
+in which resources are stored in the cloud. This process is performed using
+facilities of the network cloud, outside of ONAP. Confirm that the tenant is
+created and note the tenant ID.
+
+ONAP admin users can configure a cloud-owner to add new cloud resources.
+These are the computing and networking resources, that will support
+running VNFs. A cloud-owner holds a keystone URL, login, region and
+password, in the case of an Openstack cluster. A cloud-owner also
+belongs to a region. The region name should be the same as the Openstack
+region. Prior to creation of a cloud-owner, its region must be created
+first. Multiple tenants can share the same cloud-owner. Note that these
+tenants are ONAP tenants, not Openstack tenants. Tenant register
+services that customers are allowed to deploy. Finally, the customer is
+like an instance of the tenant.
+
+Note: there is no GUI (yet) to configure these objects. REST requests
+are sent to AAI to achieve the configuration. For a detailed list of
+required REST commands see:
+
+https://wiki.onap.org/display/DW/running+vFW+Demo+on+ONAP+Amsterdam+Release
+
+The overall process is as follows:
+
+ #. Create a region and a cloud-owner. This steps registers Openstack
+    credentials. This is the only step requiring entering Openstack specific
+    parameters.
+
+ #. Create a complex. The complex describes the coverage of the region with
+    a street address etc.
+
+ #. Create a service. The service name should match the name of the service
+    onboarded in SDC.
+
+ #. Create a tenant. Tenant in ONAP stores a design for a generic customer.
+
+ #. Associate tenants with their allowed services.
+
+ #. Create an instance of the tenant or customer. The customer is visible in
+    VID. A VID user can deploy allowed services on this new customer.
+
+   |image1|
+
+
+Validate VFs (Virtual Functions)
+--------------------------------
+
+Prior to resource onboarding, the Certification Group does the following:
+
+ - onboards the Heat template(s) and metadata to the SDC catalog
+ - creates a test VF
+ - runs the Heat scanning tools
+ - shares the results with any group that approves Virtual Functions
+
+In parallel, the Certification Group onboards the VF Image and OS to a
+standalone ONAP instance (the "sandbox") and performs the following:
+
+ - security scan
+ - compatibility test for the OS and vendor binary
+ - malware scan
+
+The Certification group then instantiates the VF image using the vendor
+Heat (if provided) in order to validate that the VM can run on the Network
+Cloud.
+
+No VF functionality testing is performed at this stage.
+
+
+Generate Manifest and Package Artifacts
+---------------------------------------
+
+Before onboarding resources, run generate-manifest.py to generate a
+MANIFEST file. These steps are performed outside SDC.
+
+OBSOLETE: **Prerequisites:** Obtain Heat/ENV files and other files required for
+onboarding. See the reference document `VNF Heat Template Requirements
+for OpenECOMP <https://wiki.onap.org/download/attachments/1015849/VNF%20Heat%20Template%20Requirements%20for%20OpenECOMP.pdf?version=2&modificationDate=1487262292000&api=v2>`__ for details.
+
+UPDATE: see VNF Modeling Requirements / HEAT: https://onap.readthedocs.io/en/casablanca/submodules/vnfrqts/requirements.git/docs/Chapter5/Heat/index.html
+
+#. Put the Heat, ENV, nested Heat, and other files used by get-file in templates
+   in a directory.
+
+   Naming guidelines:
+
+    - The base Heat should include "base" in the name.
+    - The ENV file name should match the name of the Heat file with which it
+      is associated.
+    - All get-file file names need to be unique.
+
+#. Put the python script in a directory one level above the directory that
+   contains the Heat/ENV and other files.
+
+   For example, [dir x]/[dir y]
+
+    - [dir y] contains the Heat/ENV files and other files
+    - [dir x] contains the python script
+
+#. Run the script on the Windows command line:
+
+   .. code-block::
+
+    python generate-manifest.py -f "dir y"
+
+#. Examine the manifest file and confirm that is correct.
+
+#. Package all Heat/ENV files, all other files, and the MANIFEST.json
+   into one .zip file.
+
+
+.. |image1| image:: media/tenant.png
+.. _tenant: https://wiki.onap.org/display/DW/Glossary#Glossary-tenant

diff --git a/docs/guides/onap-user/pre-onboarding/media/tenant.png b/docs/guides/onap-user/pre-onboarding/media/tenant.png
new file mode 100644 (file)
index 0000000..b5ae8c6
Binary files /dev/null and b/docs/guides/onap-user/pre-onboarding/media/tenant.png differ

diff --git a/docs/guides/onap-user/service-distribution/index.rst b/docs/guides/onap-user/service-distribution/index.rst
new file mode 100644 (file)
index 0000000..4ed2310
--- /dev/null
+++ b/docs/guides/onap-user/service-distribution/index.rst
@@ -0,0 +1,135 @@
+.. This work is licensed under a Creative Commons Attribution 4.0
+.. International License. http://creativecommons.org/licenses/by/4.0
+.. Copyright 2019 ONAP Contributors.  All rights reserved.
+
+Governance Approval and Service Distribution
+============================================
+
+Each ONAP platform operator will have a specific set of policies
+and procedures for approving Services and deploying them in the
+operator's ONAP environment. This outline describes the general
+flow of such procedures.
+
+**Goal:** Add all information required to create, instantiate, and
+manage a service.
+
+**Tools:** SDC
+
+**SDC user roles:** Governor, Ops
+
+Steps
+-----
+
+- `Review a Service for Governance Approval`_
+- `Request Service Distribution`_
+- `Distribute a Service`_
+- `Verify that the DCAE Blueprint is Deployed`_
+
+|image1|
+
+**Figure 1. Workflow**
+
+Review a Service for Governance Approval
+----------------------------------------
+
+A member of the Governance Board performs a governance review of a
+certified service and its associated VFs, and then approves (or rejects)
+the artifacts for distribution.
+
+**Prerequisites:** Service is tested.
+
+**Steps**
+
+#. Sign in to SDC as a Governor.
+#. From the HOME page, click CATALOG and select a service that is ready
+   for governance review.
+#. Review the service and its associated resources.
+#. To view deployment artifacts:
+
+   #. Click *Composition* tab (left pane) and then click the Deployment
+      Artifact icon (right pane) to see the list of artifacts.
+   #. Click the download icon adjacent to an artifact to download and
+      view it.
+
+#. When the review is complete, click:
+
+   -  *Accept* if the service passes the governance review. The service is
+      marked Approved for Distribution.
+   -  *Reject* if the service fails the governance review. The service is
+      marked Rejected for Distribution.
+
+After a service receives governance approval, it moves into the Waiting
+to be Distributed section of the Operations Workspace (Ops role)
+
+Request Service Distribution
+----------------------------
+
+Request service distribution to populate all appropriate ONAP
+components with the resources and artifacts ssociated with the service and its
+VFs.
+
+**Prerequisites:**
+
+A service has received governance approval and is
+available in the Waiting to be Distributed section of the SDC Operations
+Workspace (under the Ops Role). For more information, see
+`Review a Service for Governance Approval`_.
+
+The steps shown here are generic; each service provider has a different,
+specific set of instructions. Contact your site IT support for the
+particulars.
+
+**Steps**
+
+#. Open at ticket request at your site
+#. Make a "DISTRIBUTION REQUEST"
+#. Provide the following information in your request:
+
+   -  Environment
+   -  Name of service to be distributed
+   -  Version number
+   -  [Optional] Additional information or instructions (provide special
+      instructions for the request)
+   -  Your user ID
+   -  [Optional] Alternate Contact user ID (provide an alternate contact
+      if the primary contact is unavailable)
+
+Distribute a Service
+--------------------
+
+**Prerequisites:** The service is approved.
+
+**Steps**
+
+
+#. Sign in to SDC as Ops.
+#. In the Active Projects pane (left pane) of the HOME page, select the
+   W*aiting For Distribution* check box.
+#. Select a service that is ready for distribution.
+#. Review the version history to verify that the correct version is
+   selected.
+#. In the header, click *Distribute*.
+
+   The service moves from the Ready For Distribution folder to the
+   Distributed Services folder.
+
+#. From the Workspace pane, click *Distributed Services*.
+   All distributed services display.
+#. Select the service distributed in step 5 and click *Monitor*.
+   The Distribution Report displays.
+#. In the Distribution Report, navigate to the Component ID for the
+   service and click the adjacent down arrow.
+   The report shows all components associated with the service and their
+   distribution statuses, such as DOWNLOAD_OK.
+#. Review the status of each component.
+
+Verify that the DCAE Blueprint is Deployed
+------------------------------------------
+
+The DCAE controller requires a blueprint (or guideline) to be available
+at the site on which the first VNF is deployed. This blueprint is a
+management workflow and configuration description for a given VNF, and
+it must be available after completing the service distribution process
+and before beginning the instantiation process.
+
+.. |image1| image:: media/design_governance_workflow.png

diff --git a/docs/guides/onap-user/service-distribution/media/design_governance_workflow.png b/docs/guides/onap-user/service-distribution/media/design_governance_workflow.png
new file mode 100644 (file)
index 0000000..44d6b70
Binary files /dev/null and b/docs/guides/onap-user/service-distribution/media/design_governance_workflow.png differ

diff --git a/docs/guides/onap-user/vfcreation/index.rst b/docs/guides/onap-user/vfcreation/index.rst
new file mode 100644 (file)
index 0000000..f4c8c15
--- /dev/null
+++ b/docs/guides/onap-user/vfcreation/index.rst
@@ -0,0 +1,177 @@
+.. This work is licensed under a Creative Commons Attribution 4.0
+.. International License. http://creativecommons.org/licenses/by/4.0
+.. Copyright 2019 ONAP Doc Team.  All rights reserved.
+
+VF Creation and Testing
+=======================
+**Goal**: Using VSPs, create one or more VFs as the building blocks for a
+service. Validate and certify the VFs.
+
+**ONAP Component**: SDC
+
+**SDC user roles**: Designer, Tester
+
+|image1|
+
+Steps
+-----
+
+- `Create a VF`_
+- `Update a VF [optional]`_
+- `Submit a VF for testing`_
+- `Test a VF`_
+
+Create a VF
+-----------
+
+**Prerequisites:**
+
+- Create a license for each VF (see Create a license model) (see also the
+  tutorial Creating a Licensing Model)
+- Create a Vendor Software Product.
+
+**Steps**
+
+#. From the SDC HOME page, click the *Vendor Software Component* icon in the
+   header (upper right).
+
+   |image2|
+
+#. From the Import VF box, expand a VSP name and click the *Import VSP* icon.
+
+   |image3|
+
+#. In the General section, complete all fields.
+
+   .. note:: Use the letters "VF" in the name to indicate that the component is a VF.
+
+#. Click *Create*.
+
+   - A message displays while VF creation is in progress. (This can take up to
+     10 minutes.)
+   - A message displays when VF creation is complete.
+
+#. Click *Check In* to save changes.
+
+   - A box displays for confirming the changes.
+
+#. Enter a comment and click *OK*.
+
+   - A message displays when the VF is checked in.
+
+#. [Optional]  At any time before submitting the VF for testing, click these
+   options to update VF information:
+
+   .. note:: These tasks can be done only before submitting the VF for testing.
+
+   - Icon — change the icon associated with the VF (vendor-supplied icons are
+     preferred)
+   - Deployment Artifacts — download, view, modify, or change VF deployment
+     artifacts (for example, the contents of the Heat .zip file, which contains
+     the Heat volume template, the VF license, etc.)
+   - Information Artifacts — view or upload artifacts, such as test scripts, test
+     results, or the AIC questionnaire
+   - TOSCA Artifacts — view or upload the TOSCA model or the TOSCA template
+   - Properties — define or update VF properties (not used in Release 1)
+   - Composition — view or edit the graphical representation of the resource-level
+     TOSCA model (generated from the Heat template)
+   - Activity Log — view activity related to assets associated with the VF
+     (displays the action, date, user, status, and any comments related to each
+     action)
+   - Deployment — view VF modules defined in the Heat template
+   - Inputs — view inputs defined for the resource-level TOSCA model
+
+#. After creating a VF, submit it for testing (see `Submit a VF for testing`_).
+
+Update a VF [optional]
+----------------------
+
+- Update the VSP and other artifacts in a VF.
+- Upload a new version the VSP to the VF whenever the VSP is updated (see steps
+  3 to 5). Other reasons for updating a VF include:
+
+  - artifact changes at the VF level that need be uploaded, for example,
+    changes to ENV values (see step 6)
+
+**Prerequisites:**
+
+- `Create a VF`_.
+- If the VSP was updated: Update a VSP [optional]
+
+**Steps**
+
+#. From the SDC HOME page, click *CATALOG* and search for a VF.
+
+#. In the General section, click *Check Out*.
+   The Select VSP field is displays.
+
+#. In the Select VSP field, click *Browse*.
+   The Import VF box displays and shows the VSP that was used to create the VF.
+
+#. Expand the VSP field and click.
+
+   |image4|
+
+#. Click |image5|
+   A progress bar displays. |image6|
+
+#. Click *Deployment Artifact* to edit, upload, or delete associated [Optional]
+   deployment artifacts.
+
+#. Click *Information Artifact* and edit, upload, or delete associated
+   [Optional] information artifacts.
+
+#. Click *Check In* to save changes.
+
+#. After updating the VF:
+
+   - Submit the VF for testing (see Submit a VF for testing).
+   - Update the VF version in any service that contains the VF
+     (see step 4 in Update a service [optional]).
+
+Submit a VF for testing
+-----------------------
+
+**Prerequisites:** `Create a VF`_
+
+**Steps**
+
+#. When a VF is ready for testing, click *CATALOG* and service for the VF.
+#. Click the VF and click *Submit for Testing*.
+
+   |image7|
+
+   |image8|
+
+#. Enter a message for the testers asking that they begin service certification
+   and click *OK*.
+
+   The default mail client launches with a draft email containing the message.
+
+#. Add the email addresses of the people on the Certification Group for this
+   site with the *Tester* role and send the email.
+
+Test a VF
+---------
+
+Test the design and artifacts of a VF.
+
+**Prerequisites:** `Submit a VF for testing`_.
+
+**Steps**
+
+#. Sign in to SDC as a *Tester*.
+#. From the HOME page, select *Ready For Testing* under Active Projects.
+#. In the right pane, click the VF.
+#. Click *Start Testing*.
+#. Test the VF.
+#. When testing is complete, click *Accept*.
+
+.. |image1| image:: media/design_vf_workflow.png
+.. |image2| image:: media/image2017-1-27_11-13-30.png
+.. |image3| image:: media/image2017-1-27_11-14-3.png
+.. |image4| image:: media/image2017-1-27_11-17-18.png
+.. |image5| image:: media/sdc_artifact_update.png
+.. |image6| image:: media/design_vf_updatevspmessage.png
+.. |image7| image:: media/image2017-1-27_11-20-13.png
+.. |image8| image:: media/image2017-1-27_11-21-4.png

diff --git a/docs/guides/onap-user/vfcreation/media/design_vf_updatevspmessage.png b/docs/guides/onap-user/vfcreation/media/design_vf_updatevspmessage.png
new file mode 100644 (file)
index 0000000..bf401da
Binary files /dev/null and b/docs/guides/onap-user/vfcreation/media/design_vf_updatevspmessage.png differ

diff --git a/docs/guides/onap-user/vfcreation/media/design_vf_workflow.png b/docs/guides/onap-user/vfcreation/media/design_vf_workflow.png
new file mode 100644 (file)
index 0000000..d3e8312
Binary files /dev/null and b/docs/guides/onap-user/vfcreation/media/design_vf_workflow.png differ

diff --git a/docs/guides/onap-user/vfcreation/media/image2017-1-27_11-13-30.png b/docs/guides/onap-user/vfcreation/media/image2017-1-27_11-13-30.png
new file mode 100644 (file)
index 0000000..7bf32d4
Binary files /dev/null and b/docs/guides/onap-user/vfcreation/media/image2017-1-27_11-13-30.png differ

diff --git a/docs/guides/onap-user/vfcreation/media/image2017-1-27_11-14-3.png b/docs/guides/onap-user/vfcreation/media/image2017-1-27_11-14-3.png
new file mode 100644 (file)
index 0000000..5a8d190
Binary files /dev/null and b/docs/guides/onap-user/vfcreation/media/image2017-1-27_11-14-3.png differ

diff --git a/docs/guides/onap-user/vfcreation/media/image2017-1-27_11-17-18.png b/docs/guides/onap-user/vfcreation/media/image2017-1-27_11-17-18.png
new file mode 100644 (file)
index 0000000..d12ca8f
Binary files /dev/null and b/docs/guides/onap-user/vfcreation/media/image2017-1-27_11-17-18.png differ

diff --git a/docs/guides/onap-user/vfcreation/media/image2017-1-27_11-20-13.png b/docs/guides/onap-user/vfcreation/media/image2017-1-27_11-20-13.png
new file mode 100644 (file)
index 0000000..82392a7
Binary files /dev/null and b/docs/guides/onap-user/vfcreation/media/image2017-1-27_11-20-13.png differ

diff --git a/docs/guides/onap-user/vfcreation/media/image2017-1-27_11-21-4.png b/docs/guides/onap-user/vfcreation/media/image2017-1-27_11-21-4.png
new file mode 100644 (file)
index 0000000..5946643
Binary files /dev/null and b/docs/guides/onap-user/vfcreation/media/image2017-1-27_11-21-4.png differ

diff --git a/docs/guides/onap-user/vfcreation/media/sdc_artifact_update.png b/docs/guides/onap-user/vfcreation/media/sdc_artifact_update.png
new file mode 100644 (file)
index 0000000..266d965
Binary files /dev/null and b/docs/guides/onap-user/vfcreation/media/sdc_artifact_update.png differ

diff --git a/docs/submodules/aaf/authz.git b/docs/submodules/aaf/authz.git
index 096803c..513471c 160000 (submodule)
--- a/docs/submodules/aaf/authz.git
+++ b/docs/submodules/aaf/authz.git
@@ -1 +1 @@
-Subproject commit 096803ce0a8f4a57cc2f78f7d969cab18cb7a93e
+Subproject commit 513471c517baae37437dca2d1af6d2bdb31ab128

diff --git a/docs/submodules/aai/sparky-be.git b/docs/submodules/aai/sparky-be.git
index 1e6ea4b..9fe1f66 160000 (submodule)
--- a/docs/submodules/aai/sparky-be.git
+++ b/docs/submodules/aai/sparky-be.git
@@ -1 +1 @@
-Subproject commit 1e6ea4bd794c8e84dcdb20be7a028bcdedb2dff2
+Subproject commit 9fe1f66fe72cbb008c063dae9d60f377d3dfd410

diff --git a/docs/submodules/appc.git b/docs/submodules/appc.git
index 38a4d51..d1bddab 160000 (submodule)
--- a/docs/submodules/appc.git
+++ b/docs/submodules/appc.git
@@ -1 +1 @@
-Subproject commit 38a4d515a8414e83a3724bccbb5ab83cd50d7df9
+Subproject commit d1bddabef57ab3582d1b1c045c0554d1e476e52e

diff --git a/docs/submodules/appc/deployment.git b/docs/submodules/appc/deployment.git
index cd9e460..7480619 160000 (submodule)
--- a/docs/submodules/appc/deployment.git
+++ b/docs/submodules/appc/deployment.git
@@ -1 +1 @@
-Subproject commit cd9e460cfa7cbd090156045711c4d95efa6765b3
+Subproject commit 7480619227377cade2f2119865a87b41641314c5

diff --git a/docs/submodules/ccsdk/apps.git b/docs/submodules/ccsdk/apps.git
index 79903ae..16a34ae 160000 (submodule)
--- a/docs/submodules/ccsdk/apps.git
+++ b/docs/submodules/ccsdk/apps.git
@@ -1 +1 @@
-Subproject commit 79903ae40b4f23a95b200f2ca045475c9c9becb0
+Subproject commit 16a34aeeebad1775ea4a6675c19f041b273dcdfb

diff --git a/docs/submodules/ccsdk/cds.git b/docs/submodules/ccsdk/cds.git
index f332e6e..f6aba62 160000 (submodule)
--- a/docs/submodules/ccsdk/cds.git
+++ b/docs/submodules/ccsdk/cds.git
@@ -1 +1 @@
-Subproject commit f332e6ecd2c0a9f26451f977c941f03ed8ab84dc
+Subproject commit f6aba62c7ee10eb14e9db2aaf1dc7676ccc130fa

diff --git a/docs/submodules/ccsdk/distribution.git b/docs/submodules/ccsdk/distribution.git
index 6c64ce6..b594a9b 160000 (submodule)
--- a/docs/submodules/ccsdk/distribution.git
+++ b/docs/submodules/ccsdk/distribution.git
@@ -1 +1 @@
-Subproject commit 6c64ce6d8be0d03ddc9d940cc5caeb7000b1f390
+Subproject commit b594a9b61a49ccb3a53be0807fb090da3f606517

diff --git a/docs/submodules/ccsdk/features.git b/docs/submodules/ccsdk/features.git
index 7ab848c..c013cb9 160000 (submodule)
--- a/docs/submodules/ccsdk/features.git
+++ b/docs/submodules/ccsdk/features.git
@@ -1 +1 @@
-Subproject commit 7ab848ccda31cef44d4a817f22f2edd5a3d4a205
+Subproject commit c013cb97ea71ed746d31c5d822d57c5679fe2068

diff --git a/docs/submodules/ccsdk/parent.git b/docs/submodules/ccsdk/parent.git
index 9dcd199..e8e914a 160000 (submodule)
--- a/docs/submodules/ccsdk/parent.git
+++ b/docs/submodules/ccsdk/parent.git
@@ -1 +1 @@
-Subproject commit 9dcd199fa355a3f3cd9e52c0b63aee01988301ed
+Subproject commit e8e914a2d6fbefe2ab403af1ec43f60623edc5f4

diff --git a/docs/submodules/ccsdk/utils.git b/docs/submodules/ccsdk/utils.git
index 1e65a92..950f9e1 160000 (submodule)
--- a/docs/submodules/ccsdk/utils.git
+++ b/docs/submodules/ccsdk/utils.git
@@ -1 +1 @@
-Subproject commit 1e65a92a826ef75e03b33ffceb72d8357ec88cc4
+Subproject commit 950f9e1ca067c45ba74933030ebf715206bb6017

diff --git a/docs/submodules/clamp.git b/docs/submodules/clamp.git
index 7c66285..cc58619 160000 (submodule)
--- a/docs/submodules/clamp.git
+++ b/docs/submodules/clamp.git
@@ -1 +1 @@
-Subproject commit 7c662851d664e394ff197e9968864b53f1853f5b
+Subproject commit cc58619d3f4410f47c0d6fa8ac25e3aa7ca51438

diff --git a/docs/submodules/cli.git b/docs/submodules/cli.git
index 26fc3d0..70d5141 160000 (submodule)
--- a/docs/submodules/cli.git
+++ b/docs/submodules/cli.git
@@ -1 +1 @@
-Subproject commit 26fc3d01a9be64e10cbeb814559fd98fefbd7ba7
+Subproject commit 70d51414231a0d4f6010e40646386e3b740a7e0b

diff --git a/docs/submodules/dcaegen2.git b/docs/submodules/dcaegen2.git
index 09dab76..9f58a5d 160000 (submodule)
--- a/docs/submodules/dcaegen2.git
+++ b/docs/submodules/dcaegen2.git
@@ -1 +1 @@
-Subproject commit 09dab76658142089c222c7ce200cfbbf378080a2
+Subproject commit 9f58a5d51f8945b4813227957edc8e49451c1eca

diff --git a/docs/submodules/dmaap/buscontroller.git b/docs/submodules/dmaap/buscontroller.git
index 0494603..08b4710 160000 (submodule)
--- a/docs/submodules/dmaap/buscontroller.git
+++ b/docs/submodules/dmaap/buscontroller.git
@@ -1 +1 @@
-Subproject commit 0494603a4624d391af8b5a3918555ea7e47ffa10
+Subproject commit 08b47104ed2dfa350fc3e239cb8bfaff932a474a

diff --git a/docs/submodules/dmaap/datarouter.git b/docs/submodules/dmaap/datarouter.git
index e8fb861..bb01fec 160000 (submodule)
--- a/docs/submodules/dmaap/datarouter.git
+++ b/docs/submodules/dmaap/datarouter.git
@@ -1 +1 @@
-Subproject commit e8fb861c8f5c4b14f795f5ee40e7c5f8d2e2c18b
+Subproject commit bb01feceff0527c8f63ad513d85975e5c4e2e52f

diff --git a/docs/submodules/dmaap/dbcapi.git b/docs/submodules/dmaap/dbcapi.git
index 40e1e60..682f196 160000 (submodule)
--- a/docs/submodules/dmaap/dbcapi.git
+++ b/docs/submodules/dmaap/dbcapi.git
@@ -1 +1 @@
-Subproject commit 40e1e60eb8d8cc18d8542dbd7c00f69a9cc3042d
+Subproject commit 682f1965193e672620bc8766fec6bcb2648aa8e5

diff --git a/docs/submodules/dmaap/messagerouter/messageservice.git b/docs/submodules/dmaap/messagerouter/messageservice.git
index c041513..edecb4c 160000 (submodule)
--- a/docs/submodules/dmaap/messagerouter/messageservice.git
+++ b/docs/submodules/dmaap/messagerouter/messageservice.git
@@ -1 +1 @@
-Subproject commit c0415134c3d9bfd028fb2bd98291a95d39dcab16
+Subproject commit edecb4c2e01f0f55e17cf8982dfde0164469c290

diff --git a/docs/submodules/externalapi/nbi.git b/docs/submodules/externalapi/nbi.git
index cbc6e71..4e864e2 160000 (submodule)
--- a/docs/submodules/externalapi/nbi.git
+++ b/docs/submodules/externalapi/nbi.git
@@ -1 +1 @@
-Subproject commit cbc6e71678979c2f5ce9d42df7ea7bc066b1f40d
+Subproject commit 4e864e25383896e6a04d608b86fed31c23b7f3cf

diff --git a/docs/submodules/holmes/engine-management.git b/docs/submodules/holmes/engine-management.git
index 7e8d80c..ca5ee01 160000 (submodule)
--- a/docs/submodules/holmes/engine-management.git
+++ b/docs/submodules/holmes/engine-management.git
@@ -1 +1 @@
-Subproject commit 7e8d80c1c033b636c5816fd5e67c661d7ef0a2b8
+Subproject commit ca5ee016903924350111f39daef36018dd0a065b

diff --git a/docs/submodules/holmes/rule-management.git b/docs/submodules/holmes/rule-management.git
index d296bb5..3c487f8 160000 (submodule)
--- a/docs/submodules/holmes/rule-management.git
+++ b/docs/submodules/holmes/rule-management.git
@@ -1 +1 @@
-Subproject commit d296bb5ab9332c53572af7f479f3501fa964d846
+Subproject commit 3c487f863a32c2fe7399298e071414811e33647a

diff --git a/docs/submodules/integration.git b/docs/submodules/integration.git
index f20a2a5..12750c0 160000 (submodule)
--- a/docs/submodules/integration.git
+++ b/docs/submodules/integration.git
@@ -1 +1 @@
-Subproject commit f20a2a56e8db908749f93a7932aa055dc445e6b3
+Subproject commit 12750c04bc340ac2e4cf4497bc31323f9d1811e7

diff --git a/docs/submodules/modeling/modelspec.git b/docs/submodules/modeling/modelspec.git
index 4c9735f..62dfa44 160000 (submodule)
--- a/docs/submodules/modeling/modelspec.git
+++ b/docs/submodules/modeling/modelspec.git
@@ -1 +1 @@
-Subproject commit 4c9735f80c983573c08c708307e1d03c84140d6a
+Subproject commit 62dfa44900b49551f83b1e215fbf8b7d940f23a9

diff --git a/docs/submodules/msb/swagger-sdk.git b/docs/submodules/msb/swagger-sdk.git
index 617f07b..4cd4787 160000 (submodule)
--- a/docs/submodules/msb/swagger-sdk.git
+++ b/docs/submodules/msb/swagger-sdk.git
@@ -1 +1 @@
-Subproject commit 617f07b4e70b297de558b4e62ed58acc6cf706a1
+Subproject commit 4cd47877f91e4ca261115a8d8411c2f91e7456ce

diff --git a/docs/submodules/multicloud/azure.git b/docs/submodules/multicloud/azure.git
index 2fbd078..78c9d57 160000 (submodule)
--- a/docs/submodules/multicloud/azure.git
+++ b/docs/submodules/multicloud/azure.git
@@ -1 +1 @@
-Subproject commit 2fbd078605c199e49118037747325e833318ef51
+Subproject commit 78c9d578f5e35015cc5746c2275590f43b4127c9

diff --git a/docs/submodules/multicloud/framework.git b/docs/submodules/multicloud/framework.git
index 388ef1f..51d1d3a 160000 (submodule)
--- a/docs/submodules/multicloud/framework.git
+++ b/docs/submodules/multicloud/framework.git
@@ -1 +1 @@
-Subproject commit 388ef1f2943d5fb581cd6533e1fc225a0309df7f
+Subproject commit 51d1d3a0c0009a58f79cc7642a2777833d9c5d5b

diff --git a/docs/submodules/multicloud/k8s.git b/docs/submodules/multicloud/k8s.git
index 63933b0..619ccde 160000 (submodule)
--- a/docs/submodules/multicloud/k8s.git
+++ b/docs/submodules/multicloud/k8s.git
@@ -1 +1 @@
-Subproject commit 63933b0cf304cfdd49fc73278d9c64dcb48f90eb
+Subproject commit 619ccde3c59cdbf5066a667d2bbea465d4a68984

diff --git a/docs/submodules/music.git b/docs/submodules/music.git
index 4c8d63c..9a8b8ae 160000 (submodule)
--- a/docs/submodules/music.git
+++ b/docs/submodules/music.git
@@ -1 +1 @@
-Subproject commit 4c8d63c24acd45a9ae19af0434848c273f470ae2
+Subproject commit 9a8b8ae8d7c8d6931f99def68068f8936a8cc0b3

diff --git a/docs/submodules/oom.git b/docs/submodules/oom.git
index 960c8f4..96080d0 160000 (submodule)
--- a/docs/submodules/oom.git
+++ b/docs/submodules/oom.git
@@ -1 +1 @@
-Subproject commit 960c8f474ac54dabc43fb0864240db2de71b08bb
+Subproject commit 96080d06124ab60ce9642a840e8b9b9ca15b2534

diff --git a/docs/submodules/oom/offline-installer.git b/docs/submodules/oom/offline-installer.git
index e307e97..3dc563b 160000 (submodule)
--- a/docs/submodules/oom/offline-installer.git
+++ b/docs/submodules/oom/offline-installer.git
@@ -1 +1 @@
-Subproject commit e307e97ba9c0163b34d91d55cfca51c63848fd83
+Subproject commit 3dc563b8f1d42daf3e6455b40b63525c37001bad

diff --git a/docs/submodules/optf/cmso.git b/docs/submodules/optf/cmso.git
index 990a583..7e459e2 160000 (submodule)
--- a/docs/submodules/optf/cmso.git
+++ b/docs/submodules/optf/cmso.git
@@ -1 +1 @@
-Subproject commit 990a5833020c8b01f059c7e5f6405c0076eeed05
+Subproject commit 7e459e2f5cdd50e85a3242b9400d561b83647af1

diff --git a/docs/submodules/optf/has.git b/docs/submodules/optf/has.git
index 199e408..2689688 160000 (submodule)
--- a/docs/submodules/optf/has.git
+++ b/docs/submodules/optf/has.git
@@ -1 +1 @@
-Subproject commit 199e4080955b66a4543effa7193e36fa995b072b
+Subproject commit 268968846d94239d800240b3540173f2e5d4d232

diff --git a/docs/submodules/optf/osdf.git b/docs/submodules/optf/osdf.git
index 153223d..e817f0f 160000 (submodule)
--- a/docs/submodules/optf/osdf.git
+++ b/docs/submodules/optf/osdf.git
@@ -1 +1 @@
-Subproject commit 153223d6c985aba266df11243a0c112cb33377e8
+Subproject commit e817f0f5ad80a48fb54407c4be4951b093d2cb39

diff --git a/docs/submodules/policy/apex-pdp.git b/docs/submodules/policy/apex-pdp.git
index ca558cf..62bc4a1 160000 (submodule)
--- a/docs/submodules/policy/apex-pdp.git
+++ b/docs/submodules/policy/apex-pdp.git
@@ -1 +1 @@
-Subproject commit ca558cfb1ea47de081527771af47abb37a8cd964
+Subproject commit 62bc4a162b169971349bce415f97ace15c15eeef

diff --git a/docs/submodules/policy/distribution.git b/docs/submodules/policy/distribution.git
index e0936d1..39bac7e 160000 (submodule)
--- a/docs/submodules/policy/distribution.git
+++ b/docs/submodules/policy/distribution.git
@@ -1 +1 @@
-Subproject commit e0936d1bf5b7241eb1543c762b86bf72951870b3
+Subproject commit 39bac7ed034c56eeb2b19a1b274fab35dbc9818f

diff --git a/docs/submodules/policy/engine.git b/docs/submodules/policy/engine.git
index 52ee4af..cf91564 160000 (submodule)
--- a/docs/submodules/policy/engine.git
+++ b/docs/submodules/policy/engine.git
@@ -1 +1 @@
-Subproject commit 52ee4af3ad37e2e89815ce8c3cc1e9fc1e6db603
+Subproject commit cf915641e6476ff74761dd71601add65a8762e17

diff --git a/docs/submodules/portal.git b/docs/submodules/portal.git
index a543a77..10df99f 160000 (submodule)
--- a/docs/submodules/portal.git
+++ b/docs/submodules/portal.git
@@ -1 +1 @@
-Subproject commit a543a773266e13155d739e00c4b9d4b0d1529abf
+Subproject commit 10df99f8ffc45b03f5557a30eec5bcc307503cc6

diff --git a/docs/submodules/sdc.git b/docs/submodules/sdc.git
index 9142d9c..a39129f 160000 (submodule)
--- a/docs/submodules/sdc.git
+++ b/docs/submodules/sdc.git
@@ -1 +1 @@
-Subproject commit 9142d9cea9f033c798c7f669df05e0f6f5b63205
+Subproject commit a39129f4712805698b596da57459d980a7b4f335

diff --git a/docs/submodules/sdc/sdc-tosca.git b/docs/submodules/sdc/sdc-tosca.git
index 9c48804..c6bdb4e 160000 (submodule)
--- a/docs/submodules/sdc/sdc-tosca.git
+++ b/docs/submodules/sdc/sdc-tosca.git
@@ -1 +1 @@
-Subproject commit 9c48804399cb73b135b3f1c7a321b225635caf2c
+Subproject commit c6bdb4e477d0ad6b146ce811f32fc8356c12a226

diff --git a/docs/submodules/sdnc/oam.git b/docs/submodules/sdnc/oam.git
index 7abc384..7b30b7a 160000 (submodule)
--- a/docs/submodules/sdnc/oam.git
+++ b/docs/submodules/sdnc/oam.git
@@ -1 +1 @@
-Subproject commit 7abc384133b055fa56b8c9f33ff52255b18afbf7
+Subproject commit 7b30b7a2becb47823067526bd8c84af9155ac7a2

diff --git a/docs/submodules/so.git b/docs/submodules/so.git
index b15889d..0502bae 160000 (submodule)
--- a/docs/submodules/so.git
+++ b/docs/submodules/so.git
@@ -1 +1 @@
-Subproject commit b15889d217c97f80a973e5b594dd198ce011c78c
+Subproject commit 0502bae356e44cb381cd7ec0f72c7b2bd6429e87

diff --git a/docs/submodules/so/libs.git b/docs/submodules/so/libs.git
index 25990a8..f9b78e1 160000 (submodule)
--- a/docs/submodules/so/libs.git
+++ b/docs/submodules/so/libs.git
@@ -1 +1 @@
-Subproject commit 25990a8c079094f906414c4583ec7b0dd81b4d37
+Subproject commit f9b78e1d7ca2b64badd8529aa4600250387ddae7

diff --git a/docs/submodules/usecase-ui.git b/docs/submodules/usecase-ui.git
index 8aff6d8..76cafb6 160000 (submodule)
--- a/docs/submodules/usecase-ui.git
+++ b/docs/submodules/usecase-ui.git
@@ -1 +1 @@
-Subproject commit 8aff6d8cbc022cbe4db09cabe096f463aa98b00d
+Subproject commit 76cafb66f1897b971736a9c9bdf2e8f0fd5a9579

diff --git a/docs/submodules/vfc/nfvo/lcm.git b/docs/submodules/vfc/nfvo/lcm.git
index 7da033e..669ef8d 160000 (submodule)
--- a/docs/submodules/vfc/nfvo/lcm.git
+++ b/docs/submodules/vfc/nfvo/lcm.git
@@ -1 +1 @@
-Subproject commit 7da033ea616815244205aa97759ec75bc3326447
+Subproject commit 669ef8d8b4f9b9170d0710bc92ac621fe27fcb81

diff --git a/docs/submodules/vid.git b/docs/submodules/vid.git
index f3b31fe..4b49617 160000 (submodule)
--- a/docs/submodules/vid.git
+++ b/docs/submodules/vid.git
@@ -1 +1 @@
-Subproject commit f3b31fe846630953923844ed3ab7defea9ac4447
+Subproject commit 4b49617c80ada42ee41f3eb118898f7872f794e8

diff --git a/docs/submodules/vnfrqts/requirements.git b/docs/submodules/vnfrqts/requirements.git
index 6d4989f..09bbd2f 160000 (submodule)
--- a/docs/submodules/vnfrqts/requirements.git
+++ b/docs/submodules/vnfrqts/requirements.git
@@ -1 +1 @@
-Subproject commit 6d4989f57ed7a5e51a7289798522e384dca1f678
+Subproject commit 09bbd2f9f5cdcf84b18ff1be53caec852f331246

diff --git a/docs/validwords.txt b/docs/validwords.txt
index ea1daa9..c860d4a 100644 (file)
--- a/docs/validwords.txt
+++ b/docs/validwords.txt
@@ -126,7 +126,7 @@ javascript
 Javascript
 jboss
 JBoss
-Jenkin
+Jenkins
 Jira
 jpath
 json
@@ -297,7 +297,7 @@ SDN
 sdnc
 Sdnc
 SDNC
-Seleniunm
+Selenium
 servlet
 Servlet
 Skynet