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

Compare with Current View Page History

« Previous Version 8 Next »

Date

Attendees

DISCUSSION ITEMS LOG


CtgryItemWhoNotes

Pltfm


PLATFORM TOPICS:

Controller to NF Association

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

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)

Pltfm

PLATFORM TOPICS:

Controller LCM API Evolution

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

  • 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

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

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

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.onap.org/download/attachments/60887504/BBS_R5_v1.pptx?version=1&modificationDate=1554180715000&api=v2

Use Cases

USE CASES/5G:

PM Dictionary/FM MD GUI

FM META DATA & PM DICTIONARY in R5
Use Cases

USE CASES/5G:

PNF S/W Upgrade

PNF software upgrade in R6 Frankfurt
Use Cases

USE CASES/5G:

Preonboarding/Onboarding

PNF PREONBOARDING / ONBOARDING in R5
Use CasesUSE CASES:

IoT Service Creation

IoT Create Services on 5G

5G Use Cases in R6 Frankfurt

June 19, 2019

Use Cases

USE CASES:

Modeling gNB/5G RAN

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 that need transport models need some model consistency.

 - 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

yaoguang wang

Presented at the 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

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

POC definition
TSC

TSC/USE CASES:

Test Automation Progress

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 / M0

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

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 AAI-2594 - Getting issue details... STATUS





Frankfurt Release Requirements

KEY PRESENTATIONS & OVERVIEWS & RECORDINGS

DATETOPICPRESENTERDESCRIPTION
Apr 10, 2019Controller LCM API 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

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

Visualizer for A&AI Model Layout

Use Case Realization Call: May 1, 2019

May 8, 2019A&AI Model Browser, Sparky

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)A&AI Run-Time Browser
May 22, 2019Edge Automation Overview & Discussion

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 S/C Way of Working

Model S/C (Sub committee) contributions page:

Modeling sub-committee Contributions

https://wiki.onap.org/display/DW/Proposed+ONAP+Release+Process+Updates+for+Information+and+Data+Modeling

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

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 & DiscussionOOF / PCI / SON Use Case Demo
Aug 7, 20195G NRM (Network Resource Model) Configuration U/C Overviewyaoguang wang5G NRM (Network Resource Model) Configuration U/C Overview & Presentation
Aug 14, 2019ORAN Standards Harmonization U/C OverviewORAN Standards Harmonization U/C Overview & Presentation
Aug 21, 2019Modeling Sub-Committee guidelines & Use Case Interactions

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

Use Case Tracking Template and Use Case Template

R6 Modeling High Level Requirements Planning Page: ONAP R6 Modeling High Level Requirements

Sept 4, 2019Licensing Management OverviewIntroduction of Licensing Management in R6
Sept 11, 2019SDC & 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 Stern

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

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

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)

 

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 DiscussionDiscussion with SO PTL (Seshu Kumar) for R6 Use Case Impacts discussion and commitments.

 

PoC Planning & DiscussionTracy Van BrakleSync up on the Demo & PlugFest

 

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

 

No MeetingNo Meeting
x, 2019Discussion of Use Case Template for R7

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

SO-1838 - Getting issue details... STATUS

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

  SO-2070 - Getting issue details... STATUS

SO-2071 - Getting issue details... STATUS

SO-2072 - Getting issue details... STATUS

SO-2073 - Getting issue details... STATUS

SO-2091 - Getting issue details... STATUS

SO-2090 - Getting issue details... STATUS

SO-2089 - Getting issue details... STATUS

PNF / Configuration with NetConf
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

5G / Bulk PM

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.

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

SO-2399 - Getting issue details... STATUS

5G / PM Dictionary
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 Slicing

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

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

SO-2281 - Getting issue details... STATUS

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

CCVPN

Wiki Page: CCVPN Use Case in Frankfurt Release

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

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.

  • Will need some changes in SO to accomplish the decomposition of end to end optical service. More details need to be ironed out. > Xin Miao   will update the Wiki (it is outdated).

SUMMARY: Changes

SO-2432 - Getting issue details... STATUS
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: -

HPAWiki Page: Continuation of HPA

Frankfurt Release Requirements: Indicates Test-Only

WIKI: Unclear, Wiki needs work.

SUMMARY: Needs Investigation

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

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

DAaaS

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

Use Case Spreadsheet: Indicates Impact

WIKI: Needs work.

SUMMARY: Needs investigation

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

PREDISCUSSION CALL (OCT 31 2019)

A prediscussion call for the Nov 6, 2019 U/C Realization call was help with Seshu to discuss the SO impacts for R6 Use Cases.

ATTENDEES

SUPPORTING DOCUMENTATION

DocumentFile



Use Case Realization Tracking Spreadsheet

SO refactoring BPMN workflow (slides from Lukasz Grech)


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


RECORDING

RecordingFILE
Zoom Video & Audio (MP4)


Audio Only (M4A)


Playback (M3U)


Chat (Txt)


























  • No labels