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

VNF

VNF Fault

EPC S/P-GW – Standby MPU is offline

Retart VNF

Guest

VM Fault

VM OS abnormal, Kernel Panic, VM does not send a heartbeat to an external watchdog service for a long time.

I don't know how to merge this column.

Host

Refer to Holmes rule

public class VesAlarm{
    private String eventId;
    private String sourceId;
    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
// Standby_MPU_offline
// No heartbeat, VM is not available

// the entity of the rule
rule "SameVNF_Relation_Rule"
salience 120
no-loop true
    when
        $root : VesAlarm(                                  
            $sourceId: sourceId, sourceId != null && !sourceId.equals(""),
            specificProblem in ( "No heartbeat, VM is not available" ),
            $eventId: eventId)                                 
        $child : VesAlarm( eventId != $eventId,
            CorrelationUtil.getInstance().isTopologicallyRelated(sourceId, $sourceId),
            specificProblem in ("Standby_MPU_offline"),
            this after [-60s, 60s] $root)                      
    then                   
        DmaapService.publishResult(...);       
end

Slides

VoLTE use case control loop.pdf