diff options
| author |   anjali.walsatwar <anjali.walsatwar@huawei.com> | 2019-08-08 15:41:13 +0530 |
|---|---|---|
| committer | anjali.walsatwar <anjali.walsatwar@huawei.com> | 2019-08-08 15:41:13 +0530 |
| commit | 996ed61b0b86fb647d9f7ebd0eb5b0fdd8d210ab (patch) | |
| tree | 3ae0fe201e267dc0ad462f0609d05ba0549e13e8 /docs/platform | |
| parent | ad03c97345c2be37ff0b8a0ed38883307d88c1b5 (diff) | |
fix for delivery
documents have different spelling mistakes and grammatical issues
Issue-ID: VFC-1483
Signed-off-by: anjali.walsatwar <anjali.walsatwar@huawei.com>
Change-Id: I85311d661f9c418df34f60b02289b9f89ca59a2b
Diffstat (limited to 'docs/platform')
| -rw-r--r-- | docs/platform/delivery.rst | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/platform/delivery.rst b/docs/platform/delivery.rst index 5f717146..cd4e9755 100644 --- a/docs/platform/delivery.rst +++ b/docs/platform/delivery.rst @@ -12,13 +12,13 @@ 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. +* 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. -* 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. -* 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 @@ -42,7 +42,7 @@ GVNFM - vfc-gvnfm-vnfres Workflow - workflow-engine-mgr-service - - activiti-extension + - activity-extension VF-C support VolTE use case in R1 and R2, following are the vVoLTE releated Workflow in VF-C. @@ -68,4 +68,4 @@ VF-C support VolTE use case in R1 and R2, following are the vVoLTE releated Work .. |image3| image:: Auto-healing.png :width: 5.97047in - :height: 5.63208in
\ No newline at end of file + :height: 5.63208in |