From edcc80916503fa6a91d1ac39a11dc413e039075a Mon Sep 17 00:00:00 2001 From: Steven Wright Date: Wed, 11 Sep 2019 14:53:56 +0000 Subject: VNFRQTS add informative text on VNF Licensing Issue-ID: VNFRQTS-590 Signed-off-by: Steven Wright Change-Id: Iee0fc1c1bdd6c1a37afa48a3f98fa270a6648c0c --- docs/Chapter7/VNF-On-boarding-and-package-management.rst | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) (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 f170f30..057599a 100755 --- a/docs/Chapter7/VNF-On-boarding-and-package-management.rst +++ b/docs/Chapter7/VNF-On-boarding-and-package-management.rst @@ -557,7 +557,12 @@ Testing Licensing Requirements ^^^^^^^^^^^^^^^^^^^^^^^ - +ONAP operators 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. +HEAT or TOSCA VNF packages may support such information in future. +VNF licensing behavior also has some constraints. .. req:: :id: R-85653 -- cgit 1.2.3-korg