POMBA audit reports are generated based on the rules that applied in the rules engine generating the violations. The following is an initial capture of rules
Rule | Data Sources | Attributes | Description | Category | Severity | Story | |
---|---|---|---|---|---|---|---|
1 | Attribute Comparison | A&AI, SDN-C, Network Discovery | All | This rule compares all attributes by the same name from different Context Builders and returns a violation if the fields do no match. This includes the case where the name is present by the value is null in one of the cases. It does not produce a violation if one of the Context Builders is missing an attribute. | Attribute Mismatch | MAJOR? | |
2 | vnfc-type |
| Validate that each VNFC instance in AAI conforms VNFC type defined in SDC model | VNFC Consistency | ERROR | ||
3 | vnfc-count |
| Validate that for each VNFC node defined in SDC model there is at least one VNFC instance in AAI | VNFC Consistency | WARN | ||
4 | vf-module-type |
| Validate that each VF module instance in AAI conforms VF Module defined in SDC service model | VF Consistency | CRITICAL | ||
5 | nfc-naming-code |
| nfc-naming-code | Validate that nfc-naming-code exists and is populated in AAI VNFC instance | Expected Field Populated | CRITICAL | |
6 | data-dictionary-valid-value |
| TBD | Validates for a particular field that its value aligns to what is in the data dictionary | Invalid Value | ERROR |
Note that Attribute Comparison in particular needs to check against the following, but should check everything it can
- Network Discovered attributes
- AA&I and SDNC Comparisons for
- vnf-type
- vnf-name
- nf-naming-code