5G NF FM Dictionary:
Scope:
Gain approval for the content and delivery of the FM Dictionary for a 5G NF to ONAP. This assumes that the work to support the collection and publication of PNF artifacts is covered under the PNF Onboarding Package 5G USE Case Work Item—it is not addressed here.
Next Steps:
•Finalize the fields applicable for FM dictionary and gain agreement that this information should be provided by the NF.
• Identify which fields are mandatory and with fields are optional.
•Review with the community the dictionary content including which fields are already covered in the fault event.
•Present again the proposal to have the fault event include the dictionary information via the registration YAML.
•Publish requirements on NFs to provide the FM Dictionary information in the Fault Event registration YAML (NOTE this approach means that there is NOT a separate FM Dictionary artifact that is delivered as part of NF onboarding.
Projects Impacted:
VNF Requirements, DCAE (VES Registration Document needs to be updated), potentially policy so that the processing of the YAML with the use of the dictionary fields is automated (stretch goal). This approach does not require SDC or modeling changes because NFs already have to provide registration YAMLs. This is extending what that YAML provides. No new things have to be catalogued or defined.
Associated Files:
| File Description | File |
|---|---|
| FM dictionary proposed content including how some elements are mapped to the existing fault event | |
FM event registration YAML example showing how FM dictionary fields can be supplied via the comment capability in VES Registration |