Page Comparison

Wiki Page: PNF PLUG and PLAY in R6 Frankfurt

Use Case Spreadsheet: Indicates Impact

Frankfurt Release Requirements : Indicates Impact

WIKI:

• Refactor

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

  Clean up.

  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.

SUMMARY: Refactoring BPMN Workflow

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

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

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

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:

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

SUMMARY: Impacts

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:

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

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.

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.

SUMMARY: Changes

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