...

Scope

What is this release trying to address?

...

DCAE Focus for R8 is on following

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

Honolulu Usecases with DCAE impact

...

Honolulu Spec with DCAE Impact

Honolulu POC (

...

DCAE impact)

...

DCAEGEN2-2230

Honolulu DCAE POC

...

Global Requirements

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

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 The MVP of DCAE will include the necessary subcomponents supporting the primary objectives: meeting platform maturity goals and supporting the use cases.

...

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

...

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

...

• 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

...

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.

...

 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)

...

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.

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

• 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

Fill out the Resources and Repositories (Deprecated) centralized page

• Release Milestone

The milestones are defined at the Release Planning (legacy): Honolulu and all the supporting project agreed to comply with these dates.

...