-
Story
-
Resolution: Done
-
High
-
None
add new keyword onap_pnf_sw_information in non-MANO artifact to support PNF software version onboarding into R146092 in Frankfurt Release
Proposed Text (red font)
-------------------
Requirement: R-146092
target: VNF or PNF TOSCA CSAR PACKAGE
keyword: MUST
introduced: dublin
updated: frankfurt
If one or more non-MANO artifact(s) is included in the VNF or PNF TOSCA CSAR package, the Manifest file in the CSAR package MUST contain one or more of the following ONAP non-MANO artifact set identifier(s).
onap_ves_events: contains VES registration files
onap_pm_dictionary: contains the PM dictionary files
onap_yang_modules: contains Yang module files for configurations
onap_ansible_playbooks: contains any ansible_playbooks
onap_pnf_sw_information: contains the PNF software information file
onap_others: contains any other non_MANO artifacts, e.g. informational documents
*NOTE: According to ETSI SOL004 v.2.6.1, every non-MANO artifact set shall be identified by a non-MANO artifact set identifier which shall be registered in the ETSI registry. Approved ONAP non-MANO artifact set identifiers are documented in the following page* https://wiki.onap.org/display/DW/ONAP+Non-MANO+Artifacts+Set+Identifiers
**
-------------------
- clones
-
VNFRQTS-744 Onboard PNF software version requirements
- Closed
- is cloned by
-
VNFSDK-531 PNF package validation on PNF software version
- Closed
- links to