Versions Compared

Old Version 2

changes.mady.by.user Vijay Venkatesh Kumar

Saved on

compared with

New Version 3

changes.mady.by.user Vijay Venkatesh Kumar

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Project NameEnter the name of the project
Target Release NameHonolulu Istanbul
Project Lifecycle StateMature. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information
Participating Company AT&T, Nokia, Ericsson, Wipro,  ChinaMobileSamsung, T-MobileHuawei

Scope

What is this release trying to address?

Release Focus

DCAE Focus for R8 R9 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-440  - E2E Network Slicing use case requirements for Honolulu release

...

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

Commitment from WIPRO, China Mobile 

...

DCAEGEN2-2521

...

YES

...

SON-Handler Enhancements (CPS integration and VES alignment)

Commitment from WIPRO

...

DCAEGEN2-2522

  • Progress on DCAE Architecture transformation to migrate to Helm
    • Common Template Enhancement 
      • CMPv2 Certificate
      • Policy Sidecar
      • PG credentials management through K8S secret
      • ConfigMap Support
      • DMaap Config Support (dynamic)
    • Helm charts migration for all other DCAE services
      • Bulk PM flow - DataFile, PM-Mapper, PMSH
      • E2E Slicing - KPI-MS, Slice-Analysis, DL Handlers (Feeder, Admin, DES)
      • Son-Handler, Heartbeat, VES-Mapper, RESTCOnf, SNMPTrap, BBS-Ep
    • Remove Consul dependency - application config standardization for Helm deployed components  (Prototype for VES/HV-VES)
      • Helm charts generation through MOD  (POC)
      • ONAP Internal Helm Registry support
  • TSC/SECCOM Global requirements
  • Reducing DCAE backlogs  + security fixes

Istanbul Usecases with DCAE impact

...

REQ#DCAE Commit StatusDCAE Impact AssessmentDCAE JIRA #

REQ-

433

721  - 

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 

...

E2E Network Slicing use case enhancements for Istanbul release

YES
  1. Enhancements in Slice Analysis MS (CPS integration)
  2. Enhancements in KPI MS

Commitment from WIPRO, China Mobile 

DCAEGEN2-2771

REQ-720 - 5G SON use case enhancements for Istanbul release

YES

SON-Handler Enhancements (CPS integration and VES alignment)

Commitment from WIPRO

DCAEGEN2-2522

Istanbul Features with DCAE Impact

REQ#DCAE Commit StatusDCAE Impact AssessmentDCAE JIRA #

Image AddedREQ-723 - CMPv2 enhancements in Istanbul release


CertService client integration (replacing init container) + auto certificate reload via SDK

Commitment from Nokia

DCAEGEN2-2635

Istanbul Spec with DCAE Impact

YES

Generic mechanism to attach K8S ConfigMaps to DCAE apps. through spec/bp-gen/plugin  (VES and DFC)

Commitment from Nokia

VESCollector Enhancements – Event publish order issue 

Commitment from Nokia

Plugin path/load optimization: Taking release from PATH on raw/plugin repo location (rely on version) and update bootstrap/cloudify build

REQ#DCAE Commit StatusDCAE Impact AssessmentDCAE JIRA #
REQ-422715 - Bulk PM / PM Data Control Improvements

PMSH enhancement for dynamic filter/subscription change + API enhancements


Commitment from Ericsson

DCAEGEN2-2541

 NA (Backlog)

DCAEGEN2-2703 Add stndDefined domain to HV-VES

YES

MOD updates 
- Enhance MOD UI/catalog and deployment (POC)Add stndDefined support in HV-VES 

Commitment from AT&TNokia

DCAEGEN2-2313NA (Backlog)YES

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

DCAEGEN2-1483

NA (Backlog)Stretch 

DCAEGEN2-2337

NA (Backlog)Stretch Eliminate use of Consul service discovery in DCAEDCAEGEN2-1786

Honolulu POC (DCAE impact)

2703
DCAEGEN2-1483 - VESCollector synchronous handling

VESCollector Enhancements – Event publish order issue 


Commitment from Nokia

DCAEGEN2-1483

DCAEGEN2-2668 - MOD Enhancements 

(Backlog)

Stretch 

Address backlog items identified from previous release (Catalog/authservice/UI) 

  • Update UI dropdown/properties
  • Secure API's

