diff options
author | 2017-10-17 02:33:16 +0000 | |
---|---|---|
committer | 2017-10-17 02:33:16 +0000 | |
commit | f185becda05c00139cc4b1daea19c21b8401169e (patch) | |
tree | 43a9d2948bde2902fdacb69a020dc493d58615d2 /docs/delivery.rst | |
parent | ff647e1bf572372f7eaf999ddafd0293339dbcee (diff) | |
parent | 5544dbc5d4e49f55fa41bc008a02e1bff2f7ed1b (diff) |
Merge "Update vfc doc"
Diffstat (limited to 'docs/delivery.rst')
-rw-r--r-- | docs/delivery.rst | 14 |
1 files changed, 14 insertions, 0 deletions
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 |