...
Attendees
- Vimal Begwani
- Seshu Kumar Mudiganti
- Xin Miao
- Dongho Kim
- Fei Zhang
- John Quilty
- Prabhu Balan
- Swaminathan Seetharaman
- yaoguang wang
- Oskar Malm
- Sandeep Shah
- Fernando Oliveira
- Melanie Sater
- Marci Haas
- Gerard Hynes
- Fari Behi
- Raghavan Subramanian
- N.K. Shankaranarayanan
DISCUSSION ITEMS LOG
Ctgry | Item | Who | Notes | |||||||||||||
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? | ||||||||||||||
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)CONFIGURATION PERSISTENCE SERVICE R6 | ||||||||||||||
Pltfm | PLATFORM TOPICS: Controller LCM API Evolution | Goals (Architecture Evolution)
Present at the Arch S/C Apr 9 (Tue) second presentation. | ||||||||||||||
Use Cases | USE CASE/5G: RAN (ORAN-3GPP) Standards harmonization with ONAP |
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.
| ||||||||||||||
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 Cases | USE CASES: IoT Service Creation | IoT Create Services on 5G 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: and ONAP internal information & data model: ETSI 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) | ||||||||||||||
Use Cases | that need transport models need some model consistency. - Try a Use Case with extended ONAP model & real equipment.Use Cases | USE CASES: 5G NRM (Network Resource Model) Configuration | yaoguang wang | Presented at the June 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. | ||||||||||||||
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 / M0M1 | Need the U/C teams to fill out the Dev. Impacts. More Generalized Use Case Template (discussed w/ Model team): | 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
|
Frankfurt Release Requirements
KEY PRESENTATIONS & OVERVIEWS & RECORDINGS
Frankfurt Release Requirements
KEY PRESENTATIONS & OVERVIEWS & RECORDINGS
List of U/C Realization calls from R6 U/C Wiki: Release 6 (Frankfurt) proposed use cases and functional requirements
DATE | TOPIC | PRESENTER | DESCRIPTION |
Apr 10, 2019 | Controller LCM API Evolution |
| |
May 1, 2019 | A&AI GraphGraph Visualizer | Visualizer for A&AI Model Layout | |
May 8, 2019 | A&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, 2019 | A&AI Run Time Browser (Sparky) | A&AI Run-Time Browser | |
May 22, 2019 | Edge Automation Overview & Discussion | Central & Distributed Edge ONAP configuration. Topics include: Onboarding, Instantiation, Edge Orchestration, A&AI, Architecture, Work-flows, Multi-Tenancy | |
May 29, 2019 | Modeling, Use Case & Arch S/C Way of Working | Model S/C (Sub committee) contributions page: Modeling sub-committee Contributions | |
Jun 5, 2019 | Use Case slides for Dev. Forum | Use Case Realization Call: June 5, 2019 | |
July 10, 2019 | R6: PNF Software Upgrade | ONAP Read the Docs/R4 Announcements WIKI: PNF software upgrade in R6 Frankfurt Overview & Presentation | |
July 24, 2019 | R6: OOF/SON PCI Use Case Demo | NK Shankar | OOF / PCI / SON Use Case Discussion and Overview |
| 5G NRM Configuration U/C Overview | yaoguang wang | 5G NRM (Network Resource Model) Configuration U/C Overview & Presentation |
| ORAN Standards Harmonization | ORAN Standards Harmonization U/C Overview & Presentation | |
| Modeling S/C guidelines & Use Case Interactions | Modeling S/C Process Wiki: Proposed ONAP Release Process Updates for Information and Data Modeling with Use Case Tracking Template and Use Case Template R6 Modeling Req Plan wiki: ONAP R6 Modeling High Level Requirements | |
| Licensing Management Overview | Introduction of Licensing Management in R6 | |
| SDC & R6 Use Case Impacts Discussion | Ofir Sonsino | Discussion 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 | 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. | |
| DCAE & R6 Use Case Impacts Discussion | Vijay Venkatesh Kumar | Discussion with DCAE PTL (Vijay Kumar) for R6 Use Case Impacts discussion and commitments for DCAE impacting Use Cases |
| M1 U/C discussion | Use 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 & Discussion | Tracy 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 (Data Persistency) | 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 | |
| OOF & R6 Use Case Impacts Discussion | Shankar 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 Discussion | Discussion with SO PTL (Seshu Kumar) for R6 Use Case Impacts discussion and commitments. | |
- 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
Visualizer for A&AI Model Layout
A&AI developer Model Browser to navigate and viewing attributes, object types & edge view
Recording & Slides: Use Case Realization Call: May 8, 2019
Central & Distributed Edge ONAP configuration.
Topics include: Onboarding, Instantiation, Edge Orchestration, A&AI, Architecture, Work-flows, Multi-Tenancy
Model S/C (Sub committee) contributions page:
ONAP Read the Docs/R4 Announcements
WIKI: PNF software upgrade in R6 Frankfurt Overview & Presentation
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
VID & R6 U/C Discuss
Preparation for Technical Conference Antwerp
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)
Discussion with A&AI PTL (Jimmy Forsyth) and Chandra Cinthala for R6 A&AI Use Case Impacts discussion and commitments.
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 & Discussion | Tracy 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
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
Discussion with OOF PTL (Shankaranarayanan Puzhavakath Narayanan ) for R6 Use Case Impacts discussion and technical details for OOF impacting Use Cases
Filling out, describing and creating the Wiki for a Use Case
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?
SO USE CASE IMPACTS FOR R6
Frankfurt Release Requirements
Sync up on the Dec 5, 2019 ORAN/ONAP PlugFest & Demo | |||
| Network Slicing | CMCC-Huawei-Tencent & Wipro-ATT-Amdocs joint Network Slicing proposal | |
| No Meeting | No Meeting | |
| MDONS | Xin Miao | Presentation and discussion of Multi-domain Optical Network Services |
| Ctlr & R6 U/C Impacts | Dan Timoney | Discussion with Controller (APP-C, SDN-C) PTL (Dan Timoney) for R6 Use Case Impacts to Controller project. A technical discussion, Q&A, and U/C analysis. |
| No Meeting | No Meeting | No meeting end of December due to Holidays & Vacations |
x, 2019 | Discussion of Use Case Template for R7 | Filling out, describing and creating the Wiki for a Use Case | |
x, 2019 | Release Manager Discussion | David 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? |
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:
SUMMARY: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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: E#3a: Change to the onboarding (definition) of the BPMN workflow. 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?Need to sync on the VID implementation of 5G VID Instantiation/orchestration. VCPE also wants to use these building blocks. (SO-1838) E#3b: Migrate existing workflows to existing building blocks. (SO-1838) ACTION: Seshu Kumar Mudiganti create a new story to make it more explicit
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
PNF / PNF Software Upgrade using direct Netconf/Yang interface with PNF SUMMARY: Refactoring BPMN Workflow
SO-1838 |
| Wiki Page: PNF software upgrade in R6 FrankfurtUse Case Spreadsheet: Indicates Impact Frankfurt Release Requirements : Indicates Impact This is one of the PNF upgrade scenarios. Also includes development of some common functionality used by the other PNF upgrade scenarios. Use case with all scenarios 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: - post M4 (RC0-RC2) support. Expectation: Need to plan for different types of testing/bug fixing. Fwd'd to team. Question Seshu: asking how many people? Answer: not defined, there is a team expect enough resources. Seshu: problem when moving resources across teams, tech different and expectations different. expertise is insufficient across projects. To finish this need to identify people asap; Oskar: there is one experienced person with SO. yaoguang wang new API impacts in SO. Talked with Zu Qiang (Ericsson) in SO will provide new PNF custom W/F API. North-bound API to trigger PNF work-flow. Use existing W/Fs? Same principle as for VNFs. Look at the url will see PNF instead of VNF. CM requirements for PNF S/W upgrade. There is already W/F API for VNF. Propose to add a NEW API for PNF. Will discuss before M2. WIKI:
SUMMARY: -
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
PNF / Enable Schema Update once PNF software is updated
| Wiki Page: PNF software upgrade in R6 Frankfurt | SO-2071There is no SO impact for this requirement in Frankfurt. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
PNF / Enhancement on PNF Software Upgrade with EM with Ansible
| SO
| 2072||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Jira | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
server | ONAP JIRA | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb | key | SO-2073
| Wiki Page: PNF software upgrade in R6 Frankfurt Frankfurt Release Requirements : Indicates Impact This is one of the PNF upgrade scenarios. SO development committed by Huawei. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
PNF / PNF Software Upgrade with EM with Netconf
| SO
| 2091
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
96
Wiki Page: PNF software upgrade in R6 Frankfurt
Frankfurt Release Requirements : Indicates Impact
This is one of the PNF upgrade scenarios.
SO development committed by Huawei.
PNF / Configuration with NETCONF/ Secure Communication between xNFs and ONAP
Jira | |||||||
---|---|---|---|---|---|---|---|
|
|
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 RAN SERVICE MODELING & DEFINITION in R6 Frankfurt
The platform information model may impact SO as SO consumes the model.
SUMMARY: Need to investigate if model changes will impact SO consumption of the model. Ben will send Seshu presentation made to the modeling sub-committee.
5G / Bulk PM / PM Control
Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key REQ-129
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/connectioninstantiated. Will have dependency/connection.
For PNFs there might be a gap.
- QUESTION: (Marci Haas) This is a Use Case in December 5, 2019 to be demoed, are we on track? ANSWER: the new functionality will not be in the December Demo.
- 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: ChangesThere might be a dependency on the SO refactoring (See PnP U/C Epic #3a/#3b)
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
Wiki Page: FM META DATA & PM DICTIONARY in R6 Frankfurt
SUMMARY: No Impact
Wiki Page: FM META DATA & PM DICTIONARY in R6 Frankfurt
SUMMARY: No Impact
Wiki Page: OOF (SON) in R5 El Alto, OOF (SON) in R6 Frankfurt
SUMMARY: No Impact
Wiki Page: NETWORK SLICING PoC in R6 Frankfurt (Obsolete)
Frankfurt Release Requirements : Indicates Impact
WIKI: Original scope has undergone some changes, Swaminathan Seetharaman will discuss with SO the impacts.
- Enhance Request handler with Network Slicing instantiation
- Workflow for recursive service instantiation
- Handling of shared / dedicated services
- Store slice catalog items
SUMMARY: Impacts
Jira | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
|
need to create additional Jira, ... there is an Epic, and will need to create a story.
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: -
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
- Add new NB API for instance management for pnf
- add workflow for modify/delete/query NRM config
- Enhance related workflowSpecifications API:
- New NB API to trigger the custom workflow:
- Enhance configuration related BB to support NRM Configuration (*NOT* additional API):
- New native specific workflows(*NOT* additional API):
SUMMARY: Need some additional offline meetings with yaoguang wangSUMMARY: -
Wiki Page: LICENSING MANAGEMENT
SUMMARY: No Impact, Modeling & architecture work only for R6.
Wiki Page: Service Resolver
Seshu has discussion w/ the U/C team. Know the impacts. SO has impact but it is not in scope for R6; SO changes will be in a future release.
SUMMARY: changes Out of scope for R6SUMMARY: 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)
:
- CDS Actor Selection for Scale Out Use case (TechM)
SUMMARY: Wiki indicates Seshu has committed. No Jira created yet.
Yuriy Malakov may have already created tickets for this (check)
Benjamin Cheung Seshu Kumar Mudiganti Scale out with CDS Actor JIRA is
Jira | ||||||
---|---|---|---|---|---|---|
|
Wiki Page: MOBILE SERVICE CHAINING
SUMMARY: -
Wiki Page: BBS Broadband Service Use Case (Frankfurt)
Use Case Spreadsheet: Indicates Impact
WIKI: Needs Investigation.
Wiki page needs work.
SUMMARY: Needs Investigation. Seshu says there is no commitment right now for this U/C
Potential outage Chaker Al-Hakim . Scope is undefined. Not decided what will happen in R6 release.
Update from David Perez Caparros: BBS use case will focus on bug fixes and documentation in R6, as reported during the last F2F use case subcommittee meeting in Antwerp.
Wiki Page: CCVPN Use Case in Frankfurt Release
Use Case Spreadsheet: Indicates Impact
Frankfurt Release Requirements: ELINE Service over OTN NNI Indicates Test only
WIKI: Needs Investigation. Wiki page isn
't clear per Project Impacts.
Xin Miao - ASAIK there is no SO change. Confirm with Henry Yu (Huawei).
SUMMARY: Needs
to confirm with Henry Yu
There will likely be a Testing Effort (ELINE)
Wiki Page: Control Loop Sub Committee Frankfurt Release Planning
Use Case Spreadsheet: Indicates Impact
WIKI:
Event based Common API for Control Loop Operations, scaleup/scaledown instantiation and PNF PNP. Event based Common Notification messaging format for Control Loop Operations
APPC, SO, SDNC, VFC and SDNR to implement support of message and their flow from Policy
SUMMARY: Seshu Kumar Mudiganti has no commitment.
Potential Outage - Wiki Page indicates SO impact.
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. The two BPMN flow custom create end-to-end service instance. other is delete. Reuse these flows but to make some enhancements. there isn't a new or change in the W/F needed. We have to reuse existing flow and make model/configuration changes.
SUMMARY: ChangesCan meet off-line with Xin Miao
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
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: Seshu Kumar Mudiganti had a discussion Architecture Meeting but need follow-up.
Frankfurt Release Requirements: Indicates Test-Only
WIKI: Unclear, Wiki needs work.
SUMMARY: Needs InvestigationTest only.
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. Seshu Kumar Mudiganti is unaware of this change.
contact Srinivasa Addepalli
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. Confirmed by Seshu.
Wiki Page: Distributed Analytics as a Service (Continuation from R4)
Use Case Spreadsheet: Indicates Impact
WIKI: Needs work.
SUMMARY: Needs investigation. Seshu Kumar Mudiganti is not aware of this impact.
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. Only doing design time; run-time is not started. Contact Nishi Mathur (Telstra)
PREDISCUSSION CALL (OCT 31 2019)
...
Recording | FILE | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Zoom Video & Audio (MP4) |
| ||||||||||||
Audio Only (M4A) |
| ||||||||||||
Playback (M3U) |
| ||||||||||||
Chat (Txt) |
|