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 https://zoom.us/recording/play/KIwLvr5cJb2Q_vx1BdHBTF0-f-pFpTkD_gpO3iBSeq5VDapCSe-FjbbhS2LkTygO. 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 | |||||
All related issues are listed under JIRA Epic
| JIRA story | Task | ONAP Component | Input | Output | Task Description | Committers | Status | Notes |
|---|---|---|---|---|---|---|---|---|
| VNF CSAR defintion | SDC |
| Done | |||||
| E2E service CSAR definition | SDC |
| 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 |
| Done | SDC can support Dependency construct already | ||||
SDC-99 - Getting issue details... STATUS | Support TOSCA VNFD import | SDC | SDC Portal |
| Risk |
| ||
SDC-193 - Getting issue details... STATUS | Test vendors' VNFD onboarding | SDC | VNFD CSAR | SDC Catalog |
| High Risk |
| |
INT-137 - Getting issue details... STATUS | vEPC service design | Integration | VNFD | CSAR |
| Done | Need to discuss with integration team and come up with different design options | |
INT-142 - Getting issue details... STATUS | vIMS service design | Integration | VNFD | CSAR |
| Yang Xu | In progress | |
| A&AI schema change to support ESR | A&AI | A&AI schema |
| Done | ||||
VFC-181 - Getting issue details... STATUS | A&AI schema change to support VFC | VFC | A&AI schema |
| In progress | |||
| Workflow design and implementation | SO | Workflow |
| In progress | Yang Xu Need to confirm with SO team they can use the dependency construct
| |||
| VFC service instantiation sequence | VFC | Yan Yang | 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 | |||||
| DG design and implementation for WAN service | SDNC | DG |
| High risk | DC Gateway Controller is not available to test yet | |||
HOLMES-55 - Getting issue details... STATUS | 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:
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. |
| In progress | Integration with CLAMP/Policy/DCAE is the concern | ||
| Closed loop configuration | CLAMP | Blutprint and Operation Policy |
| Risk | Integration with Holmes/Policy/DCAE is the concern | |||
| Policy design | Policy | Drools Rules |
| In progress | Integration team needs to talk to Policy team to see how to define the policy in GUI | |||
USECASEUI-2 - Getting issue details... STATUS | Usecase UI development | Usecase UI | GUI |
| Risk | Development is delayed, and some repo is still empty. | ||
| VFC support for VoLTE Network Service | VFC |
| In progress | Expect some integration testing with vendor SVNFM and EMS | ||||
| 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 |