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?

Release Focus

DCAE Focus for R8 is on following

ONAP R8 Usecase & Feature requirement
TSC/SECCOM Global requirements
DCAE Transformation to support Helm deployment for services
General platform optimization (Cloudify upgrade for python 3.6)
Reducing DCAE backlogs + security fixes

Honolulu Usecases with DCAE impact

REQ#

DCAE Commit Status

DCAE Impact Assessment

DCAE JIRA #

REQ-440 - E2E Network Slicing use case requirements for Honolulu release

YES

Enhancements in Slice Analysis MS
Enhancements in DES.
KPI computation (new MS)

Commitment from WIPRO, China Mobile

DCAEGEN2-2521

REQ-429 - Use Case for ONAP-based SON for 5G networks

YES

SON-Handler Enhancements (CPS integration and VES alignment)

Commitment from WIPRO

DCAEGEN2-2522

Honolulu Features with DCAE Impact

REQ#

DCAE Commit Status

DCAE Impact Assessment

DCAE JIRA #

REQ-433 - ONAP/3GPP & O-RAN Alignment-Standards Defined Notifications over VES (Honolulu)

YES

Standard-defined openAPI onboarding (K8S configMap update for VEScollector)

Commitment from Nokia

TBC

DCAEGEN2-2539

REQ-431 - CMPv2 enhancements in R8

YES

DFC & RestConf(stretch) integration + OOM/cert-manager integration

Commitment from Nokia

DCAEGEN2-2422

Honolulu Spec with DCAE Impact

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 - Enhance MOD UI/catalog and deployment (POC) Commitment from AT&T	DCAEGEN2-2313
NA (Backlog)	YES	Generic mechanism to attach K8S ConfigMaps to DCAE apps. through spec/bp-gen/plugin (VES and DFC) Commitment from Nokia	DCAEGEN2-2539
NA (Backlog)	YES	BP-gen Enhancements Fix issues/bug noted in Guilin testing Adjust BP-gen to support native Kafka topics Adjust BP-gen to support DFC component spec Commitment from Nokia	DCAEGEN2-2458
NA (Backlog)	Stretch	VESCollector Enhancements – Event publish order issue Commitment from Nokia	DCAEGEN2-1483
NA (Backlog)	Stretch	Plugin path/load optimization: Taking release from PATH on raw/plugin repo location (rely on version) and update bootstrap/cloudify build	DCAEGEN2-2337
NA (Backlog)	Stretch	Eliminate use of Consul service discovery in DCAE	DCAEGEN2-1786

Honolulu POC (DCAE impact)

REQ#	DCAE Commit Status	DCAE Impact Assessment	DCAE JIRA #
REQ-479 - DCAE Transformation to support Helm	YES	Bootstrap component migration Platform sidecar (policy) Configuration management (Design) MOD helm onboarding (Design) Commitment from AT&T, Independent Contributors	DCAEGEN2-2488
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

Best Practice Candidates

REQ#	DCAE Commit Status	DCAE Impact Assesment	DCAE JIRA #
REQ-443 - CONTINUATION OF CII BADGING SCORE IMPROVEMENTS FOR SILVER LEVEL	Stretch		DCAEGEN2-2570
REQ-441 - LOGS MANAGEMENT - PHASE 1: COMMON PLACE FOR DATA	NO	Need 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)	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)

DCAEGEN2-2381

DCAEGEN2-2428

