Purpose
This template is to be used for the “Parallel Deep Dive Sessions to Align with architecture / Use cases” at the may ONAP developers event
Instructions.
The purpose of each section is to translate the use cases and functional architecture into specific identified needs for the components, and to identify potential projects to be proposed. There are three parts to this exercise:
- Identify needs based on the use case and architecture on this module, and potential dependencies on other modules or external artifacts.
- Group these into projects. Consider that coding, documentation, and testing is required. Include an initial scope for the project.
- If time, mapping the needs into the projects.
The need identification table has the following columns
- Identified need: <slogan for the identified need>
- Brief need description: <a few sentences describing the need>
- Driver:<Related use case or architecture change, if any>
- Dependencies:<identify dependencies on other modules or artifacts (e.g. other onap module, models, …)
- Project: <If time, after the projects are identified, suggest in which project the need would best fit>
Time keeping suggestion: The exercise time is 45 minutes. A good practice would be to split into 20 minutes on need identification and 20 minutes on project proposals.
Exercise output.
ONAP Meeting Session name: <insert onap module name>
Need Identification:
Identified Need | Description | Driver | Dependencies | Project fit |
Security | Enabling centralized Authentication and Authorization. Enabling centralized User Management. Administrative tasks such as Role based access to Operations Management Framework (OMF) | ONAP Security | Portal, Policy, VID, SDC | ONAP Portal Enhancements |
Support for Orchestration of complex deployment, ONAP Optimization | On-boarding and supporting the ONAP controller access through Portal and E2E control (component instantiation/restart /stop/remove) flows for administrators. | Stability, Scalability, Performance | Portal, ONAP Controller/Orchestrator | Portal's new UI Applications |
Self service | Self-Service Environment to On-Board & Define New Functions / Services / Products on to portal. Request for Network Configuration Change, Execute workflow for network change. Model driven user interface for vCPE , VoLTE use cases. | Self service environment to add new components | Portal, ONAP Controller/VNF Change Management/Closed-Loop | Portal's new UI Applications |
OPEN-O CLI/GUI convergence | Merge OPEN-O GUI into ONAP Portal | Existing GUI reusability | Portal | ONAP CLI (ECOMP + OPEN-O merge) |
Project proposals.
[repeat for each project. Note: This is not a complete project proposal skeleton, only sufficient enough for this discussion]
Project 1:
Project Name: ONAP Portal Enhancements
- ONAP Portal Onboarded applications Repository under UI umbrella
Project Description
- This provides the basis for the portal framework and onboarding of portal applications
Scope:
- Portal SDK
- User management
- Security / Authentication / Authorization
- UI Application Onboarding / Management
Other:
- Identify baseline code (if any)
Project 2:
Project Name:
- Portal's new UI Applications
Project Description
- Separate applications provided by other projects as needed based on Portal SDK
Scope:
- Examples include VID, SDC
- GUI for vCPE, VoLTE
- Model driven user interface for vCPE , VoLTE use cases
- UI for ONAP Controller, change management
Other:
- Identify baseline code (if any)
Project 3:
Project Name:
- ONAP CLI (ECOMP + OPEN-O merger scope)
Project Description
- CLI is used to allow command line access to ONAP functionality
Scope:
- Automation of portal functions
- No visual component
- Commands for orchestration of ONAP functionality
- Merger between Open-O and OpenECOMP