From ad8793f9b4a4de8fe8aa37c80d6746403631528f Mon Sep 17 00:00:00 2001 From: yangyan Date: Wed, 1 Nov 2017 12:20:49 +0800 Subject: Update VF-C doc Add VF-C release note Update VF-C component installation document Issue-ID: VFC-574 Change-Id: I8d422e341d785c8d817e53ad5a24412e50933a64 Signed-off-by: yangyan --- docs/delivery.rst | 27 --------------------------- 1 file changed, 27 deletions(-) delete mode 100644 docs/delivery.rst (limited to 'docs/delivery.rst') diff --git a/docs/delivery.rst b/docs/delivery.rst deleted file mode 100644 index 1a6ab3b4..00000000 --- a/docs/delivery.rst +++ /dev/null @@ -1,27 +0,0 @@ -VF-C Delivery -------------- -VF-C includs the following components in R1. - -|image0| - -.. |image0| image:: components.png - :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 - - -- cgit 1.2.3-korg