Overview

ONAP Policy will support CDS as an actor so that the controlloop usecases can make use of it to take any type of action by executing the CBA. We would like to use the vFW usecase to demonstrate the integration between Policy and CDS.

Problem statement

Current implementation using APPC ModifyConfig

Today, Policy allows the Control Loop Designer to specify the payload for APPC API calls through CLAMP. Policy copies the entire payload of the operation that APPC has to execute against the VNF during closed loop into the APPC LCM request.

Define ModifyConfig action in CDS for Post-Instantiation

Create CDS package (CBA: controller blueprint archive) that defines ModifyConfig action. The inputs that we envision are VNF ID, Port number and credentials for authentication. As a part of this package designer will define the ModifyConfig action by providing golden templates (XML Netconf template) along with a mapping file defining what values to resolve and a python script to resolve the configlet and apply it using NETCONF. An example of deploying configuration to a NETCONF server using CDS can be found here: https://github.com/onap/ccsdk-cds/blob/master/components/model-catalog/blueprint-model/test-blueprint/golden/Scripts/python/ConfigDeploy.py

The recording can be accessed at: Presentation#ONSNA2019

Removing ModifyConfig Parameters from the Policy Template

ModifyConfig action including the parameters and their resolution will be defined in CDS as described above. We will implement CDS API model implementation and actor implementation in policy so that we can either directly invoke CDS to push the NETCONF payload to the vPacketGen VNF or invoke APPC to execute ModifyConfig against the traffic generator VNF.

For example, as described above: a user can define ModifyConfig parameters in CDS using DD and specify the parameter resolution. 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.

Migration to APPC LCM API (Future)

We want to also deprecate the old API for ModifyConfig and use APPC's LCM API interface if possible.

Note: The architecture subcommittee is discussing the common controller API, and we will need to replace the current ModifyConfig APPC action with the common controller API

Participating Companies

Bell, AT&T ....

Artifacts

vFW Clamp and CDS integration use case.pptx

CBA: vFW_CDS_CBA.zip

Data dictionary: dd UPDATES IN cds ui with processor-db.json

Payload to CDS from Policy (rest), gRPC will entail same parameters. WIP

{
  "commonHeader": {
    "originatorId": "Policy",
    "requestId": "1234",
    "subRequestId": "1234-12234"
  },
  "actionIdentifiers": {
    "blueprintName": "test",
    "blueprintVersion": "1.0.0",
    "actionName": "config-deploy",
    "mode": "sync"
  },
  "payload": {
    "config-deploy-request": {
      "service-instance-id": "serviceInstanceId",
      "vnf-id": "genericVnfId",
      "config-deploy-properties": {
        "active-streams": "$activeStreams"
      }
    }
  }
}

Goals

1. To bring in integration of CDS into policy as another actor and demonstrate this integration using the vFirewall end-to-end closeloop usecase (design-time + runtime: instantiation and closeloop)