Former user (Deleted)

Ramki Krishnan

Zu Qiang

Ulas Kozat

wangyaoguang

07 Aug 2019 

14 Aug

2019 

marge.hillis

Vimal Begwani

21 Aug

2019 

Andy Mayer

Hui Deng

04 Sep 2019 

Timo Perala

Samuli Kuusela

11

Sep 2019 

18 Sep 2019 

25 Sep 2019 

James Forsyth

02 Oct 2019 

09 Oct 2019 

R6 M1 Deadline (Oct 10 2019)

M1 Checklist: Deliverables for Planning Milestone Checklist Template

READ THE DOCS: http://onap.readthedocs.io/en/latest/guides/onap-developer/developing/index.html  > USER GUIDES > Verified Use Cases

and discussion with A&AI (James Forsyth ) continuing discussion from Sept 25.

Network Slicing has two proposals in R6 (LIN MENG CMCC and Swaminathan Seetharaman ). Need to align the two proposals and present at Use Case S/C meeting (Alla G.) and TSC and Architecture next week Oct 14.

16 Oct 2019 

23 Oct 2019 

Benjamin Cheung

Joanne Liu Rudel

Sandeep Shah

30 Oct 2019 

Discussion with OOF PTL (Shankaranarayanan Puzhavakath Narayanan ) for R6 Use Case Impacts discussion and technical details for OOF impacting Use Cases

06 Nov 2019 

Seshu Kumar Mudiganti

13 Nov 2019 

20 Nov 2019 

Swaminathan Seetharaman

LIN MENG

Shankar PN

27 Nov 2019 

04 Dec 2019

11 Dec 2019 

Discussion with Controller (APP-C, SDN-C) PTL (Dan Timoney) for R6 Use Case Impacts to Controller project. A technical discussion, Q&A, and U/C analysis.

18 Dec 2019  25 Dec 2019 

Andy Mayer

Scott Blandford

Wiki Page: PNF PLUG and PLAY in R6 Frankfurt

Use Case Spreadsheet: Indicates Impact

Frankfurt Release Requirements : Indicates Impact

WIKI:

• E#3a: Change to the onboarding (definition) of the BPMN workflow. To bring war file with the workflow (is it a large or small refactoring) - QUESTION: "small" would keep the current approach custom BPMN, also discussion about moving to a new frame work. A large impact would be moving to a new framework. Will the custom BPMN be "deprecated" or will it will be supported fully?

• E#3b: Migrate existing workflows to existing building blocks.
• Trying to change the existing BPMN logic, make it more generic make it as a "building block" concept. Makes SO more abstract re-usable way to handle onboarding; current steps are rigid and tightly bound trying to make it on-demand. Not all BPMN will be affected, just the PNF-related BPMN W/Fs will be impacted.  The current logic will change - getting building based concept. BPMN BB is a concept of how you "write" the BPMNs.

• Need to sync on the VID implementation of 5G VID Instantiation/orchestration. VCPE also wants to use these building blocks.

• This was originally identified before R5 El Alto but was pushed to R6.

SUMMARY: E#3a: Change to the onboarding (definition) of the BPMN workflow. (SO-1838)

E#3b: Migrate existing workflows to existing building blocks. (SO-1838)

ACTION: 06 Nov 2019 Seshu Kumar Mudiganti create a new story to make it more explicit

PNF / PNF Software Upgrade using direct Netconf/Yang interface with PNF

Wiki Page: PNF software upgrade in R6 Frankfurt

Frankfurt Release Requirements : Indicates Impact

This is one of the PNF upgrade scenarios. Also includes development of some common functionality used by the other PNF upgrade scenarios.

Use case with all scenarios was presented at the SO meeting. Question (Seshu) regarding resources/workforce how many people will be working on this? joint commitment Ericsson & Huawei. Multiple people working on the U/C but don't know how division of labor yet. Want people E2E, from coding through integration. We have seen in SO is lacking in integration/test. When committing resources would be nice to have E2E commitment. Would like to have post M4 (RC0-RC2) support.

Expectation: Need to plan for different types of testing/bug fixing. Fwd'd to team. Question Seshu: asking how many people? Answer: 06 Nov 2019 not defined, there is a team expect enough resources. Seshu: problem when moving resources across teams, tech different and expectations different. expertise is insufficient across projects. To finish this need to identify people asap; Oskar: there is one experienced person with SO.

06 Nov 2019  wangyaoguang new API impacts in SO. Talked with Zu Qiang  in SO will provide new PNF custom W/F API. North-bound API to trigger PNF work-flow. Use existing W/Fs? Same principle as for VNFs. Look at the url will see PNF instead of VNF. CM requirements for PNF S/W upgrade. There is already W/F API for VNF. Propose to add a NEW API for PNF. Will discuss before M2.

WIKI:

• Support generic PNF CM workflow, including SO building block shall be extended to support PNF LCM actions
• SO API extension: PNF software upgrade with target software version
• SO BB for downloadNESw, activateNESw, preCheck, postCheck
• API (LCM or CDS SS) selection within the same BB

SUMMARY: -

PNF / Enable Schema Update once PNF software is updated

PNF / Enhancement on PNF Software Upgrade with EM with Ansible

PNF / PNF Software Upgrade with EM with Netconf

PNF / Configuration with NETCONF/ Secure Communication between xNFs and ONAP

Wiki Page: 5G RAN SERVICE MODELING & DEFINITION in R6 Frankfurt

The platform information model may impact SO as SO consumes the model.

SUMMARY: Need to investigate if model changes will impact SO consumption of the model. Ben will send Seshu presentation made to the modeling sub-committee. 28 Oct 2019 

5G / Bulk PM / PM Control

Wiki Page:

5G Bulk PM in Frankfurt/R6

Frankfurt Release Requirements : Indicates

Impact

WIKI: Workflow shall update status attribute in AAI when the VNF/PNF instance has been fully instantiated. Will have dependency/connection.

For PNFs there might be a gap.

- QUESTION: (Marci Haas) This is a Use Case in December 5, 2019 to be demoed, are we on track? ANSWER: the new functionality will not be in the December Demo.

• orchestration-status is main candidate
• At least for PNFs it is expected that the SO workflow must be updated to set this attribute (Jira issue defined)

SUMMARY: There might be a dependency on the SO refactoring (See PnP U/C Epic #3a/#3b)

Wiki Page: FM META DATA & PM DICTIONARY in R6 Frankfurt

SUMMARY: No Impact

Wiki Page: NETWORK SLICING PoC in R6 Frankfurt (Obsolete)

Frankfurt Release Requirements : Indicates Impact

WIKI:

Original scope has undergone some changes, Swaminathan Seetharaman  will discuss with SO the impacts.

• Enhance Request handler with Network Slicing instantiation
• Workflow for recursive service instantiation
• Handling of shared / dedicated services
• Store slice catalog items

SUMMARY: Impacts

need to create additional Jira, ... there is an Epic, and will need to create a story.

Wiki Page:

5G CONFIGURATION (

RunTime DB)

Use Case Spreadsheet: Indicates Impact

WIKI: Wiki Indicates No Impact

SUMMARY: -

Wiki Page: 5G Network Resource Model (NRM) Configuration in R6 Frankfurt

Frankfurt Release Requirements : Indicates Impact

WIKI:

• New BBs coding for PnP instantiation
• Enhance related workflowSpecifications API
• Add new NB API for instance management for pnf
• add workflow for modify/delete/query NRM config
• Enhance related workflowSpecifications API:
• New NB API to trigger the custom workflow:
• Enhance configuration related BB to support NRM Configuration (*NOT* additional API):
• New native specific workflows(*NOT* additional API):

SUMMARY: Need some additional offline meetings with wangyaoguang

Wiki Page: Scaling Use Case (Frankfurt)

Frankfurt Release Requirements: Indicates Impact

WIKI:

• CDS Actor Selection for Scale Out Use case (TechM)

SUMMARY: Wiki indicates Seshu has committed. No Jira created yet.

Yuriy Malakov may have already created tickets for this (check)

Benjamin Cheung Seshu Kumar Mudiganti Scale out with CDS Actor JIRA is 

Wiki Page: BBS Broadband Service Use Case (Frankfurt)

Use Case Spreadsheet: Indicates Impact

WIKI: Needs Investigation. Wiki page needs work.

SUMMARY: Needs Investigation. Seshu says there is no commitment right now for this U/C

Potential outage Chaker Al-Hakim . Scope is undefined. Not decided what will happen in R6 release. 

Update from David Perez Caparros: BBS use case will focus on bug fixes and documentation in R6, as reported during the last F2F use case subcommittee meeting in Antwerp.

Wiki Page: CCVPN Use Case in Frankfurt Release

Use Case Spreadsheet: Indicates Impact

Frankfurt Release Requirements: ELINE Service over OTN NNI Indicates Test only

WIKI: Needs Investigation. Wiki page isn't clear per Project Impacts.

Xin Miao (Unlicensed)  - 06 Nov 2019 ASAIK there is no SO change. Confirm with Henry Yu (Huawei). 

SUMMARY: Needs to confirm with Henry Yu

There will likely be a Testing Effort (ELINE)

Wiki Page: Control Loop Sub Committee Frankfurt Release Planning

Use Case Spreadsheet: Indicates Impact

WIKI:

Event based Common API for Control Loop Operations, scaleup/scaledown instantiation and PNF PNP.  Event based Common Notification messaging format for Control Loop Operations

APPC, SO, SDNC, VFC and SDNR to implement support of message and their flow from Policy

SUMMARY: Seshu Kumar Mudiganti  has no commitment.

Potential Outage - Wiki Page indicates SO impact.

Wiki Page: Multi-domain Optical Network Services

Use Case Spreadsheet: Indicates Impact

WIKI:

Alignment (done): 3rd party ODM would change on 2 of BPMN. Need coordination. 3PODM post-poned (to R7) changed, thus only this MDOSL0L1O U/C will impact.

Question: will refactoring affect this U/C? Answer: From Seshu: The refactoring is focused on PNF; thus it will NOT affect this U/C. BBS, VCPE & HPA will be affected.

Question: Interaction with CCVPN use case and how will that affect your U/C? services not in place, have you talked to the CCVPN team; the extension doesn't have impact on SO in this release. This U/C is a SUB-use case of CCVPN. Detail alignment on resource modeling. CCVPN has a subU/C about e-line service orchestration. Thus alignment needs to happen between these two use cases. Code for CCVPN will be REUSED by this U/C, just make modification on those existing. Are you expecting SO interaction? Yes, the BPMN flows.

Question: What are the two BPMN flows > the diagrams are in: Multi-domain Optical Network Services ; last time what you showed SO was a functional flow but not a BPMN change. Seshu wants to know the actual

BPMN change. The two BPMN flow custom create end-to-end service instance. other is delete. Reuse these flows but to make some enhancements. there isn't a new or change in the W/F needed. We have to reuse existing flow and make model/configuration changes.

SUMMARY: Can meet off-line with Xin Miao (Unlicensed)

Wiki Page: Change Management Frankfurt Extensions

Use Case Spreadsheet: Indicates Impact

WIKI:

• Wish List
• Workflow as Independent Artifact
• Support Service Level Workflows

Email from  Lukasz Rajewski : "can you please add Change Management use case to the agenda, at least the items/REQ I am responsible for in Frankfurt: REQ-182, REQ-187, REQ-191"

SUMMARY: Seshu Kumar Mudiganti  had a discussion Architecture Meeting but need follow-up.

Wiki Page: Run time Security using ISTIO - as a POC

WIKI:

• ISTIO-ingress and MetalLB for ingress connections (connections to Multi-Cloud project from other projects) – Secure at least with one project (SO) and non-secure with others.

SUMMARY: Needs Investigation. Seshu Kumar Mudiganti is unaware of this change.

contact Srinivasa Addepalli

Wiki Page: Distributed Analytics as a Service (Continuation from R4)

Use Case Spreadsheet: Indicates Impact

WIKI: Needs work.

SUMMARY: Needs investigation. Seshu Kumar Mudiganti  is not aware of this impact.

Wiki Page: Third-party Operational Domain Manager

Use Case Spreadsheet: Indicates Test Only

Frankfurt Release Requirements: Doesn't indicate anything

WIKI:

• Catalog Sync Interaction - (Step 5) where SO pulls SDC catalog details.
• ORDER ACTIVATION FLOW - Steps 8, 9, 12
• SDC Service Distribution - SO Impact
• Flow for Service Instantiation

SUMMARY: Impacts. Test only? Confirm. Need investigation. Only doing design time; run-time is not started. Contact Nishi Mathur (Telstra)