VoLTE Use Case Control Loop

Description

In the Amsterdam release, VoLTE use case has a requirement on fault correlation and auto-healing, which is closely related to Control Loop, including but not limited to CLAMP, DCAE, Policy, Holmes, Multi-Cloud and VF-C projects.

Story Overview

Example for R1

	Fault	Action

Fault

Action

VNF

VNF Fault

EPC S/P-GW – The slave MPU board is offline or abnormal

Retart VNF

Guest

VM Fault

The guest OS has indicated a failure, requiring VM restart

I don't know how to merge this column.

Host

Refer to Holmes rule

public class VesAlarm{
    private String eventId;
    private String sourceName;
    private String specificProblem;
    private long startEpochMicrosec;
    
    // getters and setters are ommitted for brevity
    ...
}

Refer to Holmes rule

package dcae.ves.test
import org.onap.some.related.packages;

// Alarm specific problems used in the following rules:
// specificProblem
// The slave MPU board is offline or abnormal
// The guest OS has indicated a failure, requiring VM restart

// the entity of the rule
rule "SameVNF_Relation_Rule"
salience 120
no-loop true
    when
        $root : VesAlarm(                                  
            $sourceName: sourceName, sourceName != null && !sourceName.equals(""),
            specificProblem in ( "The guest OS has indicated a failure, requiring VM restart" ),
            $eventId: eventId)                                 
        $child : VesAlarm( eventId != $eventId,
            CorrelationUtil.getInstance().isTopologicallyRelated(sourceName, $sourceName),
            specificProblem in ("The slave MPU board is offline or abnormal"),
            this after [-60s, 60s] $root)                      
    then                   
        DmaapService.publishResult(...);       
end