"type": "object",\r
\r
"properties": {\r
+\r
"context":{\r
+\r
"type": "object",\r
+\r
"properties": {\r
+\r
"globalCustomerId":{\r
+\r
"type": "string",\r
"description": "the global customer id"\r
+\r
},\r
+\r
"serviceType":{\r
"type": "string",\r
+\r
"description": "service type"\r
+\r
}\r
+\r
}\r
+\r
},\r
+\r
"csarId": {\r
\r
"type": "string",\r
: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
: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
::
- curl http://${MSB_IP}:80/api/emsdriver/v1/swagger
+ curl http://${MSB_IP}:80/api/emsdriver/v1/swagger.json
- Install vfc-gvnfm components.