...
| TOPIC | DESCRIPTION | WIKI PAGE | ||||||||
| Requirements Proposal | This is a link to the requirements proposal made on the Requirements Sub-committee | Honolulu release - functional requirements proposed list | ||||||||
| Architecture S/C info | Information on the Architecture sub-committee presentation |
| ||||||||
| Architecture S/C Review Info | Architecture Review Presentation made | |||||||||
| Prior Project "Base" Wiki | Link to the "base" wiki for the Use Case, or work from a prior release. | |||||||||
| Requirements Jira (REQ-###) Ticket | Link to the REQ Jira ticket for this use case |
| ||||||||
| Key Use Case Leads & Contacts | USE CASE LEAD: Benjamin Cheung , damian.nowak USE KEY CONTACTS: Lead Integrator Krzysztof Kuzmicki | |||||||||
| Meetings Register & Recordings | Link to PnP Use Case Team meetings. | N/A |
BUSINESS DRIVER
This section describes Business Drivers needs. These business drivers are presented on the Requirements Sub-committee and should also be put into the release requirements sub-committee page.
Executive Summary - (Give a short description of your Use Case, the "Executive 2 min elevator pitch", this describes the "WHAT")
Business Impact - (This is the Business Impact which describes why this use case is important from a business perspective, this describes the "WHY") - This requirement will introduce VID work to complement the work-flow to building block management work in SO for Plug and Play. The continues the work started in R6 and R7 where the SO work-flow to building block work was finished. The description of the "base" work was done in R6/R7 and can be found in the PnP pages for those releases. In R8, VID software "front end" will be added to allow for a user to more easily use the SO Building Blocks.
Business Impact - The enhancement to Plug and Play operation in ONAP is a critical business function because they enhance installation and commissioning activities.
Business Markets - (This is the marketing analysis, which can include but not limited to applicable markets, domains, marketing projections, this can describe the "WHERE").This project applies to any domain (wireless, transport, optical, and wireline) that ONAP may manage. It is not a market or geographical specific capability.
Funding/Financial Impacts - (The Funding requirements and Financial impacts can describe the financial savings, or CAPEX, OPEX impacts for a Use Caseplug and play project has Operating Expense (OPEX) savings for operators because of the ability to saving time and expenses during installation and commissioning and contributes towards ZTM (Zero touch management).
Organization Mgmt, Sales Strategies- (It is suggested that you use the following wording): -There is no additional organizational management or sales strategies for this use case requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider. (This would typically describe the "WHO", but because use cases are all deployed with ONAP itself, these two areas come with the actual ONAP deployment and uses the organizational management and sales strategies of a particular service provider's ONAP deployment)
Development Status
| PROJECT | PTL | User Story / Epic | Requirement |
| A&AI | No Impact | ||
| AAF | No Impact | ||
| APPC | No Impact | ||
| CLAMP | No Impact | ||
| CC-SDK | No Impact | ||
| DCAE | No Impact | ||
| DMaaP | No Impact | ||
| External API | No Impact | ||
| HOLMES | No Impact | ||
| MODELING | STORY #1 - Place Location Instance creation & association. | Analysis of the Place Model reviewed in the Modeling Sub-committee. Model Contribution. Information Complex object PIM is used to track and association the "location" of a data center for a VNF. When a BTS gNB is registered with ONAP, we want to use the PLACE Model instance to create/associate. DU (PNF) sends a pnfRegistration VES event. AssignpnfBB (BB) the A&AI entry is created. (AAI SETUP) (a) where it is created and where it is updated (AAI UPDATE) (b) ConfigAssignPnf (BB) what is run AFTER the PRH receives the pnfRegistration VES event and published a PNFready onto the DMaaP | |
Multi-VIM / Cloud | No Impact | ||
| OOF | No Impact | ||
| OOM | No Impact | ||
| POLICY | No Impact | ||
| PORTAL | No Impact | ||
| SDN-C | No Impact | ||
| SDC | No Impact | ||
| SO | No Impact | ||
| VID | STORY #2 - VID development for SO BB backend | VID development for SO BB Instantiations screens in VID Modern UI for PNFs they are currently empty. Left (model components) / Right pane (instance components) – service PNF instances Today Left pane is blank, need to enable that to setup parameters for PNF instance. Similar to VNF (but with reduce scope). Adapt the SO API built in R7. Building the PNF instantiation screens within VID. The corresponding VNFs already exist, and likely the update will look at these and modify and adapt them to the PNF. | |
| VF-C | 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
EPIC #1 VID Development
VID development will be done in R8.
VID development for SO BB
Instantiations screens in VID
Modern UI for PNFs they are currently empty.
Left (model components) / Right pane (instance components) – service PNF instances
Today Left pane is blank, need to enable that to setup parameters for PNF instance. Similar to VNF (but with reduce scope).
Adapt the SO API built in R7.
Building the PNF instantiation screens within VID.
The corresponding VNFs already exist, and likely the update will look at these and modify and adapt them to the PNF.
Create orchestration PNF forms which allow us to create
Requests towards SO GR / API.
Following SO Building Blocks
Implemented on SO side.
Know what we need to send to SO
Creating SO API request
(already exists from R7)
NEW: VID calling SO API
Modifying VID, ask instance name
Ask relevant parameters. Create SO API
VID development for PnP
EPIC #2 PLACE MODEL ANALYSIS
The Place model is at: Proposed Location Model
The R8 investigation:
USE CASE DIAGRAM
...