Merge ""Pre-Onboarding" section converted from ONAP Wiki (html) to ONAP RTD (rst...
authorEric Debeau <eric.debeau@orange.com>
Thu, 2 May 2019 14:52:47 +0000 (14:52 +0000)
committerGerrit Code Review <gerrit@onap.org>
Thu, 2 May 2019 14:52:47 +0000 (14:52 +0000)
55 files changed:
docs/guides/onap-user/service-distribution/index.rst [new file with mode: 0644]
docs/guides/onap-user/service-distribution/media/design_governance_workflow.png [new file with mode: 0644]
docs/guides/onap-user/vfcreation/index.rst [new file with mode: 0644]
docs/guides/onap-user/vfcreation/media/design_vf_updatevspmessage.png [new file with mode: 0644]
docs/guides/onap-user/vfcreation/media/design_vf_workflow.png [new file with mode: 0644]
docs/guides/onap-user/vfcreation/media/image2017-1-27_11-13-30.png [new file with mode: 0644]
docs/guides/onap-user/vfcreation/media/image2017-1-27_11-14-3.png [new file with mode: 0644]
docs/guides/onap-user/vfcreation/media/image2017-1-27_11-17-18.png [new file with mode: 0644]
docs/guides/onap-user/vfcreation/media/image2017-1-27_11-20-13.png [new file with mode: 0644]
docs/guides/onap-user/vfcreation/media/image2017-1-27_11-21-4.png [new file with mode: 0644]
docs/guides/onap-user/vfcreation/media/sdc_artifact_update.png [new file with mode: 0644]
docs/submodules/aaf/authz.git
docs/submodules/aai/sparky-be.git
docs/submodules/appc.git
docs/submodules/appc/deployment.git
docs/submodules/ccsdk/apps.git
docs/submodules/ccsdk/cds.git
docs/submodules/ccsdk/distribution.git
docs/submodules/ccsdk/features.git
docs/submodules/ccsdk/parent.git
docs/submodules/ccsdk/utils.git
docs/submodules/clamp.git
docs/submodules/cli.git
docs/submodules/dcaegen2.git
docs/submodules/dmaap/buscontroller.git
docs/submodules/dmaap/datarouter.git
docs/submodules/dmaap/dbcapi.git
docs/submodules/dmaap/messagerouter/messageservice.git
docs/submodules/externalapi/nbi.git
docs/submodules/holmes/engine-management.git
docs/submodules/holmes/rule-management.git
docs/submodules/integration.git
docs/submodules/modeling/modelspec.git
docs/submodules/msb/swagger-sdk.git
docs/submodules/multicloud/azure.git
docs/submodules/multicloud/framework.git
docs/submodules/multicloud/k8s.git
docs/submodules/music.git
docs/submodules/oom.git
docs/submodules/oom/offline-installer.git
docs/submodules/optf/cmso.git
docs/submodules/optf/has.git
docs/submodules/optf/osdf.git
docs/submodules/policy/apex-pdp.git
docs/submodules/policy/engine.git
docs/submodules/portal.git
docs/submodules/sdc.git
docs/submodules/sdc/sdc-tosca.git
docs/submodules/sdnc/oam.git
docs/submodules/so.git
docs/submodules/so/libs.git
docs/submodules/usecase-ui.git
docs/submodules/vfc/nfvo/lcm.git
docs/submodules/vid.git
docs/submodules/vnfrqts/requirements.git

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
@@ -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
@@ -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
index 096803c..513471c 160000 (submodule)
@@ -1 +1 @@
-Subproject commit 096803ce0a8f4a57cc2f78f7d969cab18cb7a93e
+Subproject commit 513471c517baae37437dca2d1af6d2bdb31ab128
index 1e6ea4b..9fe1f66 160000 (submodule)
@@ -1 +1 @@
-Subproject commit 1e6ea4bd794c8e84dcdb20be7a028bcdedb2dff2
+Subproject commit 9fe1f66fe72cbb008c063dae9d60f377d3dfd410
index 38a4d51..d1bddab 160000 (submodule)
@@ -1 +1 @@
-Subproject commit 38a4d515a8414e83a3724bccbb5ab83cd50d7df9
+Subproject commit d1bddabef57ab3582d1b1c045c0554d1e476e52e
index cd9e460..7480619 160000 (submodule)
@@ -1 +1 @@
-Subproject commit cd9e460cfa7cbd090156045711c4d95efa6765b3
+Subproject commit 7480619227377cade2f2119865a87b41641314c5
index 79903ae..16a34ae 160000 (submodule)
@@ -1 +1 @@
-Subproject commit 79903ae40b4f23a95b200f2ca045475c9c9becb0
+Subproject commit 16a34aeeebad1775ea4a6675c19f041b273dcdfb
index f2136a4..f6aba62 160000 (submodule)
@@ -1 +1 @@
-Subproject commit f2136a47fd53fcbdc117899c6e134d7ceea46d85
+Subproject commit f6aba62c7ee10eb14e9db2aaf1dc7676ccc130fa
index c6e85bc..b594a9b 160000 (submodule)
@@ -1 +1 @@
-Subproject commit c6e85bc88f2dd3427360523270c7ed92c12abdc6
+Subproject commit b594a9b61a49ccb3a53be0807fb090da3f606517
index 7ab848c..c013cb9 160000 (submodule)
@@ -1 +1 @@
-Subproject commit 7ab848ccda31cef44d4a817f22f2edd5a3d4a205
+Subproject commit c013cb97ea71ed746d31c5d822d57c5679fe2068
index 9dcd199..e8e914a 160000 (submodule)
@@ -1 +1 @@
-Subproject commit 9dcd199fa355a3f3cd9e52c0b63aee01988301ed
+Subproject commit e8e914a2d6fbefe2ab403af1ec43f60623edc5f4
index 1e65a92..950f9e1 160000 (submodule)
@@ -1 +1 @@
-Subproject commit 1e65a92a826ef75e03b33ffceb72d8357ec88cc4
+Subproject commit 950f9e1ca067c45ba74933030ebf715206bb6017
index a1ec959..cc58619 160000 (submodule)
@@ -1 +1 @@
-Subproject commit a1ec959e3f5f8639117a5134ffbfb59f7b542f80
+Subproject commit cc58619d3f4410f47c0d6fa8ac25e3aa7ca51438
index 26fc3d0..70d5141 160000 (submodule)
@@ -1 +1 @@
-Subproject commit 26fc3d01a9be64e10cbeb814559fd98fefbd7ba7
+Subproject commit 70d51414231a0d4f6010e40646386e3b740a7e0b
index 701110b..9f58a5d 160000 (submodule)
@@ -1 +1 @@
-Subproject commit 701110ba1719151a20393ced327e4e935d991ad9
+Subproject commit 9f58a5d51f8945b4813227957edc8e49451c1eca
index 0494603..08b4710 160000 (submodule)
@@ -1 +1 @@
-Subproject commit 0494603a4624d391af8b5a3918555ea7e47ffa10
+Subproject commit 08b47104ed2dfa350fc3e239cb8bfaff932a474a
index bceb18d..bb01fec 160000 (submodule)
@@ -1 +1 @@
-Subproject commit bceb18df30982e2ace538baf5c49336fe0e45b0a
+Subproject commit bb01feceff0527c8f63ad513d85975e5c4e2e52f
index 40e1e60..682f196 160000 (submodule)
@@ -1 +1 @@
-Subproject commit 40e1e60eb8d8cc18d8542dbd7c00f69a9cc3042d
+Subproject commit 682f1965193e672620bc8766fec6bcb2648aa8e5
index c041513..edecb4c 160000 (submodule)
@@ -1 +1 @@
-Subproject commit c0415134c3d9bfd028fb2bd98291a95d39dcab16
+Subproject commit edecb4c2e01f0f55e17cf8982dfde0164469c290
index 0095af5..4e864e2 160000 (submodule)
@@ -1 +1 @@
-Subproject commit 0095af54a51619546e6ab9783adff625b696f4e0
+Subproject commit 4e864e25383896e6a04d608b86fed31c23b7f3cf
index f99ee48..ca5ee01 160000 (submodule)
@@ -1 +1 @@
-Subproject commit f99ee485e1973ab462d8a0ccd86e2240109d85d7
+Subproject commit ca5ee016903924350111f39daef36018dd0a065b
index e19a111..3c487f8 160000 (submodule)
@@ -1 +1 @@
-Subproject commit e19a1115bb056b002b42c7b15afa0226877c7f46
+Subproject commit 3c487f863a32c2fe7399298e071414811e33647a
index 6eaaedc..12750c0 160000 (submodule)
@@ -1 +1 @@
-Subproject commit 6eaaedc4d320b4e032beb958123ee00f5cf9a7a1
+Subproject commit 12750c04bc340ac2e4cf4497bc31323f9d1811e7
index 4c9735f..62dfa44 160000 (submodule)
@@ -1 +1 @@
-Subproject commit 4c9735f80c983573c08c708307e1d03c84140d6a
+Subproject commit 62dfa44900b49551f83b1e215fbf8b7d940f23a9
index 617f07b..4cd4787 160000 (submodule)
@@ -1 +1 @@
-Subproject commit 617f07b4e70b297de558b4e62ed58acc6cf706a1
+Subproject commit 4cd47877f91e4ca261115a8d8411c2f91e7456ce
index 2fbd078..78c9d57 160000 (submodule)
@@ -1 +1 @@
-Subproject commit 2fbd078605c199e49118037747325e833318ef51
+Subproject commit 78c9d578f5e35015cc5746c2275590f43b4127c9
index 388ef1f..51d1d3a 160000 (submodule)
@@ -1 +1 @@
-Subproject commit 388ef1f2943d5fb581cd6533e1fc225a0309df7f
+Subproject commit 51d1d3a0c0009a58f79cc7642a2777833d9c5d5b
index 63933b0..619ccde 160000 (submodule)
@@ -1 +1 @@
-Subproject commit 63933b0cf304cfdd49fc73278d9c64dcb48f90eb
+Subproject commit 619ccde3c59cdbf5066a667d2bbea465d4a68984
index 4c8d63c..9a8b8ae 160000 (submodule)
@@ -1 +1 @@
-Subproject commit 4c8d63c24acd45a9ae19af0434848c273f470ae2
+Subproject commit 9a8b8ae8d7c8d6931f99def68068f8936a8cc0b3
index 99b4523..96080d0 160000 (submodule)
@@ -1 +1 @@
-Subproject commit 99b4523cfe191ab8d1f0d82bb68ab1605f881dab
+Subproject commit 96080d06124ab60ce9642a840e8b9b9ca15b2534
index 8cbef61..3dc563b 160000 (submodule)
@@ -1 +1 @@
-Subproject commit 8cbef61dee77ba2a77120b9b512e4e6971fa2af9
+Subproject commit 3dc563b8f1d42daf3e6455b40b63525c37001bad
index d4014ab..7e459e2 160000 (submodule)
@@ -1 +1 @@
-Subproject commit d4014abb85d839c14c9a2572098571e7a8523104
+Subproject commit 7e459e2f5cdd50e85a3242b9400d561b83647af1
index d6be402..2689688 160000 (submodule)
@@ -1 +1 @@
-Subproject commit d6be402c0765aee388bc5dc64882696a0a23be22
+Subproject commit 268968846d94239d800240b3540173f2e5d4d232
index 0a358ab..e817f0f 160000 (submodule)
@@ -1 +1 @@
-Subproject commit 0a358ab8f3f546f11c36f913018edef63ff17ed3
+Subproject commit e817f0f5ad80a48fb54407c4be4951b093d2cb39
index ca558cf..62bc4a1 160000 (submodule)
@@ -1 +1 @@
-Subproject commit ca558cfb1ea47de081527771af47abb37a8cd964
+Subproject commit 62bc4a162b169971349bce415f97ace15c15eeef
index b38e59b..cf91564 160000 (submodule)
@@ -1 +1 @@
-Subproject commit b38e59b1f797b15d0a3e1170e43a0db92216bbd0
+Subproject commit cf915641e6476ff74761dd71601add65a8762e17
index a543a77..10df99f 160000 (submodule)
@@ -1 +1 @@
-Subproject commit a543a773266e13155d739e00c4b9d4b0d1529abf
+Subproject commit 10df99f8ffc45b03f5557a30eec5bcc307503cc6
index 9142d9c..a39129f 160000 (submodule)
@@ -1 +1 @@
-Subproject commit 9142d9cea9f033c798c7f669df05e0f6f5b63205
+Subproject commit a39129f4712805698b596da57459d980a7b4f335
index 9c48804..c6bdb4e 160000 (submodule)
@@ -1 +1 @@
-Subproject commit 9c48804399cb73b135b3f1c7a321b225635caf2c
+Subproject commit c6bdb4e477d0ad6b146ce811f32fc8356c12a226
index 797f233..7b30b7a 160000 (submodule)
@@ -1 +1 @@
-Subproject commit 797f2333a91eb3de6fdbc8260e02f39e6b99e802
+Subproject commit 7b30b7a2becb47823067526bd8c84af9155ac7a2
index 9a1a01d..0502bae 160000 (submodule)
@@ -1 +1 @@
-Subproject commit 9a1a01dd07e5a64422bca75fa22ea36daa1d88d1
+Subproject commit 0502bae356e44cb381cd7ec0f72c7b2bd6429e87
index 25990a8..f9b78e1 160000 (submodule)
@@ -1 +1 @@
-Subproject commit 25990a8c079094f906414c4583ec7b0dd81b4d37
+Subproject commit f9b78e1d7ca2b64badd8529aa4600250387ddae7
index 8aff6d8..76cafb6 160000 (submodule)
@@ -1 +1 @@
-Subproject commit 8aff6d8cbc022cbe4db09cabe096f463aa98b00d
+Subproject commit 76cafb66f1897b971736a9c9bdf2e8f0fd5a9579
index 22631f1..669ef8d 160000 (submodule)
@@ -1 +1 @@
-Subproject commit 22631f12c6029a38be6cb3acdc21e6f8f6400f6c
+Subproject commit 669ef8d8b4f9b9170d0710bc92ac621fe27fcb81
index f3b31fe..4b49617 160000 (submodule)
@@ -1 +1 @@
-Subproject commit f3b31fe846630953923844ed3ab7defea9ac4447
+Subproject commit 4b49617c80ada42ee41f3eb118898f7872f794e8
index 3422870..09bbd2f 160000 (submodule)
@@ -1 +1 @@
-Subproject commit 3422870a179cdeed4df9631faa08357d28da5c7a
+Subproject commit 09bbd2f9f5cdcf84b18ff1be53caec852f331246