From fa9f2c21530f9fe15b008d08187653ba23a3be32 Mon Sep 17 00:00:00 2001 From: Eric Debeau Date: Wed, 18 Oct 2017 15:00:47 +0000 Subject: [PATCH] Change OpenO by ONAP and minor corrections Change-Id: I0d0280d8da50f5dbb28820ed364c0facbff267f4 Issue-ID: DOC-103 Signed-off-by: Eric Debeau --- docs/Chapter5.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/Chapter5.rst b/docs/Chapter5.rst index 1d20c94..bac1786 100644 --- a/docs/Chapter5.rst +++ b/docs/Chapter5.rst @@ -5113,11 +5113,11 @@ the VNF vendor self. d. Create SVNFM Adaptor Mircoservice ======================================= -Some vnfs are managed by special vnfm, before add svnfm to ONAP, a -svnfm adaptor must be added to openo to adapter the interface of nfvo -and svnfm. +Some vnfs are managed by special VNFM, before add SVNFM to ONAP, a +SVNFM adaptor must be added to ONAP to adapter the interface of NFVO +and SVNFM. -A svnfm adaptor is a micro service with unique name and an appointed +A SVNFM adaptor is a micro service with unique name and an appointed port, when started up, it must be auto registered to MSB(Micro server bus),following describes an example rest of register to MSB: -- 2.16.6