From d2af87d85d87960045ac92b8efac3e39f27b6d84 Mon Sep 17 00:00:00 2001 From: Eric Debeau Date: Thu, 27 Aug 2020 14:12:45 +0200 Subject: Correct bad reference links in user guide/pre-onboarding section onap prefix is missing for 2 references towards vnfrqts project Issue-ID: DOC-660 Signed-off-by: Eric Debeau Change-Id: I3a08aed60793f56afce691d5b885117b2da2131c --- docs/guides/onap-user/design/pre-onboarding/index.rst | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) (limited to 'docs') diff --git a/docs/guides/onap-user/design/pre-onboarding/index.rst b/docs/guides/onap-user/design/pre-onboarding/index.rst index 77583ac75..2509ee7b9 100644 --- a/docs/guides/onap-user/design/pre-onboarding/index.rst +++ b/docs/guides/onap-user/design/pre-onboarding/index.rst @@ -22,8 +22,9 @@ Generate Manifest and Package Artifacts to create TOSCA based VNF or PNF Onboarding Packages are not described here -The for onboarding the zip-file requires besides the HEAT template also a MANIFEST.json file, which describes the content of the package. -To generate a MANIFEST.json file a script can be used offered by the SDC project: +The for onboarding the zip-file requires besides the Heat template also a +MANIFEST.json file, which describes the content of the package. To generate a +MANIFEST.json file a script can be used offered by the SDC project: `generate-manifest.py`_ These steps are performed outside SDC. @@ -72,9 +73,11 @@ Validate xNF Package (VNF/PNF) VNF and PNF packages have to follow the requirements described in: -:ref:`VNF and PNF Modeling Requirements` +:ref:`VNF and PNF Modeling Requirements +` -:ref:`ONAP Management Requirements` +:ref:`ONAP Management Requirements +` For Validation of VNF and PNF packages the tools delivered by VNFSDK can be used: -- cgit 1.2.3-korg