REQ-437 - COMPLETION OF PYTHON LANGUAGE UPDATE (v2.7 → v3.8

YES

Cloudify plugins (https://git.onap.org/dcaegen2/platform/plugins/tree/) -
Policy-Handler (dcaegen2/platform/policy-handler)
SNMP-TRap Collector (dcaegen2/collectors/snmptrap) (dependency on 3.6 PyPy Python interpreter)

Cloudify upgrade to 5.1 community version

Commitment from T-mobile, Independent contributon

Risk #7 (Honolulu Risks)

DCAEGEN2-2494

DCAEGEN2-2427

DCAEGEN2-1546

Note: The above commitment is consistent with Honolulu Impact View per Component (as of 1/19/2021)

New Services introduced for this release

Following new services will be delivered in R8

KPI Computation MS (REQ-440 )
- Repository : https://git.onap.org/dcaegen2/services/tree/components/kpi-computation-ms (introduced as new subproject under existing repo)

VES-OpenAPI-Manager (REQ-433)
- Repository : https://gerrit.onap.org/r/admin/repos/dcaegen2/platform/ves-openapi-manager (New repo)

DCAE-service-policy-Sync (REQ-479)
- Repository : https://git.onap.org/dcaegen2/deployments/tree/dcae-services-policy-sync (introduced a new subproject/module under existing repo)

Platform Maturity

Platform Maturity (i.e., S3P items) 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+

Minimum Viable Product

The MVP of DCAE will include the necessary subcomponents supporting the primary objectives: meeting platform maturity goals and supporting the use cases.

- Cloudify Manager
- Consul (deployed/managed by OOM)
- DeploymentHander
- Policy-Handler
- ServiceChangeHandler
- Inventory-API
- Postgres
- ConfigBinding Service
- Dashboard

DCAE Service specific components

- VESCollector
- TCA-gen2
- PRH
- HV_VES

DCAE-MOD deployment is optional and will include following component (controlled via helm chart configuration under OOM)

Genprocessor
MOD/NiFI UI
Distributorapi
Runtimeapi
Onboardingapi

Functionalities

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.

Epics

key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution

Loading...

Refresh

Stories

key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution

Loading...

Refresh

Longer term roadmap

DCAE is the collection and analytics platform serving ONAP. Improving upon the DCAE MS catalog to add new services for data collection, analytics and the number of open/close control loops.

DCAE-MOD evolution and integration with CLAMP and Policy

Release Deliverables

Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.

Deliverable Name	Deliverable Description
Component spec	All ms added into DCAE should provide meta data representation of the component itself; will be used to generate design flow under MOD and enable blueprint generation
blueprints	Executable/SourceCode
plugins	SourceCode and wagon files under nexus/raw
deployment-handler	SourceCode/Docker image
servicechange-handler	SourceCode/Docker image
inventory-api	SourceCode/Docker image
policy-handler	SourceCode/Docker image
configbinding	SourceCode/Docker image
ves	SourceCode/Docker image
hv-ves-collector	SourceCode/jar/Docker image
prh	SourceCode/jar/Docker image
dcae-mod	SourceCode/jar/Docker image/Documentation
tca-gen2	SourceCode/jar/Docker image

Note: Only default platform components and bootstrapped MS is listed on table above. DCAE also include dynamic service components deployed based on usecases. For a complete set of available DCAE MS - refer https://docs.onap.org/projects/onap-dcaegen2/en/latest/sections/release-notes.html#deliverables

Sub-Components

List all sub-components part of this release. Activities related to sub-components must be in sync with the overall release.

Sub-components are repositories and are consolidated in a single centralized place. Edit the Resources and Repositories (Deprecated) in the centralized page.

In addition to existing platform/service component, following new components are targeted for Honolulu.

Deliverable	Repository	Components Description
KPI Computation MS	https://git.onap.org/dcaegen2/services/tree/components/kpi-computation-ms (introduced as new subproject under existing repo)	REQ-440
VES-OpenAPI-Manager	https://gerrit.onap.org/r/admin/repos/dcaegen2/platform/ves-openapi-manager (New repo)	REQ-433
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	Comments
Performance	1	1	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)
Stability	2	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
Resiliency	2	2	0 – none 1 – manual failure and recovery (< 30 minutes) 2 – automated detection and recovery (single site) 3 – automated detection and recovery (geo redundancy)
Security	1	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
Scalability	1	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
Manageability	1	1+ (Except logging, all other requirements are met)	Level 1: All ONAP components will use a single logging system. Instantiation of a simple ONAP system should be accomplished in <1 hour with a minimal footprint Level 2: A component can be independently upgraded without impacting operation interacting components Component configuration to be externalized in a common fashion across ONAP projects All application logging to adhere to ONAP Application Logging Specification v1.2 Implement guidelines for a minimal container footprint Level 3 Transaction tracing across components
Usability	1	1+	Level 1: User guide created Deployment documentation API documentation Adherence to coding guidelines Level 2: API Documentation All new API’s must adhere to the ONAP API Common Versioning Strategy and Documentation Guidelines All existing APIs must be documented in Swagger 2.0 Level 3 Consistent UI across ONAP projects Usability testing conducted API Documentation All new API’s, all external APIs, and all existing API’s that are modified must adhere to the ONAP API Common Versioning Strategy and Documentation Guidelines Level 4 API Documentation All API’s for a given project must adhere to the ONAP API Common Versioning Strategy and Documentation Guidelines

API Incoming Dependencies

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	Currently 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
CPS	Used by SON-handler and/or Slice-Analysis MS	M2	R8 M2

API Outgoing Dependencies

API this project is delivering to other projects.

API Name	API Description	API Definition Date	API Delivery date
VES Collector	API for VNFs to send VES data	Will be updated for new VES spec (7.2)
DCAE Deployment Handler	NB API for invoking the deployment of DCAE subcomponents	Currently Available	R3
DCAE Inventory	API for Add/Delete DCAE copy's TOSCA models	Currently Available	R3
Healthcheck	API for querying DCAE component healthcheck	Currently Available	R4
DCAE Onboarding API	API for publishing DCAE spec into MOD	Currently Available	R6
DCAE Inventory	API for CLAMP to retrieve flow information	Currently Available	R6
Data Extraction Service (DES)	API for data retrieval and simple computation from DL-Handler maintained storages (For R7, this will be used by DCAE components such Slice-Analyis MS) and UUI	Currently Available	R7

Third Party Products Dependencies

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
NIFI	Apache NIFI	1.9.x
Cloudify Manager	cloudifyplatform/community	19.01.24
Consul		1.0.0 (version based on OOM)

In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.

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.
    - https://sonarcloud.io/organizations/onap/projects?search=dcaegen2
  - Functional test plan
    - DCAE R8 Testplan
  - CSIT tests will continue to be supported for existing 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; below wiki page captures the test planned
    - DCAE R8 Honolulu Pairwise Test
  - 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.

Gaps identified	Impact

Known Defects and Issues

Provide a link toward the list of all known project bugs.

key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution

Loading...

Refresh

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	DCAEGEN2-2428

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: Honolulu and all the supporting project agreed to comply with these dates.

Team Internal Milestone

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 erecommended to provide these agreements and dates in this section.

It is not expected to have a detailed project plan.

Date	Sprint	#No of days	Deliverable
Key dates for Hononolu release - M1 - 1/11, M2 - 1/21, M3 - 2/25. RC0 - 3/11,Signoff - 4/1
01/04/2021 - 01/21/2021	DCAE Honolulu Sprint 1 (Planning)	14	Finalize DCAE scope and committment
01/22/2021 - 02/11/2021	DCAE Honolulu Sprint 2 (Development)	15	50% or more of Functional delivery completed Atleast 60% of release/compliance (coverage & security) API definition formalized and shared with impacted teams Integration test plan completed CSIT/automated test delivery SDK version for Honolulu to be baselined and released Documentation repo updates (API updates & new MS/component) - Honolulu Documentation
02/12/2021 - 03/04/2021	DCAE Honolulu Sprint 3 (Code Freeze)	15	M3 - 25 Feb 2021 2 weeks dev + package finalization (container released) 100% of release/compliance (coverage & security) Validate deployment/integration with ONAP/DCAE deploy New container version to be released Update OOM chart/blueprint/documentation to reflect correct version Documentation update for deployment/configuration/architecture/logging
03/05/2021 - 03/25/2021	DCAE Honolulu Sprint 4 (Integration support)	15	M3 - 11 Mar 2021 Fix Integration blockers and high priorty issue Update OOM chart/blueprint/documentation to reflect correct version Demo for new components introduced Pair-wise testing Branching

Documentation, Training
- - Highlight the team contributions to the specific document related to he project (Config guide, installation guide...).
  - Highlight the team contributions to the overall Release Documentation and training asset
  - High level list of documentation, training and tutorials necessary to understand the release capabilities, configuration and operation.
  - Documentation includes items such as:
    - Installation instructions
    - Configuration instructions
    - Developer guide
    - End User guide
    - Admin guide

Honolulu Documentation

Other Information

- Vendor Neutral

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.

- Free and Open Source Software

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.

Charter Compliance

The project team comply with the ONAP TSC Charter OBSOLETE 7 1 CLEAN.pdf.

Browser not supported