Overview
The content of this template is expected to be fill out for M1 Release Planning Milestone.
| Project Name | Portal Platform |
|---|---|
| Target Release Name | R4 Dublin Release |
| Project Lifecycle State | Incubation. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information |
| Participating Company | AT&T, ChinaMobile, IBM, Amdocs |
Scope: The scope of this release will be for the Portal Platform to support the below list: (provided the lead developers names who will be providing status on these committed features in weekly scrums)
5G Usecase Impacts on Portal platform (AT&T resources - Leimeng Shi )
New features (Chinamobile , AT&T, IBM resources)
House Keeping (AT&T, Amdocs resources)
Test Automation (IBM resources partially committed - Sireesh Chintamani )
Not-in-Scope: Please check Gaps.
Describe the use case this release is targeted for (better if the reference to customer use case).
Portal support top menu for "5G PNF Plug and Play" use case.
Supporting 5G use case, Internationalization language support, and technology stack upgrade is the MVP for this release.
List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.
Indicate at a high level the longer term roadmap. This is to put things into the big perspective.
Requirements for Dublin release - road map
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.
| Deliverable Name | Deliverable Description |
|---|---|
| Portal platform | Docker image of the application |
| SDK libraries | artifacts for onboarding applications components |
List all sub-components part of this release.
Activities related to sub-component must be in sync with the overall release.
Sub-components are repositories are consolidate in a single centralized place. Edit the Release Components name for your project in the centralized page.
List the other ONAP projects your depends on.
Components involved in 5G usecases that requires functional menus on the Portal platform. So, far SDC, VID, AAI are identified.
UsecaseUI for internationalization feature contribution.
At that stage within the Release, the team is expected to provide more Architecture details describing how the functional modules are interacting.
Block and sequence diagrams showing relation within the project as well as relation with external components are expected.
Anyone reading this section should have a good understanding of all the interacting modules.
Refering to CII Badging Security Program and Platform Maturity Requirements, fill out the table below by indicating the actual level , the targeted level for the current release and the evidences on how you plan to achieve the targeted level.
Portal's maturity requirements status is maintained for Dublin release here - Portal R4 Dublin - Integration Test Plans
List the API this release is expecting from other releases.
Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.
Prior to the delivery date, it is a good practice to organize an API review with the API consumers.
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
API this release is delivering to other releases.
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
| InternationalizationAPIs | To support language and locale | M3 | M4 | UsecaseUI team to contribute the details as they collaborating with Portal team on this requirement. *Multi-Language Functionality API List:
|
Third Party Products mean products that are mandatory to provide services for your components. Development of new functionality in third party product may or not be expected.
List the Third Party Products (OpenStack, ODL, RabbitMQ, ElasticSearch,Crystal Reports, ...).
| Name | Description | Version |
|---|---|---|
| MariaDB | The MariaDB is the repository that holds all the policies, templates, PDP group, and deployment information. | 10.0 |
| Nexus | The Nexus repository holds all the currently deployed Operational (i.e. Drools policies) and their dependent artifacts. | 2.14.2-01 |
| ElasticSearch | Used to search text within policy. | 5.4.0 |
| Ubuntu | Operating system | 14.04 |
In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.
Provide a description of the testing activities (unit test, functional test, automation,...) that will be performed by the team within the scope of this release.
Describe the plan to integrate and test the release deliverables within the overall ONAP system.
Confirm that resources have been allocated to perform such activities.
JUnit tests: 70% code coverage is the goal for all repositories without javascript.
If resources become available, we will add more CSIT test cases.
This section is used to document a limitation on a functionality or platform support. We are currently aware of this limitation and it will be delivered in a future Release.
List identified release gaps (if any), and its impact.
| Gaps identified | Impact |
|---|---|
Security (No committed resources)
New features (No committed resources)
Address ONAP Platform Maturity Guidelines (No committed resources)
House Keeping (No committed resources)
| Updated in Dublin Risks Risk#3 - Security impact on Policy, VID apps that use portal/sdk regarding addressing NexusIQ security issues and AAF integration which is not committed by Portal team so far due to lack of resources; Risk#4 - Impacts Dublin platform maturity requirements (Footprint Optimization, Logging Capabilities). Also, OOM deployment is impacted if the DB scaling changes are not supported by Portal team; also the changes for simplification of etc/hosts entries impacts the OOM deployment which is not committed by Portal team so far due to lack of resources. |
Provide a link toward the list of all known project bugs.
List the risks identified for this release along with the plan to prevent the risk to occur (mitigation) and the plan of action in the case the risk would materialized (contingency).
| Risk identified | Mitigation Plan | Contingency Plan |
|---|---|---|
| Resources | Actively seeking community support. | Current resources are not enough to satisfy even the Highest Priority Epics |
Fill out the Resources Committed to the Release centralized page.
The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.
This section is optional and may be used to document internal milestones within a project team or multiple project teams. For instance, in the case the team has made agreement with other team to deliver some artifacts on a certain date that are not in the release milestone, it is recommended to provide these agreements and dates in this section.
It is not expected to have a detailed project plan.
| Date | Project | Deliverable |
|---|---|---|
| To fill out | To fill out | To fill out |
The Documentation project will provide the Documentation Tool Chain to edit, configure, store and publish all Documentation asset. |
If this project is coming from an existing proprietary codebase, ensure that all proprietary trademarks, logos, product names, etc. have been removed. All ONAP deliverables must comply with this rule and be agnostic of any proprietary symbols.
FOSS activities are critical to the delivery of the whole ONAP initiative. The information may not be fully available at Release Planning, however to avoid late refactoring, it is critical to accomplish this task as early as possible.
List all third party Free and Open Source Software used within the release and provide License type (BSD, MIT, Apache, GNU GPL,... ).
In the case non Apache License are found inform immediately the TSC and the Release Manager and document your reasoning on why you believe we can use a non Apache version 2 license.
Each project must edit its project table available at Project FOSS.
The project team comply with the ONAP Charter.
Fill out and provide a link toward the centralized Release Artifacts.