Uploaded image for project: 'Configuration Persistence Service'
  1. Configuration Persistence Service
  2. CPS-1907

Trust Level: Change of status/Update

XMLWordPrintable

      • Currently, when a DMI plugin is down we populate the DMI Trust Map (DMI name, Trust Level)
        • When the DMI plugin goes down and comes back up then DMI trust Map will always contain the current DMI trust level
        • DMI trust level = NONE = DMI down
        • DMI trust level = COMPLETE = DMI up
        • Query Algorithm for Trust Level Queries: The map CM Handle Trust Map is being used only.
      • Change query algorithm for Trust Level Queries
        • Not only CM Handle Trust Map should be used to query cm handle by trust level but also DMI Trust Map should be utulized.
        • When a trust level query is sent, the trust level for both DMI and CM handle should be compared, and minimum of two (effective trust level) must be selected.
        • if the target trust level (comes from the request) is equal to effective trust level, then cm handle should be selected.

      A/C

      1. After initial registration the customer can query the 'trustLevel' of all cm-handles and see that the trustlevel is 'COMPLETE'
        from the URLs:
        • /ncmp/v1/ch/searches
        • /ncmp/v1/ch/id-searches
      2. Within 30 seconds of a DMI going down. The same query should show all affected handles are 'untrustworthy'

       

      Sample Query Parameters:
      {
        "cmHandleQueryParameters": [
          

      {         "conditionName": "cmHandleWithTrustLevel",         "conditionParameters": [ \{"trustLevel": "COMPLETE"}

       ]
          }
        ]
      }
       

      Out of scope: Notifications

            halil.cakal Halil Cakal
            emaclee Lee Anjella Macabuhay
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: