Versions Compared

Key

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

...

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.
Need
  • Trying to
sync on the VID implementation of 5G VID Instantiation/orchestration. VCPE also wants to use these building blocks.

SUMMARY: Refactoring BPMN Workflow

Jira LegacyserverSystem Jiracolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionserverId4733707d-2057-3a0f-ae5e-4fd8aff50176keySO-
  • 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

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

  

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

2070

2090

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId

4733707d-2057-3a0f-ae5e-4fd8aff50176keySO-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

4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-2089

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

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 / Configuration with NetConf
WIKI: TBD Possible change to new type of building blocks for PNF config-assign and config-deploy actions
SUMMARY: -
5G / 5G Service ModelingWiki Page: 5G RAN SERVICE MODELING & DEFINITION

2399

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

, Information Modeling work only in R6

5G /
Bulk PM
E2E Network Slicing

Wiki Page:

5G Bulk PM in Frankfurt/R6
Workflow shall update status attribute in AAI when the VNF/PNF instance has been fully instantiated
  • 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

  • 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-
2339
2281

5G /

PM Dictionary

SUMMARY: No Impact

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

RAN ORAN 3GPP Standards Harmonization

Wiki Page:

FM META DATA & PM DICTIONARY in R6 Frankfurt

MOBILITY STANDARDS HARMONIZATION WITH ONAP

SUMMARY: No Impact

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

Wiki Page:

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

SUMMARY: No Impact

5G / E2E Network SlicingWiki Page: NETWORK SLICING PoC in R6 Frankfurt (Obsolete)

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 HTTPSWiki Page: 5G Network Resource Model (NRM) Configuration in R6 Frankfurt

RunTime DB)

Use Case Spreadsheet: Indicates Impact

WIKI: Wiki Indicates No Impact

SUMMARY: -

5G / NRM CM w/ RESTful HTTPS
  • 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
  • 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
  • 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: -

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

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:

3rd party ODM would change on 2 of BPMN. Need coordination. 3PODM post-poned changed, thus only this U/C will impact
  • 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 (Unlicensed)  will update the Wiki (it is outdated).

SUMMARY: Changes

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

HPAWiki Page: Continuation of HPA

Frankfurt Release Requirements: Indicates

Impact

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

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)

...

SUPPORTING DOCUMENTATION

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)


RECORDING

RecordingFILE
Zoom Video & Audio (MP4)


Audio Only (M4A)


Playback (M3U)


Chat (Txt)


...