Update vfc doc

[vfc/nfvo/lcm.git] / docs / platform / delivery.rst

diff --git a/docs/platform/delivery.rst b/docs/platform/delivery.rst
index 1a6ab3b..3b86454 100644 (file)
--- a/docs/platform/delivery.rst
+++ b/docs/platform/delivery.rst
@@ -1,27 +1,71 @@
 VF-C Delivery
 -------------
-VF-C includs the following components in R1.
+VF-C includes the following components in R1.
 
 |image0|
 
 .. |image0| image:: components.png
    :width: 5.97047in
-   :height: 5.63208in
-   
-VF-C incloudes several components in ONAP R1.
+   :height: 4.63208in
+
+VF-C includes several components in ONAP R1.
+
+
 
-Catalog is used to store the package distributed by SDC, it is a runtime catalog.
+* Workflow includes two micro service: workflow manage service and workflow-activity engine service, this two services will onboard workflow to workflow engine and parse workflow.
 
-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 Lifecycle 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 instance data to A&AI.
 
-For NS lifecyle manager,it mainly completes the NS lifecycle management,such as NS Instantiation/termination and auto-healing.
+* In VF-C southbound, it includes 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 Resource manager, it will communicate with NS lifecycle manager to update intance date to A&AI.
+* 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
 
-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
+For the Amsterdam release, VF-C includes the following components:
 
+NFVO
+ - vfc-nfvo-lcm
+ - vfc-nfvo-catalog
+ - vfc-nfvo-resmgr
+ - vfc-nfvo-driver-emsdriver
+ - vfc-nfvo-driver-gvnfm-gvnfmadapter
+ - vfc-nfvo-driver-gvnfm-jujudriver
+ - vfc-nfvo-driver-svnfm-ztedriver
+ - vfc-nfvo-driver-svnfm-huaweidriver
+ - vfc-nfvo-driver-svnfm-nokiadriver
+ - vfc-nfvo-driver-sfc-ztesfcdriver
+GVNFM
+ - vfc-gvnfm-vnflcm
+ - vfc-gvnfm-vnfmgr
+ - vfc-gvnfm-vnfres
+Workflow
+ - workflow-engine-mgr-service
+ - activity-extension
+ 
+VF-C support VolTE use case in R1 and R2, following are the vVoLTE releated Workflow in VF-C.
+
+* VoLTE Use Case Instantiation In VF-C
+
+|image1|
+
+.. |image1| image:: Instantiation.png
+   :width: 5.97047in
+   :height: 5.63208in
 
+* VoLTE Use Case Termination in VF-C
+
+|image2|
+
+.. |image2| image:: Termination.png
+   :width: 5.97047in
+   :height: 5.63208in
+   
+* VoLTE Use Case Auto-healing in VF-C
+
+|image3|
+
+.. |image3| image:: Auto-healing.png
+   :width: 5.97047in
+   :height: 5.63208in