Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 24 Next »

All related issues are listed underĀ JIRA EpicĀ 

JIRA story

Task

ONAP Component

InputOutputTask DescriptionCommittersStatus

Notes


VNF CSAR defintion

SDC




  • Define import CSAR format
  • Define export CSAR format
Done


E2E service CSAR definitionSDC

  • Define E2E service CSAR format
Done

GUI WAN network design supportSDC

  • Define WAN underlay network using Underlay Network Service template
  • Define WAN overlay network using Overlay Network Service template
David ShadmiDoneIn 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 designSDC

  • Using SDC GUI to design VoLTE E2E service with vEPC, vIMS and WAN overlay and underlay networks
David ShadmiDoneWill 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

SDC-99 - Getting issue details... STATUS

Support TOSCA VNFD importSDC

  • Support new node types used by VoLTE VNFD
Risk
  • Time is very tight for SDC team because the design is finalized very recently

SDC-193 - Getting issue details... STATUS

Test vendors' VNFD onboardingSDCVNFD CSARSDC 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

INT-137 - Getting issue details... STATUS

vEPC service designIntegrationVNFDCSAR
  • 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

INT-142 - Getting issue details... STATUS

vIMS service designIntegrationVNFDCSAR
  • Design network for vIMS
  • Define different design options
  • Work with VNF vendors to figure out the network design vIMS
Yang XuIn progress

AAI-241 - Getting issue details... STATUS

AAI-250 - Getting issue details... STATUS

AAI-251 - Getting issue details... STATUS

A&AI schema change to support ESRA&AI
A&AI schema
  • Support ESR registration for VIM, SDN DC controller, SDN WAN controller, vendors' SVNFM and EMS
Done

VFC-181 - Getting issue details... STATUS

A&AI schema change to support VFCVFC
A&AI schema
  • Add new Network Service vertex in A&AI
In progress

SO-35 - Getting issue details... STATUS

SO-33 - Getting issue details... STATUS

SO-88 - Getting issue details... STATUS

Workflow design and implementationSO
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
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 sequenceVFC


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

SDNC-19 - Getting issue details... STATUS

DG design and implementation for WAN serviceSDNC
DG
  • DG for WAN underlay network
  • DG for WAN overlay network
  • Integration with SO
High riskIntegration with the vendor's PE and DC Gateway is not tested yet

HOLMES-55 - Getting issue details... STATUS

Holmes Correlation RulesHolmes
Drools Rules
  • Define correlation policy for VoLTE closed loop event. Different vendors will have different alarm code
In progressIntegration with CLAMP/Policy/DCAE is the concern

CLAMP-45 - Getting issue details... STATUS

CLAMP-34 - Getting issue details... STATUS

Closed loop configurationCLAMP

Blutprint

and Operation Policy

  • Support configuration of all closed loop policy related parameters
  • Distribute policy artifacts to DCAE, Holmes, and Policy
RiskIntegration with Holmes/Policy/DCAE is the concern

POLICY-63 - Getting issue details... STATUS

POLICY-43 - Getting issue details... STATUS

Policy designPolicy
Drools Rules
  • 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

USECASEUI-2 - Getting issue details... STATUS

Usecase UI developmentUsecase 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
Risk

Development is delayed, and some repo is still empty.

VFC-1 - Getting issue details... STATUS

VFC-38 - Getting issue details... STATUS


VFC support for VoLTE Network ServiceVFC

  • Support Network Service instantiation
  • Support auto-healing
In progressExpect some integration testing with vendor SVNFM and EMS
  • No labels