| Table of Contents |
|---|
Overview
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Honolulu |
| Project Lifecycle State | Mature. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information |
| Participating Company | AT&T, Nokia, Ericsson, Wipro, ChinaMobile, T-Mobile |
Scope
What is this release trying to address?
...
| REQ# | DCAE Commit Status | DCAE Impact Assessment | DCAE JIRA # |
| REQ-422 - Bulk PM / PM Data Control Improvements | YES | PMSH enhancement for dynamic filter/subscription change Commitment from Ericsson | DCAEGEN2-2541 |
| NA (Backlog) | YES | MOD updates Commitment from AT&T | |
| NA (Backlog) | YES | Generic mechanism to attach K8S ConfigMaps to DCAE apps. through spec/bp-gen/plugin (VES and DFC) Commitment from Nokia | |
| NA (Backlog) | YES | BP-gen Enhancements
Commitment from Nokia | |
| NA (Backlog) | Stretch | VESCollector Enhancements – Event publish order issue Commitment from Nokia | |
| NA (Backlog) | Stretch | Plugin path/load optimization: Taking release from PATH on raw/plugin repo location (rely on version) and update bootstrap/cloudify build | |
| NA (Backlog) | Stretch | Eliminate use of Consul service discovery in DCAE | DCAEGEN2-1786 |
...
| REQ# | DCAE Commit Status | DCAE Impact Assessment | DCAE JIRA # |
| REQ-479 - DCAE Transformation to support Helm | YES |
Commitment from AT&T, Independent Contributors | |
| REQ-478 - PoC - TOSCA Defined Control Loop on Honolulu Release | NO | Need more info | |
| REQ-470 - DCAE extension for collecting files from HTTP servers | YES | DFC Enhancement Commitment from Nokia | DCAEGEN2-2517 |
...
| REQ# | DCAE Commit Status | DCAE Impact Assesment | DCAE JIRA # |
| REQ-438 - COMPLETION OF JAVA LANGUAGE UPDATE (v8 → v11) | YES | Require exception for MOD/genprocessor/designtool/nifi-registry Risk #6 (Honolulu Risks) | |
| REQ-437 - COMPLETION OF PYTHON LANGUAGE UPDATE (v2.7 → v3.8 | YES |
Commitment from T-mobile, Independent contributon Risk #7 (Honolulu Risks) |
...
Platform Maturity (i.e., S3P items) Guilin Honolulu Release Platform Maturity
Green color → Target level ( details see Platform Maturity below)
- Performance: Level 1
- Stability: Level 2
- Resiliency: Level 2
- Security: Level 1+
- Scalability: Level 1
- Manageability: Level 1+
- Usability: Level 1+
...
| Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments |
|---|---|---|---|---|
| Performance | 1 | 1 |
| |
| Stability | 2 | 2 |
| |
| Resiliency | 2 | 2 |
| |
| Security | 1 | 1+ (Most DCAE components are complaint; will address remaining in Honolulu based on resource availability) |
| |
| Scalability | 1 | 1 |
| |
| Manageability | 1 | 1+ (Except logging, all other requirements are met) |
| |
| Usability | 1 | 1+ |
|
...
List the API this project is expecting from other projects. 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.
...
Testing and Integration Plans
- Unit Test addition will be enforced part of new code submission; all components are required to maintain 55% codecoverage at the minumum.
- Functional test plan
- CSIT tests will continue to be supported for existing componentsPairwise testing will be done in the WindRiver Dev lab similar to what was done in last releasecomponents and new components
- DCAE has number of CSIT - https://jenkins.onap.org/view/CSIT/; these will be continued to be validated during course of development for this release.
- Pairwise testing will be done in the WindRiver Dev lab; below wiki page captures the test planned
- DCAE also has number of Smoke test (Example - https://logs.onap.org/onap-integration/daily/onap_daily_pod4_master/01-18-2021_08-01/) enabled for several components/flows; these test are validated part of gating for new container releases
- Bulk-PM
- HV-VES
- VES
- PRH flow
Gaps
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.
...
| Risk identified | Mitigation Plan | Contingency Plan |
|---|---|---|
With Cloudify 3.x support releated by Cloudify under 5.1.1, DCAE CM pod upgrade is targetted for H release. This will be major upgrade requiring extensive regression. For any issues identified - may need to coordinate with Cloudify which could span beyond H release timeframe | Based on severity of issue - we'll assess if new continairs can be released for H release or if need to be withheld. | None |
| Due to upstream dependency on NIFI project, some of MOD (NiFI) components (designtool/gen-processor/nifi-registry) will remain in java 8 | Continue Guilin version |
Resources
Fill out the Resources and Repositories (Deprecated) centralized pagePlease see the INFO.yaml files associated with each repo as the authoritative sources of information. https://gerrit.onap.org/r/admin/repos/q/filter:dcae
Release Milestone
The milestones are defined at the Release Planning (legacy): Honolulu and all the supporting project agreed to comply with these dates.
...