...
| USE CASE | LEAD CONTACTS / DESCRIPTION | WIKI | ||||||||||
| PNF Plug and Play | 5G - PNF Plug and Play | |||||||||||
| Integration Leads | ||||||||||||
| Requirement ID | Epic Jira for the requirement |
| ||||||||||
| SO Story Jira for PnP |
| |||||||||||
| Modeling Story jira for PnP |
| |||||||||||
| Architecture Sub-committee Jira tracker | Architecture sub-committee presentation |
| ||||||||||
Model Place / Geolocation / AAI Schema Meetings Register | PNFD/SDC AID/AAI Schema Modeling/5G Svc Model - R7 Discussion Papyrus model: | |||||||||||
Generic Information Element Definition for Geolocation Model | Generic Information Element Definition for Geolocation Model |
...
EXECUTIVE SUMMARY - This requirement will augment the work-flow to building block management within SO for Plug and Play operation. The continues the work started in R6. In R6, some of the SO work-flow to building block work was finished, and in R7 this is enhanced. The description of the "base" work which will be enhanced is shown in the wiki: PNF PLUG and PLAY in R6 Frankfurt
BUSINESS IMPACT - The enhancement to Plug and Play operation in ONAP is a critical business function because they enhance installation and commissioning activities.
...
| PROJECT | PTL | User Story / Epic | Requirement |
| A&AI | NO IMPACT | ||
| AAF | Jonathan Gathman → x | EPIC #1 (TEST ONLY / Integration) CMPv2 - Enhanced Secure X.509 Certificate support (email from Damian Nowak (Nokia) suggests to remove this dependency - testing will occur with REQ-321) REQ-318 PNF Plug & Play in R7 I think, we need to remove the dependency to AAF for REQ-318. REQ-318 covers mainly work in the SO component. Looking at PNF PNP feature E2E we might have some relation to REQ-321, but no strict dependency. Perhaps some AAF dependency was mentioned in REQ-318, before REQ-321 was created. I`d remove the AAF dependency from REQ-318 actually. | |
| APPC | NO IMPACT | ||
| CLAMP | NO IMPACT | ||
| CC-SDK | NO IMPACT | ||
| DCAE | NO IMPACT | ||
| DMaaP | NO IMPACT | ||
| External API | NO IMPACT | ||
| MODELING | NO IMPACT | ||
Multi-VIM / Cloud | NO IMPACT | ||
| MUSIC | bharathb → (Empty) | NO IMPACT | |
| OOF | NO IMPACT | ||
| POLICY | NO IMPACT | ||
| PORTAL | NO IMPACT | ||
| SDN-C | EPIC #3 Licensing Management flow w.r.t. PnP (q.v. Licensing Management Use Case) (Dependency) Enhancements for requesting License Key File (LKF) & Licenses from License Service (message exchange) | ||
| SDC | NO IMPACT | ||
| SO | EPIC #2 Workflow to Building Block Development and integration BB execution Framework, extended to understand PNFs. Preparing input object used for different BBs. Framework needs to take into PNFs. (Possible debug/work) (Testing & Integration Work). Environment where this is run Model parameters added, address the right CDS Blueprint. | ||
| VID | NO IMPACT | ||
| VF-C | → Yuanhong Deng | NO IMPACT | |
| VNFRQTS | NO IMPACT | ||
| VNF-SDK | NO IMPACT | ||
| CDS | NO IMPACT |
List of PTLs:Approved Projects
*Each Requirement should be tracked by its own User Story in JIRA
...