Versions Compared

Old Version 4

changes.mady.by.user Marco Platania

Saved on

compared with

New Version 5

changes.mady.by.user Marco Platania

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

For Dublin, we will model the vFW interfaces with CDT. This will deprecate the current APPC ModifyConfig API call from Policy to APPC and upgrade to APPC's latest LCM API. Further details about Policy/SO/APPC interaction will be defined later, depending on which technologies (e.g. DD) we can leverage for Dublin release. 

Removing ModifyConfig Parameters from the Policy Template

Today, Policy hardcodes the entire body of the operation that APPC has to execute against the VNF during closed loop. For Dublin, we plan to remove this limitation: Policy will receive the ModifyConfig parameters from CLAMP and pass them to APPC. . Further details about Policy/APPC interaction will be defined later, depending on which technologies we can leverage for Dublin release.

For example, if DD will be available, a user can define ModifyConfig parameters in CDS (extension of current CDT) and specify the parameter resolution in DD. During closed loop, Policy will just tell APPC to execute ModifyConfig against a specific VNF. APPC will then look at the VNF template (built with CDS) to retrieve the ModifyConfig parameters and use DD for their resolution. If DD will not be available, then ModifyConfig parameters could be defined in CLAMP and pushed to Policy during closed loop creation. Policy will then pass these parameters to APPC during closed loop execution. This is how the automated scale out use case is designed for Casablanca.



  • The parameters of the ModifyConfig API should also be made available when CLAMP builds the Operational Policy. This will remove hard-coding of the parameters in the Policy Template. 
  • Addition of guard policies to restrict the number of restarts in a time window (Stretch)
  • Addition of another Control Loop to restart the vPacketGenerator when it hangs (Stretch - need investigation to see if feasible)
    • PLD via Phil Weir - add APPC HealthCheck before restart. Restart would only run if the any HealthCheck failure occurs (eg. the VNF really is hung).
  • Future: Add in Control Loop Coordination of both Control Loops. See the following for more details: https://wiki.onap.org/pages/viewpage.action?pageId=35523671&preview=/35523671/36965215/CLC_11_July_2018.pdf

...