DCAEGEN2-2668

Honolulu POC (DCAE impact)

REQ#DCAE Commit StatusDCAE Impact AssessmentDCAE JIRA #
REQ-685 - DCAE Transformation to support Helm (Phase2)YES
  • Migrate all remaining DCAE services to helm
  • DCAE svc template extension to support generic functions
  • Archiving Cloudify workflow related handlers

Commitment from AT&T, Nokia, Ericsson, Wipro, Independent, Orange/Samsung (OOM)

DCAEGEN2-2630

Best Practices/GLOBAL Requirements

REQ#DCAE Commit StatusDCAE Impact
Assessment
AssesmentDCAE JIRA #
REQ-
479
443 - 
DCAE Transformation to support HelmYES
  • 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 ReleaseNONeed more infoREQ-470 - DCAE extension for collecting files from HTTP serversYES

DFC Enhancement 

Commitment from Nokia

DCAEGEN2-2517 

Best Practice Candidates

...

Tcagen2, DFC, RESTConf, VES, InventoryAPI, MOD-runtimeAPI, Mapper, PM-Mapper, PRH, SON-Handler

...

 CFY Plugin to support IPv6 service exposure + VES Spec updates 

Commitment from Nokia

...

Global Requirements

...

Require exception for MOD/genprocessor/designtool/nifi-registry

Risk #6 (Honolulu Risks)

...

DCAEGEN2-2381

DCAEGEN2-2428

...

CONTINUATION OF CII BADGING SCORE IMPROVEMENTS FOR SILVER LEVEL 

DCAEGEN2-2570?
REQ-439 - CONTINUATION OF PACKAGES UPGRADES IN DIRECT DEPENDENCIESYES

Tcagen2, DFC, RESTConf, MOD-runtimeAPI, Mapper, PM-Mapper, PRH, SON-Handler, KPI-Computation MS, Slice-Analysis MS


DCAEGEN2-2768
REQ-437 - COMPLETION OF PYTHON LANGUAGE UPDATE (v2.7 → v3.8)YES

HealthCheck container 


DCAEGEN2-2737
REQ-438 - COMPLETION OF JAVA LANGUAGE UPDATE (v8 → v11)
  • dcaemod-designtool
  • dcaemod-nifi-registry

DCAEGEN2-2736


DCAEGEN2-2381?

DCAEGEN2-2428?

REQ-432 - IPv4/IPv6 dual stack support in ONAPYES

Enhance ONAP common-service template - add IPv4/IPv6 support

Commitment from Nokia

OOM-2749 




Note: The above commitment is consistent with Istanbul Impact View per Component (as of 06/09/2021) 

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

Jira
serverONAP Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject=dcaegen2 and issuetype in (epic) and fixversion='Istanbul Release'
serverId425b2b0a-557c-3c0c-b515-579789cceedb

Stories

Jira
serverONAP Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject=dcaegen2 and issuetype in (story) and fixversion = 'Istanbul Release'
serverId425b2b0a-557c-3c0c-b515-579789cceedb

Longer term roadmap

      Complete DCAE transformation initatives and backlog items.

  • DCAE MOD: Support for Helm flow (onboarding and chart generation*)
  • DCAE/OOM: Remove consul dependency after all DCAE service are migrated to the latest SDK
  • Policy/CLAMP: Continue integration for Control Loop design for Helm-based deployment of DCAE Services*
  • DCAE: Chart migration from OOM repo to DCAE & ONAP CI/CD integration for helm chart builds
  • Integration: Robot test suites migration to support helm services*
  • DCAE: Archive Cloudify and associated handlers/plugins and disable under ONAP deployment

Release Deliverables

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

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

  • 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 

Platform Maturity

 Platform Maturity (i.e., S3P items)  Honolulu Release Platform Maturity

...

      • 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

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject=dcaegen2 and issuetype in (epic) and fixversion='Honolulu Release' and status != 'Closed'
serverId425b2b0a-557c-3c0c-b515-579789cceedb

Stories

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject=dcaegen2 and issuetype in (story) and fixversion = 'Honolulu Release'
serverId425b2b0a-557c-3c0c-b515-579789cceedb

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

...

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

...

REQ-440 

...

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)

...


ONAP Dependencies

List the other ONAP projects you depend on.

...