Uploaded image for project: 'Logging analytics'
  1. Logging analytics
  2. LOG-434

Post Orchestration Audit - Rules Update for Attribute Comparison

XMLWordPrintable

      As an Operations person, I would like Validation Rules for POMBA to be updated to include attributes from Network Discovery so that it can be audited against other retrieved contexts from AAI/SDNC. This will be done in a generic way such that any two attributes of the same name against a given resource shall be compared to see if they are an exact match. It should also support additional context builders returning the same fields and then having the fields audited. While adding new attributes can't require a rule update, adding new context builders may.

      Initially

      • A&AI versus SDNC
      • A&AI versus Network Discovery
      • SDNC versus Network Discovery

      A rule must be added that compares fields from various data sources that share the same attribute name (as defined in the POMBA common model) and raises a violation if these do not match.

      • Rule Name
        • Attribute Comparison
      • Violation Names
        • Attribute Value Mismatch

      The rule must not require that specific fields need to be added to the rule in order for validation to take place.

      Each violation has to report the following for each attribute in question

      • Data source (ie context builder)
      • Attribute name
      • Attribute value

      It must be possible to clearly report either one attribute violation or a list of them. This can be achieved in one of two ways, whichever is easiest

      • Report as separate violations in the same report
      • Report as a single violation in the report, where each attribute in violation is clearly listed and well-formatted.

      If this rule results in double reporting of problems due to the way some existing rules were written, then these existing rules should be modified, unless there is a compelling reason to not do so.

      Value

      Rules are able to audit network discovery information, as well as any other two data sources that return the same field.

       

      Success Criteria

      • Compliant to the ask above
      • Support for all ONAP best practices
      • Code checked in, use documented on Wiki
      • Demo to working group

      Exclusions

      • Testing for network discovery use cases if not ready. This can be tracked separately.
        • SDNC-319 Network Discovery - Open Stack - VM Attributes
        • SDNC-328 Network Discovery - Open Stack - L3 Network

            prioux prioux
            dkedrosk dkedrosk
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: