...

Gain approval for the content and delivery of the Alarm Dictionary to ONAP.  This assumes that the work to support the collection and publication of PNF artifacts is covered under the PNF Onboarding Package Item—it is not addressed here.

Next Steps:

•Finalize the fields applicable for fault/alarm 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. (note the VES Registration document is supposed to include this as an example in 7.0.1—verify this or provide an example)
•Publish requirements on NFs to provide the fault dictionary information in the Alarm Event registration YAML (NOTE this approach means that there is NOT a separate Alarm 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 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: