Versions Compared

Old Version 10

changes.mady.by.user Xin Miao (Unlicensed)

Saved on

compared with

New Version Current

changes.mady.by.user Oskar Malm

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Attendees

DISCUSSION ITEMS LOG


that need transport models need some model consistency.
CtgryItemWhoNotes

Pltfm


PLATFORM TOPICS:

Controller to NF Association

Benjamin Cheung

R5/R6 Topic

See Slides Nov 6, 2018. Development of Controller to NF assignment association S/W.

CDS, VF-C, APP-C, SDN-R, SDN-C; will the CCSDK "merging" of controllers happen in R6?

USE CASE REALIZATION MEETING (Notes 2018-11-6) Ctrl-NF

Pltfm

PLATFORM TOPICS:

Data Persistency, RunTime DB

N.K. Shankaranarayanan

Joanne Liu Rudel

Benjamin Cheung

STATUS: Work for RunTime DB completed, not merged in R4

Dan Timoney moved to R5, one Jira for RunTime DB. One issue about merging.

ONAP code added can take a test ONAP deployment to have the ConfigDB work.

USE CASE REALIZATION MEETING (Notes 2019-01-30) U/C Cross-Interaction, Persistency

5G CONFIGURATION (RunTime DB)CONFIGURATION PERSISTENCE SERVICE R6

Pltfm

PLATFORM TOPICS:

Controller LCM API Evolution

Oskar Malm

https://wiki.onap.org/download/attachments/50202249/2019-04-09%20ONAP_LCM_API_Evolution_El_Alto.pptx?api=v2

Goals (Architecture Evolution)
  • Target is common LCM API in CCSDK usable by different controller personas to simplify for both clients and controller implementations
  • Support PNFs for applicable LCM operations in a consistent way
  • Enable use of CDS blueprint processor to customize behavior of LCM operations in the 'self-service' category
    • In ONAP R4, CDS can be used for pre/post-instantiation configuration. Generic and model-driven design should allow CDS usage to be extended for additional operations and use cases.
  • Evolution steps that preserve backwards compatibility for clients

Present at the Arch S/C Apr 9 (Tue) second presentation.

Use Cases

USE CASE/5G:

RAN (ORAN-3GPP) Standards harmonization with ONAP

marge.hillis

Vimal Begwani

fred feisullin

  • Orchestration at the Edge.
  • A1/O1/E2 communications. Edge to ENBs, Telemetry.
  • E2 will not have this info. O1 is I/F for PM counts. Not a management I/F.
  • WG3 (ORAN) is defining this.
  • ONAP w/ O1. Changes w/ O1 interface.
  • How to satisfy A1/O1 and in what time-frame.
  • U/C ORAN - ONAP harmonization. 3GPP ORAN ONAP.
  • Starting a new U/C in 5G. Marge, Vimal, Fred Feisullin
  • Edge inventory & topology. Transport BH consideration w/ real-time near-RT aspects
  • Akraino. MEC. Edge automation (Ramki).

Use Case WIKI: MOBILITY STANDARDS HARMONIZATION WITH ONAP

Use Cases

USE CASE/5G:

Licensing Management

Timo Perala

Samuli Kuusela

New U/C added to the 5G Use Cases for Licensing Management

Use case Wiki: LICENSING MANAGEMENT

(Oct 8 2019) Arch Samuli presented on Licensing Management. Object development. Modeling S/C.

Modeling work: ONAP R6 Modeling High Level Requirements

Use Cases

USE CASE/5G:

OOF / SON / PCI

N.K. Shankaranarayanan

PoC for December 2019?

SDN-R south-bound NetConf I/F w/ model

and also integration with Runtime DB work.

Use Cases

USE CASES:

BBS U/C Evolution

David Perez Caparros

Tim Carey

Chaker Al-Hakim

BBS Evolution - Slide set linked in R6 proposed U/C. List of proposals & functional requirements.

  1. Change Service - want to use ONAP platform.
  2. Full Closed Loop for Fault Management - CLAMP.
  3. Service Update API (SO) - will be developed

https://wiki.lf-onap.orgatlassian.net/wiki/download/attachments/6088750416362101/BBS_R5_v1.pptx?version=1&modificationDate=1554180715000&api=v2

Use Cases

USE CASES/5G:

PM Dictionary/FM MD GUI

