From a4e0df11ff98a3a1b821f619e040506e3c3a33ed Mon Sep 17 00:00:00 2001 From: "Bozawglanian, Hagop (hb755d)" Date: Fri, 27 Jul 2018 19:16:26 +0000 Subject: VNFRQTS - Correcting initial release info Removing references to initial release of ONAP from Open-O and OpenECOMP. Change-Id: I749cfdf449d243720d47314525dd94a9fded16e1 Issue-ID: VNFRQTS-280 Signed-off-by: Bozawglanian, Hagop (hb755d) --- docs/Chapter4/Design.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/Chapter4/Design.rst') diff --git a/docs/Chapter4/Design.rst b/docs/Chapter4/Design.rst index 35acd65..70f5598 100644 --- a/docs/Chapter4/Design.rst +++ b/docs/Chapter4/Design.rst @@ -20,7 +20,7 @@ grouping functions in a common cloud data center to minimize inter-component latency. The VNFs should be designed with a goal of being modular and reusable to enable using best-in-breed vendors. -Section 5.a VNF Design in *VNF Guidelines* describes +Section 4.1 VNF Design in *VNF Guidelines* describes the overall guidelines for designing VNFs from VNF Components (VNFCs). Below are more detailed requirements for composing VNFs. -- cgit 1.2.3-korg