VoLTE Use Case Development Tasks



VoLTE use case blocking issues to discuss during Paris F2F Developer Event

JIRA Story

Issue

Issue Description

Reporter

Committer

Action

Status

Note

JIRA Story

Issue

Issue Description

Reporter

Committer

Action

Status

Note



A demo of VoLTE E2E service design on SDC

We would like to see a demo of designing VoLTE E2E service which includes vEPC, vIMS, underlay and overlay networks

Integration team

SDC team





We have seen an early version of it on

SDC VoLTE Demo by David.mp4

You can start from 1:36:00



Integration between VFC/SDNC

SDNC overlay implementation needs to fetch the network information (network id) which should have been stored in A&AI when creating DC network. SDNC will query A&AI based on predefined network name. VFC team needs to provide an A&AI query example to fetch the network info based on network name

SDNC

@maopeng zhang





























All related issues are listed under JIRA Epic 

JIRA story

Task

ONAP Component

Input

Output

Task Description

Committers

Status

Notes

JIRA story

Task

ONAP Component

Input

Output

Task Description

Committers

Status

Notes



VNF CSAR defintion

SDC







  • Define import CSAR format

  • Define export CSAR format

@David Shadmi

Done





E2E service CSAR definition

SDC





  • Define E2E service CSAR format

@David Shadmi



Done





GUI WAN network design support

SDC





  • Define WAN underlay network using Underlay Network Service template

  • Define WAN overlay network using Overlay Network Service template

@David Shadmi

Done

In R1, WAN design part is done through importing Network Service templates which define all parameters needed for WAN underlay and overlay networks.



GUI support on E2E service design

SDC





  • Using SDC GUI to design VoLTE E2E service with vEPC, vIMS and WAN overlay and underlay networks

@David Shadmi

Done

Will add a link to the meeting recording which has a simple demo of VoLTE E2E service design



VoLTE service instantiation sequencing

SDC





  • SDC support of service instantiation sequencing by using Dependency construct

@David Shadmi

Done

SDC can support Dependency construct already

SDC-99: Onbording Tosca VNFClosed

Support TOSCA VNFD import

SDC



SDC Portal

  • Support new node types used by VoLTE VNFD

@David Shadmi

@victor gao

Risk

  • Time is very tight for SDC team because the design is finalized very recently

SDC-193: [Acceptance] onboared vEPC & vIMS VNF'sClosed

Test vendors' VNFD onboarding

SDC

VNFD CSAR

SDC Catalog

  • Obtain vendor's VNFD

  • Verify vendors' VNFD can be onboarded by ONAP

@Chengli Wang

@Michael Lando

High Risk

  • Chengli will help to obtain vendors' VNFD

  • Michael will verify vendors' VNFD can be onboarded by ONAP

INT-137: vEPC Network Service DesignClosed

vEPC service design

Integration

VNFD

CSAR

  • Design network for vEPC

  • Define different design options

  • Work with VNF vendors to figure out the network design for vEPC



@Yang Xu

Done

Need to discuss with integration team and come up with different design options

INT-142: Design network service for vIMSClosed

vIMS service design

Integration

VNFD

CSAR

  • Design network for vIMS

  • Define different design options

  • Work with VNF vendors to figure out the network design vIMS

@Yang Xu

In progress



AAI-241: Define the Rest API of VNFM in esr-serverClosed

AAI-250: Define the Rest API of thirdparty sdnc according to the new data modelClosed

AAI-251: Define the Rest API of VIM register according to the new data modelClosed

A&AI schema change to support ESR

A&AI



A&AI schema

  • Support ESR registration for VIM, SDN DC controller, SDN WAN controller, vendors' SVNFM and EMS

@Zi Li



Done



VFC-181: Update AAI schema for VFC modelsClosed

A&AI schema change to support VFC

VFC



A&AI schema

  • Add new Network Service vertex in A&AI

@maopeng zhang

@subhash

In progress



SO-35: To be able to use Sub worflow BPMN for the flow 2 from top BPMNClosed

SO-33: In order to implement use cases for alternative 2 involving BPMN, they must be modeled.Closed

SO-88: Complete the Network(SDN-C) Function for the VoLTE UsecaseClosed

Workflow design and implementation

SO



Workflow

  • Design a new SO NB interfaces for VoLTE E2E service LCM

  • Design and implement workflow for VoLTE E2E service

  • SO can use Dependency construct to implement service instantiation sequencing

@Chuanyu Chen

@jin xin

@Zhuoyao Huang

In progress

@Yang Xu Need to confirm with SO team they can use the dependency construct

  • Zhuoyao is working on SO SDNC subflow

  • Chuanyu and Xin are working on other part of workflow (flow 2) for VoLTE use case



VFC service instantiation sequence

VFC







@Yan Yang

Done

As we discussed with deployment team in CMCC, parallel deployment of VNFs will hit VIM performance bottleneck.

Have sent Yan Yang an email asking about the need to support VNF instantiation sequencing

[Yan] VF-C didn't  receive the requirements from the VNF vendor that one vnf depends on the others.  So in the R1, VoLTE case don't need to define the VNF sequence.  In the futrue, we can cooperate with SDC team to do it if needed.VNF instantiation parallel is a streth goal in VF-C.



https://lf-onap.atlassian.net/browse/SDNC-19

SDNC-28: Create Directed graphs to activate VXLAN overlay between two DC GWsClosed

SDNC-43: Write JSON template for RESTCONF interface to 3rd party SDN-C controller for overlay networkClosed

DG design and implementation for WAN service

SDNC



DG

  • DG for WAN underlay network

  • DG for WAN overlay network

  • Integration with SO

@gaurav.agrawal

@Zhuoyao Huang

@Brian Freeman

@Dan Timoney

High risk

DC Gateway Controller is not available to test yet

HOLMES-55: Create Rules for the VoLTE Use CaseClosed

Holmes Correlation Rules

Holmes

An example given by Guangron, it contains 2 rules. CLAMP can only support 1 rule in R1.

In email attachment sent by Guangrong on 9/7, file holmes-rule-mgmt-componentspec.json defines:

"parameters": [ { "name": "holmes.default.rule.volte.scenario1", "value": "package dcae.ves.test import org.onap.some.related.packages; rule"SameVNF_Relation_Rule" salience 120 no-loop true

when $root : VesAlarm( $sourceId: sourceId, sourceId != null && !sourceId.equals(""), specificProblem in ( "LSS_cpiPCSCFFailReg(121297)", "LSS_cpiSIPRetransmitInvite(120267)" ), $eventId: eventId) $child : VesAlarm( eventId != $eventId, CorrelationUtil.getInstance().isTopologicallyRelated(sourceId, $sourceId), specificProblem in ("LSS_externalLinkDown(4271)","LSS_failedAttachReqsRateExceeded(4272)"), this after [-60s, 60s] $root) then DmaapService.publishResult(...); end", "description": "The default rule for the VoLTE usecase." }, ],

As Pam explained, in R1 Holmes rules will be bundled with Holmes artifact. DCAE will convert the rules into Blueprint format when onboarding Holmes. CLAMP will configure the rules and store them into Policy. When service is instantaiated, Policy will distribute the rules to DCAE and DCAE will pass it to Holmes when bringing up Holmes analytics.



  • Define correlation policy for VoLTE closed loop event. Different vendors will have different alarm code

@Guangrong Fu

In progress

Integration with CLAMP/Policy/DCAE is the concern

https://lf-onap.atlassian.net/browse/CLAMP-45

https://lf-onap.atlassian.net/browse/CLAMP-34

Closed loop configuration

CLAMP



Blutprint

and Operation Policy

  • Support configuration of all closed loop policy related parameters

  • Distribute policy artifacts to DCAE, Holmes, and Policy

@Gervais-Martial Ngueko

Risk

Integration with Holmes/Policy/DCAE is the concern

https://lf-onap.atlassian.net/browse/POLICY-63

https://lf-onap.atlassian.net/browse/POLICY-43

Policy design

Policy



Policy R1 Amsterdam Functional Test Cases

VoLTE Operational Policy Example:

controlLoop:
  version: 2.0.0
  controlLoopName: ControlLoop-VOLTE-2179b738-fd36-4843-a71a-a8c24c70c55b
  trigger_policy: unique-policy-id-1-restart
  timeout: 3600
 
policies:
  - id: unique-policy-id-1-restart
    name: Restart the VM
    description:
    actor: VFC
    recipe: Restart
    target:
      type: VM
    retry: 3
    timeout: 1200
    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

  • Support auto healing policy for VoLTE

  • Define auto healing policy in GUI

@Pamela Dragosh

@Chenfei Gao

In progress

Integration team needs to talk to Policy team to see how to define the policy in GUI


https://lf-onap.atlassian.net/browse/USECASEUI-2

Usecase UI development

Usecase UI



GUI

  • Support all parameter input defined in VoLTE service template

  • Support VoLTE E2E service instantiation by clicking one button

  • Support alarm monitoring for ONAP and VoLTE service

@Tao Shen

Risk

Development is delayed, and some repo is still empty.

https://lf-onap.atlassian.net/browse/VFC-1

https://lf-onap.atlassian.net/browse/VFC-38



VFC support for VoLTE Network Service

VFC





  • Support Network Service instantiation

  • Support auto-healing

@victor gao

@Yan Yang

In progress

Expect some integration testing with vendor SVNFM and EMS

https://lf-onap.atlassian.net/browse/OOM-18

https://lf-onap.atlassian.net/browse/OOM-19



Containerize ONAP all modules

OOM



ONAP on K8S

ONAP deployment on K8S

@Mike Elliott

Risk

Some ONAP projects (VFC, UUI, MultiCloud, DMaaP) are not deployed by OOM yet. May delay integration