| VNF CSAR defintion | SDC
|
|
| - Define import CSAR format
- Define export CSAR format
| | Done |
|
| E2E service CSAR definition | SDC |
|
| - Define E2E service CSAR format
| | 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
| | Done | SDC can support Dependency construct already |
| Jira |
|---|
| server | ONAP JIRA |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | SDC-99 |
|---|
|
| Support TOSCA VNFD import | SDC |
|
| - Support new node types used by VoLTE VNFD
| | Risk | - Time is very tight for SDC team because the design is finalized very recently
|
| Jira |
|---|
| server | ONAP JIRA |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | SDC-193 |
|---|
|
| Test vendors' VNFD onboarding | SDC | VNFD CSAR | SDC Catalog | - Obtain vendor's VNFD
- Verify vendors' VNFD can be onboarded by ONAP
| | High Risk | - Chengli will help to obtain vendors' VNFD
- Michael will verify vendors' VNFD can be onboarded by ONAP
|
| Jira |
|---|
| server | ONAP JIRA |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | INT-137 |
|---|
|
| 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
| | In progress | Need to discuss with integration team and come up with different design options |
| Jira |
|---|
| server | ONAP JIRA |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | INT-142 |
|---|
|
| 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 |
|
| A&AI schema change to support ESR | A&AI |
|
| - Support ESR registration for VIM, SDN DC controller, SDN WAN controller, vendors' SVNFM and EMS
| | Done |
|
| A&AI schema change to support VFC | VFC |
|
| - Add new Network Service vertex in A&AI
| | In progress |
|
| Jira |
|---|
| server | ONAP JIRA |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | SO-35 |
|---|
|
| Jira |
|---|
| server | ONAP JIRA |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | SO-33 |
|---|
|
| Workflow design and implementation | SO |
|
| - 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
| | In progress | Yang Xu Need to confirm with SO team they can use the dependency construct |
| VFC service instantiation sequence | VFC |
|
|
| Yan Yang |
|
|
| DG design and implementation for WAN service | SDNC |
|
| - DG for WAN underlay network
- DG for WAN overlay network
- Integration with SO
| | High risk | Integration with the vendor's PE and DC Gateway is not tested yet |
| Holmes Correlation Policy | Holmes |
|
| - Define correlation policy for VoLTE closed loop event. Different vendors will have different alarm code
| | Risk | Developement is delayed, may not in MVP |
| Closed loop configuration | CLAMP |
|
| - Support configuration of all closed loop policy related parameters
- Distribute policy artifacts to DCAE, Holmes, and Policy
| | Risk | Developement is delayed, may not in MVP |
| Policy design | Policy |
|
| - Support auto healing policy for VoLTE
- Define auto healing policy in GUI
| | In progress | Integration team needs to talk to Policy team to see how to define the policy in GUI
|
| Usecase UI development | Usecase UI |
|
| - 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
| | Risk | Development is delayed, and repo is still empty as of September 5, 2017. May not in MVP |
