...
Ctgry | Item | Who | Notes |
Meeting Notes Discussion |
| ||
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: 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/5G: PNF S/W Upgrade | R7 Support xNF Software Upgrade in association to schema updates | |
Use Cases | USE CASES/5G: Preonboarding/Onboarding | R7 PNF Pre-onboarding / (onboarding) VNF-SDK Artifact package security | |
Use Cases | USE CASES: Modeling gNB/5G RAN | 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 | USE CASES: 5G NRM (Network Resource Model) Configuration | wangyaoguang | June 2019 LFN DDF, titled as '5G Provisioning management service to NRM' Presentation: 5G Network Resource Model (NRM) Configuration in R6 Frankfurt |
Use Cases | USE CASES: PNF / Plug and Play | Benjamin Cheung | PNF Plug and Play |
TSC | TSC/USE CASES: Test Automation Progress | Use Case Test Automation Action Items: Use case subcommittee to provide current percentage of testing automation regarding your use case and functional requirements | |
Release Tracking | R7 Frankfurt | All Team Members | Need the U/C teams to fill out the Dev. Impacts. More Generalized Use Case Template (discussed w/ Model team): |
Demos Plug- fest | Demo Plugfest | POC & Plugfest in September 2020 WINLAB? A1/O1 ORAN & ONAP Joint Plugfest Panel Discussion - Setup. Bronze Release. / Slicing, Heart Beat-Health Check | |
Architecture Topics | Architecture Topics | All Team Members | Architecture Component Descriptions and Architecture Flows: https://safratech.net/onapdocs/ |
Use Cases | Read the Docs | All members | DOCUMENTATION - Documentation (Read the Docs) - M1 - M4
"Are you referring to MS1 and the preliminary documentation? https://wikilf-onap.onapatlassian.orgnet/wiki/display/DW/Frankfurt+Documentation Multiple Repo / Use Cases are under Integration Repo VNFREQ has Repo / Verified U/C in Integration Repo Andreas Geissler - Discussed should put docs on the readthedocs (not in wiki) should have own Repo for Use Cases or Req sub-committee own repo |
Use Cases | Req / Use Case Way of Working Process (WoW) | All members | ONAP Use Case / Requirements Teams Process Way of Working (WoW) |
...
USE CASE REQUIREMENTS | DESCRIPTION & DISCUSSION | ||||||||
---|---|---|---|---|---|---|---|---|---|
CMPv2 ENHANCEMENTS | WIKI PAGE: R7 Certificate Management Protocol (CMPv2) JIRA: IMPACT: in discussion w/ Pawel Baniewski this feature had AAF dependency but AAF doesn't have PTL, so containers will be R6 only (no new software) Will use the R6 version of AAF cert-service container, no code impact but DCAE can progress. DCAE team requests output artifacts should be configurable (P12, PEM) DCAE Micro-service onboarding & design (MOD) - Work Internal to DCAE. Component specifications modified to accommodate parameters to execute the client, with certificate details. In DCAE changed deploying applications collectors, servers, analytics – understood by DCAE only, cloudify blueprint created and DMaaP configuration to deploy the service and connected w/ DMaaP topic. JSON/YAML internally to DCAE. Micro-service onboarding artifact. DCAE MOD. Cloudify Manager (Development) OPEN - two ways ext. jks files from AAF. initial work, come back on how to resolve that. | ||||||||
OOF SON PCI USE CASE | WIKI PAGE: R7 OOF SON Use Case JIRA: IMPACT: enhancement to SON handler.
(discuss w/ SON team) Swaminathan Seetharaman | ||||||||
3GPP ORAN ONAP STANDARD DEFINED VES EVENT | WIKI PAGE: ONAP/3GPP & O-RAN Alignment-Standards Defined Notifications over VES JIRA: IMPACT: New Standard Defined (stndDef) VES event for DCAE VES Collector. Uses VES 7.2 standard. Some of it has started and Progressing. Followup item will be presenting Dependency on ORAN-3GPP team publishing schema expected to be used by R7 Specs were just updated, this should be its next priority available in July 2020. From ONAP PoV need to doc ext.schema & spec that will be supported go into VNF-REQ project. A note stdDef, these are the ext. schema being supported by VES. New Schemas made official incorporate into DCAE VES collector for secondary validation. damian.nowak initiated w/ standards Reps. Marge will follow up for deliveries. Need by M2/M3 API freeze milestone. Crossing ONAP & O-RAN. Due: Presenting show a possibility of Mapping new standard def events into existing Fault-file ready, heartbeat VES events. transformational mapping inc. mapping mS into R8 or beyond. showing HOW it could be done, not proposing actual S/W deliveries until R8 beyond. VES 7.2 reviewed and approved in May appears in readthedocs. | ||||||||
E2E Network Slicing | WIKI PAGE: E2E Network Slicing Use Case in R7 Guilin JIRA: IMPACT: Key contact: Swaminathan Seetharaman | ||||||||
Configuration & Persistency Service | WIKI PAGE: Configuration & Persistency Service R7 JIRA: IMPACT: C&PS PoC is USING the StndDef VES Event. (test only??) Data from DMaaP, NameSpace 3GPP-Configuration (DMaaP topic) Coordinate become from DCAE and when the C&PS PoC can USE & Test ... Tony Finnerty & Toine Siebelink | ||||||||
Bulk PM / PM CONTROL Extensions | WIKI PAGE: Bulk PM/ PM Data Control Extension JIRA: IMPACT: Dedicate discussion | ||||||||
Intent Based Networking | WIKI PAGE: Intent-Based Network JIRA: IMPACT: Contact Huang ZongHe . Presented at the Architecture S/C. Possibly moved to POC status: Linked to: Arch S/C recordings: ONAPARC 2020 Meetings (Copy) Presentation https://jira.onap.org/secure/attachment/16127/16127_ONAP_Proposal_IBN+V1.7.pptx Discussion w/ China Telcom ... questions still to be reviewed. | ||||||||
MDONS EXTENSION | WIKI PAGE: (NONE) JIRA: IMPACT: Test ONLY. Xin Miao (Unlicensed) has been in contact with Vijay. VES flow. VES mapper. would not need code change. Initially thought. |
...
Recording | FILE | ||||||
---|---|---|---|---|---|---|---|
Zoom Video & Audio (MP4) |
| ||||||
Audio Only (M4A) |
| ||||||
Playback (M3U) |
| ||||||
Chat (Txt) |
|