marge.hillis
FM META DATA & PM DICTIONARY in R5
Use Cases

USE CASES/5G:

PNF S/W Upgrade

Zu Qiang

wangyaoguang

PNF software upgrade in R6 Frankfurt
Use Cases

USE CASES/5G:

Preonboarding/Onboarding

Benjamin Cheung

Zu Qiang

Michela Bevilacqua

PNF PREONBOARDING / ONBOARDING in R5
Use CasesUSE CASES:

IoT Service Creation

Atul Purohit

IoT Create Services on 5G

5G Use Cases in R6 Frankfurt

June 19, 2019

Use Cases

USE CASES:

Modeling gNB/5G RAN

Thinh Nguyenphu (Unlicensed)

Benjamin Cheung

Melanie Sater

Tracy Van Brakle

Martin Skorupski

Align , & harmonize , reconcile various information models to ONAP model:Expand & verify model and harmonize with the ONAP internal information & data model:

ETSI SOL001 ... 007 with ONAP internal Model, PNFD modeling (Model S/C), 5G Model (3GPP, RAN), ORAN (WGs, RAN), Open ROADM (reconfig optical add/drop multiplexer, Optical), ONF (Optical), ISOMII (Optical)
, OTCC (Optical transport config & control) -

Use Cases

 - Try a Use Case with extended ONAP model & real equipment.

ORAN Model PlugFest (Dec 2019)

Use Cases

USE CASES:

5G NRM (Network Resource Model) Configuration

wangyaoguang

Presented at the June 2019 June LFN DDF, titled as '5G Provisioning management service to NRM' 

(Oct 9 2019) Presented at CDS team and discussed with Yuriy and Seshu; presented at Resource Modeling S/C. Slides will be updated and re-presented.

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

Arch

Architecture S/C

PNF POB/OB Flow

Benjamin Cheung

Arch S/C Information Flows: Draft ONAP Information Flows

New Information flow for Preonboarding/Onboarding xNF packages/resources.

ARCHCOM: InfoFlow - Onboard Resource into SDC Flow

TSC

TSC:

PoC Definition

Benjamin Cheung

Alla.Goldner

POC definition
TSC

TSC/USE CASES:

Test Automation Progress

Benjamin Cheung

Alla.Goldner

Use Case Test Automation

Action Items: Use case subcommittee to reach the Dublin use case owner to provide the following information. what's the current percentage of testing automation regarding your use case and functional requirements; what will be the plan to be 100% and constraints (resources availability etc.)


R6 Frankfurt / M0M1

Use Case Tracking Template

Need the U/C teams to fill out the Dev. Impacts.

More Generalized Use Case Template (discussed w/ Model team):

Use Case Tracking Template and Use Case Template

VID: Service Models Browser Orchestration

James Forsyth

Former user (Deleted)

