...
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:
|
|
SUMMARY: Refactoring BPMN Workflow
SUMMARY: Refactoring BPMN Workflow
| ||||||||||
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:
SUMMARY: -
|
|
Jira Legacy | ||||||||
---|---|---|---|---|---|---|---|---|
|
Jira Legacy | ||||||||
---|---|---|---|---|---|---|---|---|
|
Jira Legacy | ||||||||
---|---|---|---|---|---|---|---|---|
|
| |||||||||||
PNF / Configuration with NetConf | 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 | ||||||||||
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.
SUMMARY: Changes
|
Jira Legacy | ||||||||
---|---|---|---|---|---|---|---|---|
|
| ||
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 Slicing | Wiki Page: |
NETWORK SLICING PoC in R6 Frankfurt (Obsolete) Frankfurt Release Requirements : Indicates Impact WIKI: |
- 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: Impacts
|
| ||
5G / |
SUMMARY: No Impact
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: |
SUMMARY: No Impact
5G / RAN ORAN 3GPP Standards Harmonization
Wiki Page: MOBILITY STANDARDS HARMONIZATION WITH ONAP
SUMMARY: No Impact
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: |
- 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 | ||||||||
---|---|---|---|---|---|---|---|---|
|
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: -
Wiki Page: LICENSING MANAGEMENT
SUMMARY: No Impact, Modeling & architecture work only for R6.
Wiki Page: Service Resolver
SUMMARY: No Impact ? (Wiki lists nothing) ??
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: MOBILE SERVICE CHAINING
SUMMARY: -
Wiki Page:
Use Case Spreadsheet: Indicates Impact
WIKI: Needs Investigation. Wiki page needs work.
SUMMARY: -
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: -
Wiki Page: Control Loop Sub Committee Frankfurt Release Planning
Use Case Spreadsheet: Indicates Impact
WIKI: doesn't show where SO is impacted.
SUMMARY: -
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
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.
SUMMARY: Changes
| ||||||||||
CHANGE MANAGEMENT | Wiki Page: Change Management Frankfurt Extensions Use Case Spreadsheet:Indicates Impact WIKI:
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: - | ||||||||||
HPA | Wiki 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:
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:
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:
SUMMARY: Impacts. Test only? Confirm. Need investigation |
PREDISCUSSION CALL (OCT 31 2019)
...
- Benjamin Cheung
- Xin Miao (Unlicensed)
- Oskar Malm
- Prabhu Balan
- Stavros Kanarakis
- Fei Zhang (Ericsson)
- Seshu Kumar Mudiganti
- Timo Perala
SUPPORTING DOCUMENTATION
Document | File | ||||||
---|---|---|---|---|---|---|---|
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 (Unlicensed) |
RECORDING
Recording | FILE |
---|---|
Zoom Video & Audio (MP4) | |
Audio Only (M4A) | |
Playback (M3U) | |
Chat (Txt) |
...