Uploaded image for project: 'Policy Framework'
  1. Policy Framework
  2. POLICY-2769

Support multiple PAP instances

    XMLWordPrintable

Details

    • Story
    • Status: Closed
    • High
    • Resolution: Done
    • None
    • Istanbul Release
    • None
    • Policy 2/25-3/8, Policy 3/16-3/30, Policy 3/30 - 4/13, Policy 4/21 - 5/5, Policy 5/6 - 5/20, Policy 23/6 - 7/7

    Description

      As an ONAP developer, I would like to make it possible to run multiple instances of the PAP component.  May only be able to do design work during Honolulu.

      Considerations:

      • Should secondary PAP instances be able to update PDPs simultaneously?
      • Race conditions may occur if CLAMP were to issue policy deployment requests to more than one PAP
      • Even if CLAMP only communicates with a single PAP, race conditions may still occur, wherein the wrong PAP has the final say on what is deployed to a given PDP
      • The approach needs to be able to handle the case where a PDP is unable to deploy a policy
      • Should all PAPs read and process heartbeats?  If not, then the heartbeats will have to be published on a separate topic from the PDP-UPDATE responses, because the latter have to go to all PAPs to avoid the need for point-to-point communication

      Attachments

        Issue Links

          is blocked by

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. POLICY-2648 Make PAP component stateless

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed
          relates to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. POLICY-2898 Policy should function in a multi-cluster environment

          • High - Severely impaired functionality. Erratic performance and reduced system availability. It may cause major components or features of the system to be unavailable although certain parts of the system remain functional. A workaround may exist but its use is unsatisfactory or at a high time cost (manual intervention required). Must be fixed in any of the upcoming builds and should be included in the current release.
          • Closed
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              jrh3 Jim Hahn
              jrh3 Jim Hahn
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: