summaryrefslogtreecommitdiffstats
path: root/docs/onboardingpackages.rst
diff options
context:
space:
mode:
authorChrisC <christophe.closset@intl.att.com>2020-11-13 15:04:38 +0100
committerVasyl Razinkov <vasyl.razinkov@est.tech>2020-11-13 16:05:14 +0000
commit8143fb5a129a321079cc6e93c74e32abc03ab041 (patch)
tree6c13562e8d74d7fad17473d99c0f64a88c1dafc3 /docs/onboardingpackages.rst
parentb8d71b90706577bd748371f90160c1862a8ce96a (diff)
Update Documentation
Update local SDC doc with Guilin Content Issue-ID: SDC-3370 Signed-off-by: ChrisC <christophe.closset@intl.att.com> Change-Id: I3d94e3dbb8c4a8e2723ec364e6d4c6e9ff03946a
Diffstat (limited to 'docs/onboardingpackages.rst')
-rw-r--r--docs/onboardingpackages.rst17
1 files changed, 16 insertions, 1 deletions
diff --git a/docs/onboardingpackages.rst b/docs/onboardingpackages.rst
index ee668a3178..bdca18b606 100644
--- a/docs/onboardingpackages.rst
+++ b/docs/onboardingpackages.rst
@@ -14,6 +14,11 @@ SDC supports the following packages types
- Heat Package
- ONAP Tosca CSAR Package
- ETSI SOL004 Tosca CSAR Package
+- Basic Helm package support for CNF
+
+For an extensive guide on how to perform onboarding, please refer to the ONAP User guide:
+* :ref:`doc_guide_user_des`
+
Heat Package
^^^^^^^^^^^^
@@ -50,6 +55,12 @@ Other Points to note when onboarding this package are:
- The original input CSAR is maintained and stored as the SDC artifact *ETSI_PACKAGE* in the xNF internal model. For existing legacy xNF, it can be stored as *ONBOARDED_PACKAGE* instead.
- The non-mano artifacts are mapped to the corresponding SDC Artifact Type in the xNF internal model.
+Basic Helm package support for CNF
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+The helm package support is new since Guilin release, helm chart packaged as tgz file can be onboarded and distributed.
+The support is limited for this first release.
+
Package Types applicable to Resource Types
------------------------------------------
VF
@@ -88,7 +99,11 @@ How does SDC determine which package type is being onboarded
SDC onboarding processes each of the package types differently. SDC determines which package type is being onboarded, and
hence which logic to use, based on the following
-First SDC checks the extension of the package. If the package extension is *.zip* then the package is treated as a `Heat package`_.
+First SDC checks the extension of the package. If the package extension is *.zip* then the package is treated as a `Heat package`_ or `Basic Helm package support for CNF`_.
+
+To determine whether the package is of type Helm, SDC looks into the package content and tries to find Helm base files if not found it will treat it as Heat.
+
+If it determines that this is a Helm package, SDC will add dummy Heat descriptor files.
If the package extension is *.csar* and the following is true