diff options
author | subhash kumar singh <subhash.kumar.singh@huawei.com> | 2017-12-29 11:02:25 +0000 |
---|---|---|
committer | subhash kumar singh <subhash.kumar.singh@huawei.com> | 2017-12-29 11:12:02 +0000 |
commit | aaf22fefe1a892080d11bcb2916524676a18dcbd (patch) | |
tree | b408e4358ebbcbb4cab19c7b0a75be380c064bca /docs | |
parent | 45379424cdd43443dcad1659a4858cf8cb48d02b (diff) |
Fix typo in documentation
Fix typos in documentation.
Change-Id: I8b53c224821343e9e2fe4663127f7abd1a1f7b54
Issue-ID: VFC-629
Signed-off-by: subhash kumar singh <subhash.kumar.singh@huawei.com>
Diffstat (limited to 'docs')
-rw-r--r-- | docs/platform/delivery.rst | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/docs/platform/delivery.rst b/docs/platform/delivery.rst index 9622789d..13d1e0f8 100644 --- a/docs/platform/delivery.rst +++ b/docs/platform/delivery.rst @@ -1,31 +1,31 @@ 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. + +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 serivce, this two service 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 service, 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 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 intance date 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 includs Gvnfmdriver and SVNFM driver which will interact with GVNFM and Vendor VNFM respectively to execute VNF lifecycle management, +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 Amsterdan release, VF-C includes the following components: +For the Amsterdam release, VF-C includes the following components: NFVO - vfc-nfvo-lcm |