Page Comparison

(from Marge Hillis)

Agenda

David McBride---M4 Requirements discussion

Sylvia ---introduction to the ReadtheDocs  and its evolution.

M4 Requirements

https://lf-onap.atlassian.net/wiki/display/DW/Frankfurt+Release+Requirements

David reviewed the requirements and what he needs for the M4.

Several folks had follow on questions:

How do I mark my requirement if I am moving part of it out?  Requirements can be scaled back even later in the release if we need to extend some of the work into subsequent releases.  We need to be as accurate as possible in filling out the score card.  Need to be clear when a requirement is being descoped and need to be clear on the existing status of the requirement as it is documented and include notes if some things will be de-scoped e.g. if you are moving some things out but haven’t done it yet you are probably yellow not green and you should put in notes saying the parts you can’t do and that you intend to move them to the Guilin release.

If a requirement is moved do we have to get approval or can we assume its ok for the next release e.g. if move from Frankfurt is approval for Guilin automatic?  The answer was no you have to communicate to the architectural subcommittee and let them know that Frankfurt scope was reduced and you want to be able to add it to Guilin.  They will probably accept this but you have to review

We were not sure what the Use Case Action item was that you wanted David to discuss.  He suggested we re-schedule that.

READ THE DOCS

Sylvia provided an over view of the plans for the evolution of material from the WIKI to the read the docs site.

The reason for making this evolution in documentation is to provide an easier more organized way to find official information.  Much information will remain on the WIKI but critical Use Case information as it matures and stabilizes needs to move to the ReadTheDocs.  A task force is being started to evaluate what material should move from the WIKI.  One of the members of the audience (I didn’t’ catch the name) showed some examples of issues they were facing and with the difficulty in getting items to the Read the Docs.  Sylvia acknowledged that the documentation is a little sparse and that they are working on improving the documentation guidelines.  I asked if they might prepare a tutorial that they could film and post with the guidelines showing folks how to do some of the basic things and then providing resources for questions.  Sylvia seemed very willing to do that.  She said that they plan to have a Hackathon to improve the documentation and info on the hackathon is below.  If anyone from the use case realization team is interested in participating or perhaps in being a beta contributor to move a use case using their new documentation and tools she would very much welcome that.  Let her know if you want to get involved.  She is also willing to come back to your project utilization call and provide updates on their progress with the idea that perhaps we can partner to start to move use cases. https://lf-onap.atlassian.net/wiki/display/DW/March+11th+Documentation+Hackathon

A gentleman from Orange told us that the scale out use case is an excellent example of the sort of documentation we are looking for.  Below is a link to that Use Case.  He went through a bit of it and it seemed very impressive.

Good example of use cases is https://docs.onap.org/en/latest/submodules/integration.git/docs/docs_scaleout.html

PLATFORM TOPICS:

Controller to NF Association

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

PLATFORM TOPICS:

Data Persistency, RunTime DB

RunTime Config DB is now a R6 use case :

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

5G CONFIGURATION (RunTime DB)CONFIGURATION PERSISTENCE SERVICE R6

Jan 22 - CMNotify; SA5 3GPP Meeting. CMNotify domain. VES Event spec 7.1.1. Alok Gupta has not updated the VES event. On a leave of absence (Hip surgery). CMNotify is going to be done by Nokia. Sync with Sandeep Shah

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

• 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 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 CASE/5G:

Licensing Management

New U/C added to the 5G Use Cases Wiki: LICENSING MANAGEMENT

(Oct 8 2019) Arch Samuli presented on Licensing Management.

Modeling work: ONAP R6 Modeling High Level Requirements

Kevin Skaggs Proposed Licensing Platform Model

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:

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://wikilf-onap.onapatlassian.orgnet/wiki/download/attachments/6088750416362101/BBS_R5_v1.pptx?version=1&modificationDate=1554180715000&api=v2

USE CASES/5G:

PM Dictionary/FM MD GUI

USE CASES/5G:

PNF S/W Upgrade

USE CASES/5G:

Preonboarding/Onboarding

PNF PREONBOARDING / ONBOARDING in R5

VNF-SDK Artifact package security

IoT Service Creation

IoT Create Services on 5G

5G Use Cases in R6 Frankfurt

June 19, 2019

USE CASES:

Align & harmonize information models to ONAP model and 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:

5G NRM (Network Resource Model) Configuration

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

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

USE CASES:

PNF / Plug and Play

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:

PoC Definition

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

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

Frankfurt Release Requirements

POC & Plugfest in End June 2020

WINLAB? A1/O1 ORAN & ONAP Joint Plugfest

Panel Discussion - ? / Maybe in January-February

Setup. Bronze Release. / Slicing, Heart Beat-Health Check

Architecture Component Descriptions:

ONAP Architecture Component Description - Dublin

Architecture Flows:

Dublin ONAP Information Flows