...
- TOSCA-Metadata directory and TOSCA.meta file (unique CSAR package structure supported in ONAP Frankfurt)
- Manifest file extension, XXX.mf, located at the root or in a location identified in the .meta file. The name of the file is the same of the TOSCA yaml file. Below is example of pnf_main_descriptor.mf in dummyPnfv3.csar
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
metadata:
pnfd_name: myPnf
pnfd_provider: Acme
pnfd_archive_version: 1.0
pnfd_release_date_time: 2019-03-11T11:25:00+00:00
Source: pnf_main_descriptor.mf
Source: Definitions/pnf_main_descriptor.yaml
Source: Definitions/etsi_nfv_sol001_pnfd_2_5_1_types.yaml
Source: Definitions/etsi_nfv_sol001_vnfd_2_5_1_types.yaml
Source: Files/ChangeLog.txtSource: Files/Events/MyPnf_Pnf_v1.yaml
Source: Files/Guides/user_guide.txt
Source: Files/Measurements/PM_Dictionary.yaml
Source: Files/Scripts/my_script.sh
Source: Files/Yang_module/mynetconf.yang
Source: TOSCA-Metadata/TOSCA.meta
Source: Files/pnf-sw-information/pnf-sw-information.yaml
non_mano_artifact_sets:
onap_ves_events:
Source: Files/Events/MyPnf_Pnf_v1.yaml
onap_pm_dictionary:
Source: Files/Measurements/PM_Dictionary.yaml
onap_yang_modules:
Source: Files/Yang_module/mynetconf.yang
onap_others:
Source: Files/Guides/user_guide.txt
onap_pnf_sw_information:
Source: Files/pnf-sw-information/pnf-sw-information.yaml |
Ín the example the following files are not provided:
...