From 74fa7b13a32e948fd5dc7f1706e2c2f209c65d8b Mon Sep 17 00:00:00 2001 From: yangyan Date: Tue, 20 Mar 2018 11:20:43 +0800 Subject: Improve VF-C documentation Issue-ID: VFC-828 Change-Id: Iec104860b92b81784863cccd89c85416b8f9cdb2 Signed-off-by: yangyan --- docs/platform/index.rst | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) (limited to 'docs/platform/index.rst') diff --git a/docs/platform/index.rst b/docs/platform/index.rst index 12fa0be0..364a4c94 100644 --- a/docs/platform/index.rst +++ b/docs/platform/index.rst @@ -15,6 +15,30 @@ As part of the integration between OpenECOMP and OPEN-O, VF-C leverages ETSI NFV * support microservice architecture and model driven resource orchestration and management +|image0| + +.. |image0| image:: vfc-component.png + :width: 3.97047in + :height: 2.63208in + +VF-C as one controller in ONAP includes two components NFV-O and GVNFM. + +* NFVO component + + * compliant with ETSI NFV MANO architecture and information model, + * providing resource orchestration and full life cycle management and FCAPS for NS, + * providing standard south bound interface to VNFMs, + * providing north bound interface to SO, to take part in fulfilling the orchestraion and operation of end2end service, + * providing interface and work with DCAE and Policy for Close Loop Automation. + +* GVNFM component + + * compliant with ETSI NFV MANO architecture and information model + * providing full life cycle management and FCAPS for VNFs which do not require a vendor VNFM, + * providing interface and work with NFV-O component, to take part in fulfiiling the LCM and FCAPS management of NS, + * providing interface and work with DCAE and Policy for Close Loop Automation. + + .. toctree:: :maxdepth: 1 -- cgit 1.2.3-korg