| 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 |
| SDC Portal | - 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
| | Done | 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 |
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | AAI-241 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | AAI-250 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | AAI-251 |
---|
|
| 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
| | Done |
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | VFC-181 |
---|
|
| A&AI schema change to support VFC | VFC |
| A&AI schema | - 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 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-88 |
---|
|
| 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
| | 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.
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SDNC-19 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SDNC-28 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SDNC-43 |
---|
|
| DG design and implementation for WAN service | SDNC |
| DG | - DG for WAN underlay network
- DG for WAN overlay network
- Integration with SO
| | High risk | Integration with the vendor's PE and DC Gateway Controller is not tested yetavailable to test yet |
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | HOLMES-55 |
---|
|
| 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. | Holmes Correlation Policy | Holmes |
| - Define correlation policy for VoLTE closed loop event. Different vendors will have different alarm code
| | Risk | In progress | Integration with CLAMP/Policy/DCAE is the concern
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CLAMP-45 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CLAMP-34 |
---|
|
Developement is delayed. Not in MVP | 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
| | Risk | Developement is delayed, not in MVP | Integration with Holmes/Policy/DCAE is the concern |
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | POLICY-63 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | 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
| 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
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | 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
| | Risk | Development is delayed, and some repo is still empty as of September 5, 2017. Not in MVP. |
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | VFC-1 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | VFC-38 |
---|
|
| VFC support for VoLTE Network Service | VFC |
|
| - Support Network Service instantiation
- Support auto-healing
| | In progress | Expect some integration testing with vendor SVNFM and EMS |
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | OOM-18 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | 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 |