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

Make PAP component stateless

    XMLWordPrintable

Details

    • Story
    • Status: Closed
    • Medium
    • Resolution: Done
    • None
    • Honolulu Release
    • None

    Description

      As an ONAP developer, I would like to make the PAP component stateless by persisting the cache in policy db so that another instance of PAP can also utilize the current deployment status of the system.

      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

      Attachments

        Issue Links

          blocks

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. POLICY-2769 Support multiple PAP instances

          • 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

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. POLICY-2526 Policy deployment API should be enhanced to reflect actual policy deployment status in PDPs

          • 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

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. POLICY-1821 Persistence of run time policy state in Pdps

          • 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

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. POLICY-1837 Review transaction boundaries of models

          • 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
          mentioned in

          Page Loading...

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              jrh3 Jim Hahn
              ramverma Ram Krishna Verma
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: