Overview

Scope

What is this release trying to address?

Release Focus

DCAE Focus for R7 R8 is on following

• ONAP R7 R8 Usecase & Functional Feature requirement 
• TSC/SECCOM MUST-HAVE requirementsGlobal requirements
• DCAE Transformation to support Helm deployment for services
• General platform optimization 
• DCAE Bootstrap/CM Manager optimization (moving plugins to CM)
• MOD catalog/UI redesign (POC)
Addressing DCAE back logs optimization (Cloudify upgrade for python 3.6)
• Reducing DCAE backlogs  + security fixes

Honolulu Usecases with DCAE impact

Following new services will be delivered in R7 to support REQ-342

Slice Analysis MS 

Repository : https://git.onap.org/dcaegen2/services/tree/components/slice-analysis-ms

Data Extraction Service (DES)

Repository : https://git.onap.org/dcaegen2/services/tree/components/datalake-handler/des

Honolulu Features with DCAE Impact

Functional Requirements

...

YES

...

PMSH and PM-Mapper enhancements

Commitment based on Ericsson

...

YES

...

VESCollector + platform/deployment support via config-map

Commitment based on Nokia 

...

MOD updates 
- Nifi backlog reduction
- New MOD UI/catalog (POC)

Commitment based on AT&T

...

DCAE Platform (k8splugin, CM/Bootstrap)
Component_spec + Bp-gen
MOD component
OOM revision

Commitment based on Nokia, AT&T

...

K8splugin change to support k8s 1.17+  

Commitment based on Nokia

...

Non-Functional Requirement 

...

Add explicit references to dockerhub or nexus to all images  

Commitment based on Samsung, AT&T

...

HIGH RISK - Approved base images list NOT CONFIRMED + MULTIPLE DCAE COMPONENT IMPACT  (RISK#5- Guilin Risks)

• Approved base image for NodeJS TBC
• Need exception for some DCAE components (Cloudify, MOD) due to upstream dependency
• Need resource/community support due to number of impact component 

Commitment : AT&T, Nokia, Ericsson, Wipro,  ChinaMobile

...

Per TSC 2.7->3.8 important; 3.7-3.8 (nice to have) 

Except Cloudify and SNMPTrap - all other DCAE components will be migrated to 3.8. SECCOM approved exception on 7/3 (refer jira)

Commitment based on T-Mobile

...

MEDIUM RISK - Need further assessment on DCAE components impacted (RISK#6 Guilin Risks)

Commitment based on Ericsson

...

MEDIUM RISK - Need further assessment on DCAE components impacted  (RISK#6 Guilin Risks)

Exception required for Cloudify due to upstream dependency. 

Commitment based on Ericsson

...

Resource TBD

...

Commitment based on Orange/Samsung/AT&T

...

Okay for service components (as CBS is used); Platform component should be okay. MOD - to be verified (possibly MOD/Nifi container) + Dashboard

...

Need further assesment.  Current list of component impact -  Dashboard/Inventory/TCA-gen2/heartbeat/PM-Mapper/DL-feed/Son-handler

Commitment based on WIPRO/ChinaMobile

...

MEDIUM RISK : Due to number of DCAE components impacted.  (RISK#7 Guilin Risks)

• Some MOD components will need exception (due to NiFI upstream dependency)
• VES-Mapper/RESTConf  - Resource TBC 

Commitment : AT&T, Nokia, Ericsson, Wipro,  ChinaMobile

...

Already complaint for Frankfurt components; new component/enhancement to adhere

Commitment : AT&T, Nokia, Ericsson, Wipro,  ChinaMobile

...

DCAE Backlog Reduction

• VESCollector Enhancements
  • DCAEGEN2-1483  – Event publish order issue (stretch goal)
  • DCAEGEN2-1484  - Set dynamic partitionkey (stretch goal) - AT&T
  • DCAEGEN2-608   - Performance/benchmarking - Nokia
• DL Handlers Enhacements DCAEGEN2-1849 (stretch goal) - China Mobile
• DCAE Dashboard Fixes and security updates - AT&T

Inaddition adhoc platform items from backlog below are targetted for this release also. 

...

With Honolulu release, following components will be deprecated and no longer available part of ONAP DCAE deployments. Corresponding repositories will be marked as RO.

• TCA/CDAP (replaced by TCA-gen2)
• RESTConf Collector*
• VES-Mapper*

    * Pending discussion with ARC/TSC

Platform Maturity

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

Stories

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.

...

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

...

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.

...

Components Description

...

dcaegen2/services

...

org.onap.dcaegen2.services.sliceanalysis

...

Slicen Analysis MS for 5G E2E Slice usecase support

...

org.onap.dcaegen2.services.dl-handler.des

...

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.

Image Removed

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.

Honolulu Features with DCAE Impact

Honolulu Spec with DCAE Impact

Honolulu POC (DCAE impact)

Best Practice Candidates

Global Requirements

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

Stories

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.

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.

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.

Image Added

Target Architecture (REQ-479)

Image Added

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.

...

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

...

• Known Defects and Issues

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

• 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

...

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

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.

• Known Defects and Issues

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

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

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

...

• 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

Guilin Honolulu Documentation

Other Information

• • Vendor Neutral

...