Overview
Current CL event format is based on old structure not expandable to include additional event information if required by downstream.
Problem Statement
Extending VES Data Model to Trigger Close Loop using VES Internal Data Structure to include Control loop specified fields required by Policy to Trigger Close Loop. This approach retains original network event information received (or transferred) into VES under respective domain. The solution ensure all relevant data is at one place for future analysis
Business Requirements
Please see attached PPT.
Current Implementation to implement the control loop requires following data to be placed on the DMaaP:
{
"closedLoopControlName": "ClosedLoop_vSCP",
"requestID": "82ef38ba-2632-4d18-a803-08cf837f14cf",
"triggerID": "107.250.169.145_f5BigIP1461338889739",
"closedLoopAlarmStart": 1461338889739,
"closedLoopEventClient": "microservice.stringmatcher",
"target": "VM_NAME",
"AAI": {
"AICVServerSelfLink": "http://135.25.246.131:8774/v2/81fc2bc61f974de1b5a49e8c2ec090bb/servers/38b28256-a770-4cb2-8724-ea6495123c76",
"VNF_NAME": "vcts3",
"AICVMID": "38b28256-a770-4cb2-8724-ea6495123c76",
"AICTenantID": "81fc2bc61f974de1b5a49e8c2ec090bb",
"LOC_ID": "Middletown",
"AICIdentity": "http://130.3.192.150:5000/v2.0",
"Prov_status": "ACTIVE",
"OAM_IPV4": "107.250.169.145",
"VM_NAME": "basx0001vm034",
"OAM_IPV6": "fe80::f817:3eff:fec3:5d32/64"
},
"from": "DCAE",
"policyScope": "service=vSCP;resource=F5;type=configuration",
"policyName": "configuration.dcae.microservice.stringmatcher.xml",
"policyVersion": "v0.0.1",
"closedLoopEventStatus": "ONSET"
}
Another implementation is to capture the same data in VES commoneventHeader.internalHeader. the data filed are displayed below:
Field name | Required? | Source | Format | Format Example/Values | Description |
closedLoopControlName | no | mS | string | ClosedLoop-FRWL-SIG_d925ed73-8231-4d02-9545-db4e113213abab322 | The closedLoopFlag and closed LoopControlName value is set by the policy defined in Camunda with alarmcondition as key. Camunda, sends the policy update to CAE/PDAS, and HP populates the field during the enrichment |
closedLoopFlag | no | mS | string | Y/N | The closedLoopFlag and closed LoopControlName value is set by the policy defined in Camunda. Camunda, sends the policy update to CAE/PDAS, and HP populates the flag if alarmcondition meets the policy keys. |
identityUrl | no | A&AI | string | get from A&AI | |
oamIpv4 | no | A&AI | string | "107.250.169.145", | OAM IPv4 Address |
oamIpv6 | no | A&AI | string | fe80::f817:3eff:fec3:5d32/64 | OAM IPv6 Address |
physicalLocationId | no | A&AI | string | Middletown | Physical location of the resource |
policyScope | no | mS | string | service=vSCP;resource=F5;type=configuration | The scope of the policy associated with the VES event message |
policyVersion | no | mS | string | v0.0.1 | The version number of the policy associated with the VES event message |
requestId | no | mS | string | "82ef38ba-2632-4d18-a803-08cf837f14cf", | A universially unqiue identifier for the event transaction across all ONAP systems |
selfLink | no | A&AI | string | ||
tenantId | no | A&AI | string | "81fc2bc61f974de1b5a49e8c2ec090bb", | The ID of the provider tenant that owns the resource |
tenantName | no | A&AI | string | The AIC tenant name |
The above data from the Excel file (also added as embedded file) shows the data in the internalHeader (attached to commoneventheader) that is required for executing Control Loop. This replicates the data currently passed via API.
Each Service Provider can define and collect data generated within DCAE echo system by micro Services.(an example is included in the embedded excel file).
Participating Companies
Goals
Contributions
Impacts
- Policy
- DCAE (ServiceComponent/MS)