From d1406d59efe349a65274f298bf9c77914ee55d10 Mon Sep 17 00:00:00 2001 From: JunfengWang Date: Tue, 29 Sep 2020 10:55:03 -0400 Subject: Correction of section 7.2.7 for general description Issue-ID: VNFRQTS-932 Signed-off-by: JunfengWang Change-Id: I3ed91648b3782bf43234740f98e18b06a5146cf1 --- docs/Chapter7/VNF-On-boarding-and-package-management.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs') diff --git a/docs/Chapter7/VNF-On-boarding-and-package-management.rst b/docs/Chapter7/VNF-On-boarding-and-package-management.rst index 2d4d07c..48f9dd1 100755 --- a/docs/Chapter7/VNF-On-boarding-and-package-management.rst +++ b/docs/Chapter7/VNF-On-boarding-and-package-management.rst @@ -555,9 +555,9 @@ Testing Licensing Requirements ^^^^^^^^^^^^^^^^^^^^^^ -ONAP can support external licensing management solution (e.g. vendor specific) -in addition to its own licensing management solution. If licensing management -solution is provided by ONAP, then ONAP operators build the VNF License using SDC during onboarding. +ONAP can support external licensing management solutions. For example, a vendor-specific solution where +the VNF or PNF obtains its licenses from an external source and ONAP licensing management solution is not used. +If the licensing management solution is provided by ONAP, then ONAP operators will build the VNF license using SDC during onboarding. Refer to the ONAP User Guide for details. The operators require certain information regarding VNF licences. This information currently is delivered out of band. -- cgit 1.2.3-korg