Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
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)
Mark to deprecate the old API for ModifyConfig and leverage CDS GRPC enabled Self Service API to enable LCM actions such as configModify and other lcm action for xNF.
Participating Companies
Bell, AT&T, Ericsson. Huawei
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
Another possibility to make the payload to be JSON format:
Code Block | ||||
---|---|---|---|---|
| ||||
{
"commonHeader": {
"originatorId": "Policy",
"requestId": "1234", # From the Onset event
"subRequestId": "5678" # From the ControlLoopOperation object
},
"actionIdentifiers": {
"blueprintName": "test", # Embedded into operational policy YAML payload
"blueprintVersion": "1.0.0", # Embedded into operational policy YAML payload
"actionName": "config-deploy", # Embedded into operational policy YAML payload
"mode": "async"
},
"payload": {
"config-deploy-request": {
"aai-properties":{
"$aai.params": "$aai.params" # Enriched AAI attributes in node.attribute format
.....
},
"config-deploy-properties": { # FRee form JSON from CLAMP embedded into operational policy YAML payload.
"$data": {
"mapInfo": {
"key": "val"
},
"arrayInfo": [
"one",
"two"
],
"paramInfo": "val"
}
}
}
}
} |
Sample matching operational policy YAML (El-Alto): To be aligned with changes per Control Loop Policy Type Design Proposal #1: Simple upgrade of legacy policy types to TOSCA and TOSCA Compliant Policy Types)
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
tosca_definitions_version: tosca_simple_yaml_1_0_0 topology_template: policies: - operational.modifyconfig: type: onap.policies.controlloop.Operational version: 1.0.0 metadata: policy-id: operational.modifyconfig properties: controlLoop: version: 2.0.0 controlLoopName: ControlLoop-vFirewall-__ResourceID__ trigger_policy: unique-policy-id-1-modifyConfig timeout: 1200 abatement: false policies: - id: unique-policy-id-1-modifyConfig name: modify_packet_gen_config description: actor: CDS recipe: config-deploy # Blueprint action-name target: resourceID: __ResourceID__ type: VNF payload: artifact_name: vfw-cds # Blueprint name artifact_version: 1.0.0 # Blueprint version mode: async # Blueprint mode type data: '{"mapInfo":{"key":"val"},"arrayInfo":["one","two"],"paramInfo":"val"}' # Free-form json supplied by CLAMP retry: 0 timeout: 300 success: final_success failure: final_failure failure_timeout: final_failure_timeout failure_retries: final_failure_retries failure_exception: final_failure_exception failure_guard: final_failure_guard |
TBD: To be tracked as a separate functional requirement
CLAMP rendering possible actions supported by CDS + rendering of the input fields from CBA. Below options available from CDS (Yuriy to add more details)
- Open API generated from the protobuf.
- Ingest the TOSCA yaml from CDS
Follow-up from Controlloop subcommittee item "Discussion on the type of spec CDS needs to create for CLAMP to use: OPEN-API or grpc specification":
- @Rashmi and @Yuriy to add the CBA CSAR to the wiki.
- CDS team @Yuriy to think of the notion of classification in CDS to identify the level at which the action/resolution must be acted upon. We do have this representation in Policy.
- What is the standard way to to expose actor capabilities via CLAM? @Martial to get back with feedback for @Yuriy about the preferred way of their choice of spec to ingest the CDS models: Open-API/gRPC. Investigate expressing the model in TOSCA (SDC CSAR).
Goals
- 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)
Contributions
[WIP]
Operational Policy Model to support CDS as an actor
CDS Blueprint archive details
Future improvements
Impacts
Project | Impact | Notes |
---|---|---|
Policy | high |
|
CLAMP | low | Provide CDS as an actor for policy |
CDS | low | Policy-CDS Self-Serve API, CBA definition |
Integration | medium | Update the testsuite repo to use the latest CBA, new operational policies and other updated artifacts |
Open Questions
Facilitate ways for policy to ingest/process a dynamic payload in a generic way so it can act as a passthrough between CLAMP and CDS for payload specific params. CLAMP to render CDS blueprint??CDS actions and the layer at which the target resolution/actions are to be taken → driven by CDS action and target-type in Operational Policy modelMapping between CLAMP --> Operational Model --> CDS input params
Mark old APPC LCM API for deprecation. Leveraging CDS GRPC enabled Self Service API to enable LCM actions such as configModify and other lcm action for xNF- CDS + CLAMP integration: new functional requirement and usecase requirement to demonstrate this integration.
Dependency on updating TOSCA Operational Policy model. To follow-up on Controlloop subcommittee - Stretch Goal: Testsuite update (Daniel Rose), parallel testsuite for vFW. Continue using current APPC workflow for vFW.