...
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 VESJIRA:
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 |
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
IMPACT: Dedicate discussion
WIKI PAGE: Intent-Based Network
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
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:| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
IMPACT: Test ONLY. Xin Miao (Unlicensed) has been in contact with Vijay.
VES flow. VES mapper. would not need code change. Initially thought.
A1 Policy Adaptor
ORAN/ONAP/3GPP Harmonization
Q: U/C & Non-functional Req. U/C help out on NFRs. U/C owner should contribute to some NFRs for components they are working on (TSC guidance). Need resources for "must have" DCAE NFRs. should allocate some space/work to help out.
| NFRs | Description | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Guilin release - non-functional requirements proposed list#ONAPmustcompleteupdateofthejavalanguage(fromv8-%3Ev11) | |||||||||
See non-functional requirements R7 page; |
| ||||||||
| Status | |||||||||
| colour | Yellow | ||||||||
| title | FR=Y NFR=N | ||||||||
| Status | |||||||||
| colour | Yellow | ||||||||
| title | FR=N NFR=Y | ||||||||
| Status | |||||||||
| colour | Green | title | FR=Y NFR=Y|||||||
COMPONENT IMPACTS TABLE
The following table shows the impacts of each requirement/use case per component
...