diff options
| -rw-r--r-- | docs/APIs/NSLCM_API/NSLCM_API_Specification_v0.1.rst | 12 | ||||
| -rw-r--r-- | docs/architecture.rst | 11 | ||||
| -rw-r--r-- | docs/delivery.rst | 14 | ||||
| -rw-r--r-- | docs/installation.rst | 2 |
4 files changed, 36 insertions, 3 deletions
diff --git a/docs/APIs/NSLCM_API/NSLCM_API_Specification_v0.1.rst b/docs/APIs/NSLCM_API/NSLCM_API_Specification_v0.1.rst index ff9e621a..bada11e7 100644 --- a/docs/APIs/NSLCM_API/NSLCM_API_Specification_v0.1.rst +++ b/docs/APIs/NSLCM_API/NSLCM_API_Specification_v0.1.rst @@ -566,19 +566,31 @@ NS LCM API "type": "object",
"properties": {
+
"context":{
+
"type": "object",
+
"properties": {
+
"globalCustomerId":{
+
"type": "string",
"description": "the global customer id"
+
},
+
"serviceType":{
"type": "string",
+
"description": "service type"
+
}
+
}
+
},
+
"csarId": {
"type": "string",
diff --git a/docs/architecture.rst b/docs/architecture.rst index 20ac2118..dc7ef09b 100644 --- a/docs/architecture.rst +++ b/docs/architecture.rst @@ -13,6 +13,13 @@ Following is the VF-C architecture. :width: 5.97047in :height: 5.63208in -VF-C includes two components: NFVO and GVNFM + +VF-C as one controller in ONAP includes two components NFV-O and GVNFM. + +For NFV-O, it provides north bound interface to SO to take part in fulfilling the orchestration and operation of end2end service.and provides standard south bound interface to VNFMs. -VF-C has many dependencies with other projects,such as SO,Policy,A&AI,SDC,DCAE,Multi-cloud and so on.
\ No newline at end of file +For GVNFM, it provides LCM for VNFs which do not require a vendor VNFM and works with NFV-O component to take part in fulfilling the LCM of NS. + +In addition, VF-C provides interface to Policy and works with DCAE for Close Loop Automation. + +As you can see in this picture,VF-C has many dependencies with other projects,such as SO,Policy,A&AI,SDC,DCAE,Multi-cloud and so on.
\ No newline at end of file diff --git a/docs/delivery.rst b/docs/delivery.rst index 9fa6fa81..1a6ab3b4 100644 --- a/docs/delivery.rst +++ b/docs/delivery.rst @@ -8,6 +8,20 @@ VF-C includs the following components in R1. :width: 5.97047in :height: 5.63208in +VF-C incloudes several components in ONAP R1. +Catalog is used to store the package distributed by SDC, it is a runtime catalog. + +Workflow include two micro service, one is workflow manage service and the other is workflow-activiti engine serivce, this two service will onboard workflow to workflow engine and parse workflow. + + +For NS lifecyle manager,it mainly completes the NS lifecycle management,such as NS Instantiation/termination and auto-healing. + +For Resource manager, it will communicate with NS lifecycle manager to update intance date to A&AI. + +In VF-C southbound, it includs Gvnfmdriver and SVNFM driver which will interact with GVNFM and Vendor VNFM respectively to execute VNF lifecycle management, +VF-C provides vnfm driver northbound api,then Vendor can implement this APIs to integrate with VF-C. + +For the EMS driver,it can collect VNF lay’s Fcaps data from Vendor EMS, and then translate and put these data to DCAE Vescollector diff --git a/docs/installation.rst b/docs/installation.rst index c72c77a5..66fd2fce 100644 --- a/docs/installation.rst +++ b/docs/installation.rst @@ -126,7 +126,7 @@ For testing, we can use curl command to access the swagger api. :: - curl http://${MSB_IP}:80/api/emsdriver/v1/swagger + curl http://${MSB_IP}:80/api/emsdriver/v1/swagger.json - Install vfc-gvnfm components. |