| 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) | TBCYES | Generic mechanism to attach K8S ConfigMaps to DCAE apps. through spec/bp-gen/plugin (VES and DFC) Commitment from Nokia | |
| NA (Backlog) | TBCYES | BP-gen Enhancements
Commitment from Nokia | |
| NA (Backlog) | TBCStretch | 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-1786NA |
Honolulu POC (
...
DCAE impact)
...
Honolulu POC (DCAE impact)
| REQ# | DCAE CommitREQ# | 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 | TBCNO | TBANeed 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-443 - CONTINUATION OF CII BADGING SCORE IMPROVEMENTS FOR SILVER LEVEL | TBCStretch | TBA | DCAEGEN2-2570 | |
| REQ-441 - LOGS MANAGEMENT - PHASE 1: COMMON PLACE FOR DATA | NO | TBANeed more info | ||
| REQ-439 - CONTINUATION OF PACKAGES UPGRADES IN DIRECT DEPENDENCIES | YES | Tcagen2, DFC, RESTConf, VES, InventoryAPI, MOD-runtimeAPI, Mapper, PM-Mapper, PRH, SON-Handler | DCAEGEN2-2551 | |
| REQ-432 - IPv4/IPv6 dual stack support in ONAP (Honolulu) | TBC (based on resource)YES | CFY Plugin to support IPv6 service exposure + VES Spec updates Commitment from Nokia | DCAEGEN2-2477 | |
Global Requirements
| 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) |
Note: The above commitment is consistent with Honolulu Impact View per Component (as of 1/19/2021)
New Services introduced for this release
...
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+
...
In addition to existing platform/service component, following new components are targeted for Honolulu.
- Level 0: no performance testing done
- Level 1: baseline performance criteria identified and measured (such as response time, transaction/message rate, latency, footprint, etc. to be defined on per component)
- Level 2: performance improvement plan created
- Level 3: performance improvement plan implemented for 1 release (improvement measured for equivalent functionality & equivalent hardware)
2
- Level 0: none beyond release requirements
- Level 1: 72 hour component-level soak test (random test transactions with 80% code coverage; steady load)
- Level 2: 72 hour platform-level soak test (random test transactions with 80% code coverage; steady load)
- Level 3: track record over 6 months of reduced defect rate
- 0 – none
- 1 – manual failure and recovery (< 30 minutes)
- 2 – automated detection and recovery (single site)
- 3 – automated detection and recovery (geo redundancy)
1+ (Most DCAE components are complaint; will address remaining in Honolulu based on resource availability)
- Level 0: None
- Level 1: CII Passing badge
- Including no critical and high known vulnerabilities > 60 days old
- Level 2: CII Silver badge, plus:
- All internal/external system communications shall be able to be encrypted.
- All internal/external service calls shall have common role-based access control and authorization using CADI framework.
- Level 3: CII Gold badge
1
- Level 0: no ability to scale
- Level 1: supports single site horizontal scale out and scale in, independent of other components
- Level 2: supports geographic scaling, independent of other components
- Level 3: support scaling (interoperability) across multiple ONAP instances
1+ (Except logging, all other requirements are met)
| Deliverable | Repository | Maven Group ID | Components Description |
ONAP Dependencies
List the other ONAP projects you depend on.
DCAE depends on the the following components as part of the general ONAP architecture:
- AAI: DCAE MS retrieves and updates VNF data from/to AAI
- DMaaP: Message bus for communication with other components in the solution
- Policy - For managing application configuration policy
- CLAMP - For CL flow related MS instantiation and configuration
- OOF - For SON handler support
Architecture
High level architecture diagram
At that stage within the Release, the team is expected to provide more Architecture details describing how the functional modules are interacting.
Indicate where your project fit within the Amsterdam architecture diagram_1.0.0.pptx.
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.
Platform Maturity
Refering to 2017-06-28 CII badging for ONAP.pptx and Platform Maturity Requirements (aka Carrier Grade), 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.
Components Description | ||
| KPI Computation MS | https://git.onap.org/dcaegen2/services/tree/components/kpi-computation-ms (introduced as new subproject under existing repo) | |
| VES-OpenAPI-Manager | https://gerrit.onap.org/r/admin/repos/dcaegen2/platform/ves-openapi-manager (New repo) | |
DCAE-service-policy-Sync | https://git.onap.org/dcaegen2/deployments/tree/dcae-services-policy-sync (introduced a new subproject/module under existing repo) | REQ-479 |
ONAP Dependencies
List the other ONAP projects you depend on.
DCAE depends on the the following components as part of the general ONAP architecture:
- AAI: DCAE MS retrieves and updates VNF data from/to AAI
- DMaaP: Message bus for communication with other components in the solution
- Policy - For managing application configuration policy
- CLAMP - For CL flow related MS instantiation and configuration
- OOF - For SON handler support
Architecture
High level architecture diagram
At that stage within the Release, the team is expected to provide more Architecture details describing how the functional modules are interacting.
Indicate where your project fit within the Amsterdam architecture diagram_1.0.0.pptx.
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.
Target Architecture (REQ-479)
Platform Maturity
Refering to 2017-06-28 CII badging for ONAP.pptx and Platform Maturity Requirements (aka Carrier Grade), 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.
| 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.
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
| SDC model distribution API | API for retrieving TOSCA model of close loop | Currently Available | To fill outCurrently Available | Link toward the detailed API description |
| Policy Engine | API for retrieving configuration policy updates | Currently Available | Currently Available | NA |
| Policy (PDP) | API to push DCAE MS configuration/policy models | Currently Available | Currently Available | |
| A&AI | API invoked for information enhancements | Currently Available | Currently Available | |
| DMaaP Message Router | API for topic publish / subscribe | Currently Available | Currently Available | |
| DMaaP Bus Controller | DMaaP Bus Controller is a part of DMaaP that provides topic provisioning; this is the API for topic provisioning. | Currently Available | Currently Available | |
| OOF | PCI Optimization API http://{OOF-host}:{port}/api/oof/v1/pci http://{pcims-host}:{port}/callbackUrl Call back URL for SON-MS (to provide PCI optimization results) | Currently Available | Currently Available | |
| ConfigDB | http://{ConfigDB-host/IP}:{port}/SDNCConfigDBAPI/getNbrList/{cellId}/{ts} (Get neighbor list for a cell Id) http://{ConfigDB-host/IP}:{port}/SDNCConfigDBAPI/getPnfName/{cellId}/{ts} (Get the PNF name for a cell Id) | Currently Available | Currently Available |
API Outgoing Dependencies
...
| CPS | Used by SON-handler and/or Slice-Analysis MS | M2 | R8 M2 |
API Outgoing Dependencies
API this project is delivering to other projects.
...
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 components 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 similar to what was done in last release
Gaps
...
- ; 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.
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Risks
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).
...
Cloudify support for Python 3.x not available currently, expected in by Aug 2020 timeframe. This impacts migration of Cloudify and associated plugins in Honolulu (REQ-373)
...
Resources
...
|
Risks
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 |
|---|---|---|
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
Please 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.
...