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

Resolve specification of policy type versions in policies in TOSCA

    XMLWordPrintable

Details

    • Story
    • Status: Closed
    • Medium
    • Resolution: Done
    • None
    • Kohn Release
    • apex-pdp
    • None

    Description

      TOSCA allows specification of versions on policy type definitions. However, there is no way of specifying a version of a policy type on a policy? We introduced the type_version field in our implementation to overcome this ambiguity.

      POLICY-1738 implements the following:
      a) Respect the type_version field if it exists
      b) Use the latest version of a policy type if the type_version field is not specified
      c) Always check that the policy type for a policy exists prior to creating or updating a policy.

      This story is opened in order to trigger an activity to get an ONAP-wide consensus on what should be done here and in order to feed that back to the TOSCA organization.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. POLICY-1738 PAP: Policy Deployment from CLAMP fails as policy-type-version is required to not be null

          • 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

          Bug - A problem which impairs or prevents the functions of the product. POLICY-1738 PAP: Policy Deployment from CLAMP fails as policy-type-version is required to not be null

          • 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

              liamfallon Liam Fallon
              liamfallon Liam Fallon
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: