-
Story
-
Resolution: Done
-
Medium
-
None
-
- SDC users need to onboard ETSI v3.3.1 SOL004 VNF CSAR Packages with minimum CNF enhancements from 4.1.1
- Manifest File (e.g., MainServiceTemplate.mf): a new non-MANO artifact set identifier "onap_cnf_helm" - This would identify the "top-level" helm chart that can be used to deploy the CNF directly, i.e., without utilizing the LCM info the VNF Descriptor
- e.g., onap_cnf_helm:
source: Artifacts/helm/helm_charts.yaml
- e.g., onap_cnf_helm:
- Manifest File (e.g., MainServiceTemplate.mf): a new non-MANO artifact set identifier "onap_cnf_helm" - This would identify the "top-level" helm chart that can be used to deploy the CNF directly, i.e., without utilizing the LCM info the VNF Descriptor
- SDC users need to onboard ETSI v3.3.1 SOL004 VNF CSAR Packages with minimum CNF enhancements from 4.1.1
-
- note: to support the direct path, the VNFD could be optional (under discussion with ETSI NFV and ONAP Direct Path team)
- SDC users should be also able to onboard the existing ETSI v2.6.1 SOL004 CSAR packages - one level backward compatibility needs to be supported
- For backward compatibility support, SDC needs to check the package manifest file and metadata such as "compatible_specifcation_versions".
- If it is 3.3.1+, SDC needs to follow a new onboarding path for the ETSI 3.3.1 version package.
- If the version is prior to 3.3.1, SDC follows the existing 2.x onboarding path.
- The package version and its descriptor version should match.
- mentioned in
-
Page Loading...