From cbb9954bb32cdd161ea39d8fd81bd5c93981d504 Mon Sep 17 00:00:00 2001 From: yangyan Date: Tue, 27 Mar 2018 16:18:43 +0800 Subject: Improve VF-C documnent Issue-ID: VFC-828 Change-Id: Ibddfb5bf709567e8060c8c3363c1cb8d76920d98 Signed-off-by: yangyan --- docs/platform/delivery.rst | 44 ++++++++++++++++++++++++++++++++++---------- 1 file changed, 34 insertions(+), 10 deletions(-) (limited to 'docs/platform/delivery.rst') diff --git a/docs/platform/delivery.rst b/docs/platform/delivery.rst index 13d1e0f8..5f717146 100644 --- a/docs/platform/delivery.rst +++ b/docs/platform/delivery.rst @@ -6,23 +6,21 @@ VF-C includes the following components in R1. .. |image0| image:: components.png :width: 5.97047in - :height: 5.63208in + :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 include two micro service, one is workflow manage service and the other is workflow-activiti engine service, this two service will onboard workflow to workflow engine and parse workflow. +* 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 service, 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 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 Resource manager, it will communicate with NS lifecycle manager to update instance data to A&AI. -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. +* 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 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 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: @@ -44,4 +42,30 @@ GVNFM - vfc-gvnfm-vnfres Workflow - workflow-engine-mgr-service - - activiti-extension \ No newline at end of file + - activiti-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 \ No newline at end of file -- cgit 1.2.3-korg