VID: Service Models browser - display orchestration type (macro / a`la carte) use-case.

This use-case requires us to extend the AAI data-model, with an additional field, related to Service Model.

This field will be used later on to indicate in VID the Service Model orchestration type.

A&AI Epic 2594

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAI-2594

Frankfurt Release Requirements

KEY PRESENTATIONS & OVERVIEWS & RECORDINGS

...

Oskar Malm

...

  • Target is common LCM API in CCSDK usable by different controller personas to simplify for both clients and controller implementations
  • Support PNFs for applicable LCM operations in a consistent way
  • Enable use of CDS blueprint processor to customize behavior of LCM operations in the 'self-service' category
    • In ONAP R4, CDS can be used for pre/post-instantiation configuration. Generic and model-driven design should allow CDS usage to be extended for additional operations and use cases.
  • Evolution steps that preserve backwards compatibility for clients

https://wiki.onap.org/download/attachments/50202249/2019-04-09%20ONAP_LCM_API_Evolution_El_Alto.pptx?api=v2

...

Former user (Deleted)

...

Visualizer for A&AI Model Layout

Use Case Realization Call: May 1, 2019

...

James Forsyth

...

A&AI developer Model Browser to navigate and viewing attributes, object types & edge view

Recording & Slides: Use Case Realization Call: May 8, 2019

...

Giulio Graziani

...





...

Frankfurt Release Requirements

KEY PRESENTATIONS & OVERVIEWS & RECORDINGS

List of U/C Realization calls from R6 U/C Wiki: Release 6 (Frankfurt) proposed use cases and functional requirements

DATETOPICPRESENTERDESCRIPTION
Apr 10, 2019Controller LCM API Evolution
Oskar Malm
  • Target is common LCM API in CCSDK usable by different controller personas to simplify for both clients and controller implementations
  • Support PNFs for applicable LCM operations in a consistent way
  • Enable use of CDS blueprint processor to customize behavior of LCM operations in the 'self-service' category
    • In ONAP R4, CDS can be used for pre/post-instantiation configuration. Generic and model-driven design should allow CDS usage to be extended for additional operations and use cases.
  • Evolution steps that preserve backwards compatibility for clients

https://wiki.onap.org/download/attachments/50202249/2019-04-09%20ONAP_LCM_API_Evolution_El_Alto.pptx?api=v2

May 1, 2019A&AI GraphGraph Visualizer

Former user (Deleted)

Visualizer for A&AI Model Layout

Use Case Realization Call: May 1, 2019

May 8, 2019A&AI Model Browser, Sparky
James Forsyth

A&AI developer Model Browser to navigate and viewing attributes, object types & edge view

Recording & Slides: Use Case Realization Call: May 8, 2019

May 15, 2019A&AI Run Time Browser (Sparky)
Giulio Graziani
A&AI Run-Time Browser
May 22, 2019Edge Automation Overview & Discussion

Ramki Krishnan

Central & Distributed Edge ONAP configuration.

Topics include: Onboarding, Instantiation, Edge Orchestration, A&AI, Architecture, Work-flows, Multi-Tenancy

Use Case Realization Call: May 22, 2019

May 29, 2019Modeling
S/C ,
, Use Case
Project Teams, Architecture
& Arch S/C Way of Working
Benjamin Cheung

Model S/C (Sub committee) contributions page:

Modeling sub-committee Contributions

https://

wiki

lf-onap.

onap

atlassian.

org

net/wiki/display/DW/Proposed+ONAP+Release+Process+Updates+for+Information+and+Data+Modeling

Jun 5, 2019Use Case slides for Dev. Forum
Benjamin Cheung
Use Case Realization Call: June 5, 2019
July 10, 2019R6: PNF Software Upgrade
Overview & Discussion

Zu Qiang

Ulas Kozat

wangyaoguang

ONAP Read the Docs/R4 Announcements

WIKI: PNF software upgrade in R6 Frankfurt Overview & Presentation

July 24, 2019R6: OOF/SON PCI Use Case Demo
, Overview & DiscussionN.K. Shankaranarayanan
NK ShankarOOF / PCI / SON Use
Case DemoAug 7, 2019
Case  Discussion and Overview

 

5G NRM
(Network Resource Model)
Configuration U/C Overviewwangyaoguang5G NRM (Network Resource Model) Configuration U/C Overview & Presentation

14,

 

ORAN Standards Harmonization
U/C Overview

marge.hillis

Vimal Begwani

ORAN Standards Harmonization U/C Overview & Presentation

21,

 

Modeling
Sub-Committee
S/C guidelines & Use Case Interactions

Andy Mayer

Hui Deng

Modeling S/C Process Wiki: Proposed ONAP Release Process Updates for Information and Data Modeling

with Use Case Tracking Template and Use Case Template

R6 Modeling

High Level Requirements Planning Page

Req Plan wiki: ONAP R6 Modeling High Level Requirements

Sept 4,

 

Licensing Management Overview

Timo Perala

Samuli Kuusela

Introduction of Licensing Management in R6
Sept

,

 

SDC & R6 Use Case Impacts DiscussionOfir SonsinoDiscussion with SDC PTL Ofir w/ the Use Case Teams and SDC commitments. See the summary Table for SDC impacting Use Cases.

 

VID & R6 U/C Discuss

Preparation for Technical Conference Antwerp


ittay

Use Case Teams

Discussion with VID PTL (Ittay Stern) for R6 Use Case Impacts discussion and commitments for VID impacting Use Cases

Preparing slides for Use Cases at the Technical Conference Antwerp (for 5G/PNF use cases)

 

A&AI & R6 Use Case Impacts Discussion

James Forsyth

Discussion with A&AI PTL (Jimmy Forsyth) and Chandra Cinthala for R6 A&AI Use Case Impacts discussion and commitments.

Use Case Realization Call: September 25, 2019

 

DCAE & R6 Use Case Impacts DiscussionVijay KumarDiscussion with DCAE PTL (Vijay Kumar) for R6 Use Case Impacts discussion and commitments for DCAE impacting Use Cases

 

M1 U/C discussionUse Case Teams

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.

 

PoC Planning & DiscussionTracy Van Brakle

Combination Plugfest & PoC 1st week of December bringing together subset of ONAP modules as SMO (svc mgmt orchestration) layer w/ other artifacts from ORAN S/W (LF). LF will publicize. Planned June 2020.

Co-Demo discussion Nokia & Ericsson: Plug Fest Planning Discussion Oct 28, 2019

 

RunTime Config DB (Data Persistency)

Benjamin Cheung

Joanne Liu Rudel

Sandeep Shah

Discussion of the RunTime DB Use Case in R6 Frankfurt which introduces a Common Service Data Layer for a data lake to store configuration and operational parameters.

Component & Flows:

ARC RunTime DB Component Description - R6 Frankfurt

ARCHCOM: InfoFlow - RunTime Config DB Information Flow

5G CONFIGURATION (RunTime DB)

CONFIGURATION PERSISTENCE SERVICE R6

 

OOF & R6 Use Case Impacts DiscussionShankar PN

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

 

SO & R6 Use Case Impacts Discussion

Seshu Kumar Mudiganti

Discussion with SO PTL (Seshu Kumar) for R6 Use Case Impacts discussion and commitments.

 

PoC Planning & DiscussionTracy Van BrakleSync up on the
Demo & PlugFest
Dec 5, 2019 ORAN/ONAP PlugFest & Demo

 

Network Slicing

Swaminathan Seetharaman

LIN MENG

Shankaranarayanan Puzhavakath Narayanan

Shankar PN

CMCC-Huawei-Tencent & Wipro-ATT-Amdocs joint Network Slicing proposal

 

No MeetingNo Meeting
x,

Discussion of Use Case Template for R7

Andy Mayer

Scott Blandford

Filling out, describing and creating the Wiki for a Use Case

Use Case Tracking Template and Use Case Template

Proposed Functional Template for Use Cases

x, 2019Release Manager DiscussionDavid McBride

Discussion with David McBride of the Linux Foundation, the R6 Release Manager regarding practices, wiki page updates, Jira dashboard and what is a use case?

Release Planning: Frankfurt

Frankfurt Release Requirements

SO USE CASE IMPACTS FOR R6

Frankfurt Release Requirements

PNF / Preonboarding Onboarding

Wiki Page: PNF/VNF PREONBOARDING / ONBOARDING in R6 Frankfurt

SUMMARY: No Impact

PNF / Plug and Play

Wiki Page: PNF PLUG and PLAY in R6 Frankfurt

Use Case Spreadsheet: Indicates Impact

Frankfurt Release Requirements : Indicates Impact

WIKI:

  • Refactor BPMN workflow. Clean up. (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?
  • 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.

SUMMARY: Refactoring BPMN Workflow

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-1838

PNF / Software Upgrade

Wiki Page: PNF software upgrade in R6 Frankfurt

Use Case Spreadsheet: Indicates Impact

Frankfurt Release Requirements : Indicates Impact

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.

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: -

  Jira LegacyserverSystem Jiracolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionserverId4733707d-2057-3a0f-ae5e-4fd8aff50176keySO-2070

 

MDONSXin Miao (Unlicensed)Presentation and discussion of Multi-domain Optical Network Services

 

Ctlr & R6 U/C ImpactsDan Timoney

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.

   

No MeetingNo MeetingNo meeting end of December due to Holidays & Vacations




x, 2019Discussion of Use Case Template for R7

Andy Mayer

Scott Blandford

Filling out, describing and creating the Wiki for a Use Case

Use Case Tracking Template and Use Case Template

Proposed Functional Template for Use Cases

x, 2019Release Manager DiscussionDavid McBride

Discussion with David McBride of the Linux Foundation, the R6 Release Manager regarding practices, wiki page updates, Jira dashboard and what is a use case?

Release Planning: Frankfurt

Frankfurt Release Requirements






SO USE CASE IMPACTS FOR R6

Frankfurt Release Requirements

key,summary,type,created,
PNF / Preonboarding Onboarding

Wiki Page: PNF/VNF PREONBOARDING / ONBOARDING in R6 Frankfurt

SUMMARY: No Impact

PNF / Plug and Play

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:  Seshu Kumar Mudiganti create a new story to make it more explicit

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-20711838
(Task)

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

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
key
SO
REQ-
2072
Jira Legacy
serverSystem Jira
columns
84

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:  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.

  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.

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-2071

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: -

 
Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-2070

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-2071

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-2072

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-2073

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-2091

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-2090

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-2089

PNF / Enable Schema Update once PNF software is updated

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-88

Wiki Page: PNF software upgrade in R6 Frankfurt

There is no SO impact for this requirement in Frankfurt.

PNF / Enhancement on PNF Software Upgrade with EM with Ansible

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-53

Wiki Page: PNF software upgrade in R6 Frankfurt

Frankfurt Release Requirements : Indicates Impact

This is one of the PNF upgrade scenarios.

SO development committed by Huawei.

PNF / PNF Software Upgrade with EM with Netconf

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-96

Wiki Page: PNF software upgrade in R6 Frankfurt

Frankfurt Release Requirements : Indicates Impact

This is one of the PNF upgrade scenarios.

SO development committed by Huawei.

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

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
key

SO

REQ-

2073 Jira LegacyserverSystem Jiracolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionserverId4733707d-2057-3a0f-ae5e-4fd8aff50176keySO-2091

76

Wiki Page: Configuration with NETCONF in Frankfurt/R6
Test only, no SO development in R6 for this feature.
For integration e2e test case, the latest PNF workflow will be used. It is possible that this WF will be updated by other release requirements during R6 development.
5G / 5G Service Modeling

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.  

5G / Bulk PM

5G / Bulk PM / PM Control

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
key
SO
REQ-
2090

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-2089

PNF / Configuration with NetConf
Wiki Page: Configuration with NETCONF in Frankfurt/R6
Frankfurt Release Requirements: Indicates Impact
WIKI: TBD Possible change to new type of building blocks for PNF config-assign and config-deploy actions.
This is TBD due to the answer from the refactoring of SO work in the PnP U/C.
Don't propose new functionality, try to understand if there is impact due to the answer from the refactoring of SO work in the PnP U/C. With orchestrator the PNF W/F since R4 is able to interact w/ controller. Should not be any change in that. Change W/F to building blocks to make them generic, if trying to use that might impact as both the code is changing. There is a presentation from Lukasz Grech.
SUMMARY: -
5G / 5G Service Modeling

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

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

SUMMARY: No Impact, Information Modeling work only in R6

Wiki Page: 5G Bulk PM in Frankfurt/R6

129

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)

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-2399

5G / PM Dictionary

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

SUMMARY: No Impact

5G / 5G FM Meta Data

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

SUMMARY: No Impact

5G / OOF SON (PCI)

Wiki Page: OOF (SON) in R5 El Alto, OOF (SON) in R6 Frankfurt

SUMMARY: No Impact

5G / E2E Network Slicing5G / 5G FM Meta DataWiki Page: FM META DATA & PM DICTIONARY in R6 Frankfurt

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

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.

  • 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: ChangesOriginal 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

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-
2399
5G / PM Dictionary

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

SUMMARY: No Impact

2281
(Epic)

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

5G / RAN ORAN 3GPP Standards Harmonization

Wiki Page: MOBILITY STANDARDS HARMONIZATION WITH ONAP

SUMMARY: No Impact

5G / OOF SON (PCI)/ Runtime Config DB , Data Persistency U/C

Wiki Page:

OOF

5G CONFIGURATION (

SON) in R5 El Alto, OOF (SON) in R6 Frankfurt

SUMMARY: No Impact

5G / E2E Network Slicing

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

Use Case Spreadsheet: Indicates Impact

WIKI: Wiki Indicates No Impact

SUMMARY: -

5G / NRM CM w/ RESTful HTTPSCCVPNWiki Page: CCVPN Use Case in Frankfurt Release

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

Frankfurt Release Requirements : Indicates Impact

WIKI:

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

SUMMARY: Impacts

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-2281

5G / RAN ORAN 3GPP Standards Harmonization

Wiki Page: MOBILITY STANDARDS HARMONIZATION WITH ONAP

SUMMARY: No Impact

5G / Runtime Config DB , Data Persistency U/C

Wiki Page: 5G CONFIGURATION (RunTime DB)

Use Case Spreadsheet: Indicates Impact

WIKI: Wiki Indicates No Impact

SUMMARY: -

5G / NRM CM w/ RESTful HTTPS

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

Frankfurt Release Requirements : Indicates Impact

WIKI:

  • 1. New BBs coding for PnP instantiation
  • 2. Enhance related workflowSpecifications API
  • 3. Add new NB API for instance management for pnf
  • 4.add workflow for modify/delete/query NRM config

SUMMARY: -

5G / Licensing Management

Wiki Page: LICENSING MANAGEMENT

SUMMARY: No Impact, Modeling & architecture work only for R6.

SERVICE RESOLVER

Wiki Page: Service Resolver

SUMMARY: No Impact ? (Wiki lists nothing) ??

SCALING

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.

Mobile Service Chaining & Service Selection

Wiki Page: MOBILE SERVICE CHAINING

SUMMARY: -

BBS

Wiki Page:

Use Case Spreadsheet: Indicates Impact

WIKI: Needs Investigation. Wiki page needs work.

SUMMARY: Needs Investigation

  • 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

5G / Licensing Management

Wiki Page: LICENSING MANAGEMENT

SUMMARY: No Impact, Modeling & architecture work only for R6.

SERVICE RESOLVER

Wiki Page: Service Resolver

Seshu has discussion w/ the U/C team. Know the impacts.  SO has impact but it is not in scope for R6; SO changes will be in a future release.

SUMMARY: changes Out of scope for R6

SCALING

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 

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-2316

Mobile Service Chaining & Service Selection

Wiki Page: MOBILE SERVICE CHAINING

SUMMARY: -

BBS

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.

CCVPN

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)  -  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)

Control Loop

Wiki Page: Control Loop Sub Committee Frankfurt Release Planning

Use Case Spreadsheet: Indicates Impact

WIKI:

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

SUMMARY: Needs Investigation

Control Loop

Wiki Page: Control Loop Sub Committee Frankfurt Release Planning

Use Case Spreadsheet: Indicates Impact

WIKI: doesn't show where SO is impacted.

SUMMARY: -

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.

Multi Domain Optical Service L0/L1 Orchestration

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 but not a BPMN change. Seshu wants to know the actual BPMN change.SUMMARY: Changescustom 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)

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-2432
CHANGE MANAGEMENT

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: --191"

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

HPAWiki Page: Continuation of HPA

Frankfurt Release Requirements: Indicates Test-Only

WIKI: Unclear, Wiki needs work.

SUMMARY: Needs InvestigationTest only.

RUN TIME SECURITY

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

K8S Based Cloud Region Support

Wiki Page: K8S based Cloud region support (Continue from R4)

Use Case Spreadsheet: Indicates Impact

Frankfurt Release Requirements : Indicates Test Only

WIKI:

  • All the changes are expected to be done in Multi-Cloud project. We don't expect any changes to API exposed by Multi-Cloud to the SO. Also, there are no changes expected in SDC to Multi-Cloud interface. All the work that was done SDC and SO will be good enough in R6.
  • There are some suggestions from the community to make "K8S workload support" as first class citizen and that may require changes to SDC and SO. But that is not planned for R6.

SUMMARY: Confirm Test only. Confirmed by Seshu.

DAaaS

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.

3rd Party Operational Domain Manager

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)

PREDISCUSSION CALL (OCT 31 2019)

...

DocumentFile



Use Case Realization Tracking Spreadsheet

View file
nameR6Frankfurt-UseCaseImpactsInteract_25Sept2019v4.xlsx
height250

SO refactoring BPMN workflow (slides from Lukasz Grech)


Multi Domain Optical Services L0/L1 orchestration (link to ppt slides) - Xin Miao (Unlicensed)

View file
nameMDONS_ONAP_R6_Impacts_v0.11.

pdf

pdf
height250

RECORDING for Pre-Meeting Oct 31, 2019

...

RecordingFILE
Zoom Video & Audio (MP4)

View file
namezoom_0.mp4
height250

Audio Only (M4A)

View file
nameaudio_only.m4a
height250

Playback (M3U)

View file
nameplayback.m3u
height250

Chat (Txt)

View file
namechat.txt
height250
View file
namemeeting_saved_chat.txt
height250