From 351e1f2a3a33d9348776cd8e1e45eb90e0276992 Mon Sep 17 00:00:00 2001 From: hp1256 Date: Thu, 12 Oct 2017 11:51:16 -0700 Subject: VNFRQTS -Requirements fixed outline VNFRQTS -Requirements fixed outline for chapter 5 Change-Id: I8ec38a4e87137e92c5dfe464bf28714323035972 Issue-ID:VNFRQTS-111 Signed-off-by: hp1256 --- docs/Chapter5.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs') diff --git a/docs/Chapter5.rst b/docs/Chapter5.rst index 2d8952b..4c2490e 100644 --- a/docs/Chapter5.rst +++ b/docs/Chapter5.rst @@ -5093,7 +5093,7 @@ to the Heat template. *Note:* It is important to follow this convention to the extent possible even in the short-term as of the long-term direction. -d. VNFM Driver Develop Steps +c. VNFM Driver Develop Steps ============================== Aid to help the VNF vendor to fasten the integration with the NFVO via @@ -5110,7 +5110,7 @@ SVNFM. The interface of NFVO is aligned to the ETSI IFA interfaces and can be gotten in the charter 5.5. The interface of SVNFM is provided by the VNF vendor self. -e. Create SVNFM Adaptor Mircoservice +d. Create SVNFM Adaptor Mircoservice ======================================= Some vnfs are managed by special vnfm, before add svnfm to openo, a -- cgit 1.2.3-korg