Uploaded image for project: 'Release Requirements'
  1. Release Requirements
  2. REQ-21

TOSCA Compliant Policies

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Medium Medium
    • Frankfurt Release
    • None
    • None
    • All Control Loop Policy Models should be TOSCA Compliant
    • 2

      In Dublin, not all the current policy models were converted to TOSCA compliant Policy Types. Notably the Control Loop operational and guard policies retained the pre-Dublin model definitions and simpler payloads for the new Policy Lifecycle API. The control loop projects successfully converted the DCAE uS Monitoring policies to the appropriate TOSCA Policy Types vs previously being declared as Node Types. CLAMP only had enough time/resources to support GUI changes for Monitoring TOSCA Policy Types.

      Ideally, all the policies for Control Loops should be declared as TOSCA Compliant Policy Types. In addition, there should be a root Control Loop Policy Type for all the different types of policies such as and not limited to: monitoring, operational, guard, and control loop coordination. The root definition allows for better organization of the policies for a single control loop so a user and or application can "tie" the policies together. Ideally this can now allow the CLAMP platform to be developed such that it can dynamically support any potential Control Loop Policy Type defined by an ONAP user.

       

      https://wiki.onap.org/display/DW/TOSCA+Compliant+Policy+Types

       

            pdragosh pdragosh
            pdragosh pdragosh
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: