VoLTE Use Case Development Tasks
- Yang Xu
- Yan Yang
VoLTE use case blocking issues to discuss during Paris F2F Developer Event
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 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 |
|---|---|---|---|---|---|---|---|---|
VNF CSAR defintion | SDC |
| @David Shadmi | Done | ||||
E2E service CSAR definition | SDC |
| @David Shadmi | Done | ||||
GUI WAN network design support | SDC |
| @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 |
| @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 |
| @David Shadmi | Done | SDC can support Dependency construct already | |||
Support TOSCA VNFD import | SDC | SDC Portal |
| @David Shadmi @victor gao | Risk |
| ||
Test vendors' VNFD onboarding | SDC | VNFD CSAR | SDC Catalog |
| @Chengli Wang @Michael Lando | High Risk |
| |
vEPC service design | Integration | VNFD | CSAR |
| @Yang Xu | Done | Need to discuss with integration team and come up with different design options | |
vIMS service design | Integration | VNFD | CSAR |
| @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 |
| @Zi Li | Done | ||
A&AI schema change to support VFC | VFC | A&AI schema |
| @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 |
| @Chuanyu Chen @jin xin @Zhuoyao Huang | In progress | @Yang Xu Need to confirm with SO team they can use the dependency construct
| |
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. | ||||
SDNC-19: Deliver capabilities necessary to support VoLTE use caseClosed SDNC-28: Create Directed graphs to activate VXLAN overlay between two DC GWsClosed | DG design and implementation for WAN service | SDNC | DG |
| @gaurav.agrawal @Zhuoyao Huang @Brian Freeman @Dan Timoney | High risk | DC Gateway Controller is not available to test yet | |
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. |
| @Guangrong Fu | In progress | Integration with CLAMP/Policy/DCAE is the concern | ||
Closed loop configuration | CLAMP | Blutprint and Operation Policy |
| @Gervais-Martial Ngueko | Risk | Integration with Holmes/Policy/DCAE is the concern | ||
Policy design | Policy | Policy R1 Amsterdam Functional Test Cases VoLTE Operational Policy Example:
|
| @Pamela Dragosh @Chenfei Gao | In progress | Integration team needs to talk to Policy team to see how to define the policy in GUI | ||
Usecase UI development | Usecase UI | GUI |
| @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 |
| @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 |