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?

...

TBCTBC

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 - New 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)	TBCStretch	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
NA (Backlog)	?	DataLake Handler Enhancements (TLS support/security/GUI test suite)	DCAEGEN2-2230

Honolulu POC (DCAE impact)

TBC

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	TBANeed more info
REQ-470 - DCAE extension for collecting files from HTTP servers	YES	DFC Enhancement Commitment from Nokia	DCAEGEN2-2517

...

TBATBC (based on resource)

REQ#	DCAE Commit Status	DCAE Impact Assesment	DCAE JIRA #
REQ-443 - CONTINUATION OF CII BADGING SCORE IMPROVEMENTS FOR SILVER LEVEL	TBC	Stretch		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)	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)

TBC (based on upstream depenency)MOD/genprocessor

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

TBC (based on resource)

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

New Services introduced for this release

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

...

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.

Maven Group ID

Deliverable

Repository

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:

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

...

Anyone reading this section should have a good understanding of all the interacting modules.

Target Architecture (REQ-479)

Image Added

Platform Maturity

...

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 footprintminimal 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 Transaction tracing across components Consistent UI across ONAP projects Usability	1	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 1+ Level 1: User guide created Deployment documentation API documentation Adherence to coding guidelines Level 2: API Documentation All new API’s API’s for a given project must adhere to the ONAP API Common Versioning Strategy and 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.

...

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)

...

http://{ConfigDB-host/IP}:{port}/SDNCConfigDBAPI/getNbrList/{cellId}/{ts} (Get neighbor list for a cell Id)

...

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

...

API Outgoing Dependencies

API this project is delivering to other projects.

...

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, ...).

...

cloudifyplatform/community

...

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
  - CSIT tests will continue to be supported for existing components
  - Pairwise testing will be done in the WindRiver Dev lab similar to what was done in last release

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 components will MOD (NiFI) components (designtool/gen-processor/nifi-registry) will remain in java 8	Continue Frankfurt Guilin version	DCAEGEN2-2428

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.

...

Space shortcuts

Page tree

Versions Compared

Old Version 11

New Version Current

Key

Scope

What is this release trying to address?

Honolulu POC (DCAE impact)

Global Requirements

New Services introduced for this release

New Services introduced for this release

ONAP Dependencies

ONAP Dependencies

Architecture

Platform Maturity

API Incoming Dependencies

API Incoming Dependencies

API Outgoing Dependencies

Third Party Products Dependencies

Testing and Integration Plans

API Outgoing Dependencies

Third Party Products Dependencies

Testing and Integration Plans

Gaps

Resources

Release Milestone

Space shortcuts

Page tree

Page History

Versions Compared

Old Version 11

New Version Current

Key

Scope

What is this release trying to address?

Honolulu POC (DCAE impact)

Global Requirements

New Services introduced for this release

New Services introduced for this release

ONAP Dependencies

ONAP Dependencies

Architecture

Platform Maturity

API Incoming Dependencies

API Incoming Dependencies

API Outgoing Dependencies

Third Party Products Dependencies

Testing and Integration Plans

API Outgoing Dependencies

Third Party Products Dependencies

Testing and Integration Plans

Gaps

Resources

Release Milestone