...
Project Name | Enter the name of the project |
---|---|
Target Release Name | Honolulu Istanbul |
Project Lifecycle State | Mature. 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
...
- Enhancements in Slice Analysis MS
- Enhancements in DES.
- KPI computation (new MS)
Commitment from WIPRO, China Mobile
...
...
YES
...
SON-Handler Enhancements (CPS integration and VES alignment)
Commitment from WIPRO
...
- 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
- Common Template Enhancement
- TSC/SECCOM Global requirements
- Reducing DCAE backlogs + security fixes
Istanbul Usecases with DCAE impact
...
REQ# | DCAE Commit Status | DCAE Impact Assessment | DCAE JIRA # |
721 - |
YES
Standard-defined openAPI onboarding (K8S configMap update for VEScollector)
Commitment from Nokia
TBC
YES
DFC & RestConf(stretch) integration + OOM/cert-manager integration
Commitment from Nokia
...
YES |
Commitment from WIPRO, China Mobile | ||
REQ-720 - 5G SON use case enhancements for Istanbul release | YES | SON-Handler Enhancements (CPS integration and VES alignment) Commitment from WIPRO |
Istanbul Features with DCAE Impact
REQ# | DCAE Commit Status | DCAE Impact Assessment | DCAE JIRA # |
REQ-723 - CMPv2 enhancements in Istanbul release | TBC | CertService client integration (replacing init container) + auto certificate reload via SDK Commitment from Nokia |
Istanbul Spec with DCAE Impact
REQ# | DCAE Commit Status | DCAE Impact Assessment | DCAE JIRA # | ||||||||
REQ-422715 - Bulk PM / PM Data Control Improvements | YES | PMSH enhancement for dynamic filter/subscription change + API enhancements Commitment from Ericsson | NA (Backlog) | ||||||||
DCAEGEN2-2703 Add stndDefined domain to HV-VES | YES | Add stndDefined support in HV-VES Commitment from Nokia | DCAEGEN2-2703 | ||||||||
DCAEGEN2-1483 - VESCollector synchronous handling MOD updates Commitment from AT&T NA(Backlog) | YES | VESCollector Enhancements – Event publish order issue Commitment from Nokia | |||||||||
DCAEGEN2-2668 - MOD Enhancements | NA (Backlog) | YES | BP-gen Enhancements
Commitment from Nokia | NA (Backlog) | Stretch | NA (Backlog) | Stretch | ||||
NA (Backlog) | Stretch | Eliminate use of Consul service discovery in DCAE | DCAEGEN2-1786 |
Honolulu POC (DCAE impact)
Stretch | Address backlog items identified from previous release (Catalog/authservice/UI)
|
Istanbul POC (DCAE impact)
REQ# | DCAE Commit Status | DCAE Impact Assessment | DCAE JIRA # |
REQ-685 - DCAE Transformation to support Helm (Phase2) | YES |
Commitment from AT&T, Nokia, Ericsson, Wipro, Independent, Orange/Samsung (OOM) |
Best Practices/GLOBAL Requirements
REQ# | DCAE Commit Status | DCAE Impact |
Assesment | DCAE JIRA # |
REQ- |
443 - |
CONTINUATION OF CII BADGING SCORE IMPROVEMENTS FOR SILVER LEVEL | YES |
- Bootstrap component migration
- Platform sidecar (policy)
- Configuration management (Design)
- MOD helm onboarding (Design)
Commitment from AT&T, Independent Contributors
DFC Enhancement
Commitment from Nokia
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)
...
...
Sonar security fixes (RESTConf) CII badging score improvement | DCAEGEN2-2829 | ||
REQ-439 - CONTINUATION OF PACKAGES UPGRADES IN DIRECT DEPENDENCIES | YES | 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) | No |
Exception will be filed with SECCOM for waivers due to upstream (NIFi) dependency | |
REQ-432 - IPv4/IPv6 dual stack support in ONAP | YES | 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) Istanbul 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
As DCAE transformation is underway, two different deployment options will be available. The MVP of DCAE will vary based on deployment choice and will include the necessary subcomponents supporting the primary objectives: meeting platform maturity goals and supporting the use cases.
Helm Deployment (dcaegen2-services)
- VESCollector
- TCA-gen2
- PRH
- HV_VES
Helm/Cloudify Deployment (dcaegen2)
- 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 server ONAP Jira
- 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)
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
...
- 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 server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=dcaegen2 and issuetype in (epic) and fixversion='Honolulu Release' and status != 'Closed' serverId 425b2b0a-557c-3c0c-b515-579789cceedb
Stories
Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=dcaegen2 and issuetype in (storyepic) and fixversion='Honolulu Istanbul Release' serverId 425b2b0a-557c-3c0c-b515-579789cceedb
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
...
https://git.onap.org/dcaegen2/services/tree/components/kpi-computation-ms (introduced as new subproject under existing repo)
...
...
https://gerrit.onap.org/r/admin/repos/dcaegen2/platform/ves-openapi-manager (New repo)
...
...
DCAE-service-policy-Sync
...
https://git.onap.org/dcaegen2/deployments/tree/dcae-services-policy-sync (introduced a new subproject/module under existing repo)
...
Jira server ONAP Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=dcaegen2 and issuetype in (story) and fixversion = 'Istanbul Release' serverId 425b2b0a-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 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/blueprint/helm charts |
hv-ves-collector | SourceCode/jar/Docker image/blueprint/helm charts |
prh | SourceCode/jar/Docker image/blueprint/helm charts |
dcae-mod | SourceCode/jar/Docker image/Documentation |
tca-gen2 | SourceCode/jar/Docker image/blueprint/helm charts |
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.
ONAP Dependencies
List the other ONAP projects you depend on.
...
- AAI: DCAE MS retrieves and updates VNF data from/to AAI
- DMaaP: Message bus for communication with other components in the solution
- Policy/CLAMP - Policy - For managing application configuration policy. CLAMP - For CL flow related MS instantiation and configuration
- OOF - For SON handler support
...
Anyone reading this section should have a good understanding of all the interacting modules.
Target Architecture (REQ-479685)
Platform Maturity
Istanbul Release 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 | How, Evidences | Comments | |||
---|---|---|---|---|---|---|---|
Performance | 1 | 1 |
| ||||
Stability | 2 | 2 |
| ||||
Resiliency | 2 | 2 |
| ||||
Security | 1 | 1+ | Security | 1 | 1+ (Most DCAE components are complaint; will address remaining in Honolulu based on resource availability) |
| |
Scalability | 1 | 1 |
| ||||
Manageability | 1 | 1+ (Except logging, all other requirements are met) |
| ||||
Usability | 1 | 1+ |
|
...
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.
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 | This will be replaced with CPS for Istanbul | |
CPS | Used by SON-handler and/or Slice-Analysis MS | Currently Available | Currently Available |
API Outgoing Dependencies
API this project is delivering to other projects.
API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
VES Collector | API for VNFs to send VES data | Currently Available | No change for this release | |||||||||||||||||||||||
DCAE Deployment Handler | NB API for invoking the deployment of DCAE subcomponents | Currently Available | R3 | No change for this release | ||||||||||||||||||||||
DCAE Inventory | API for Add/Delete DCAE copy's TOSCA models | Currently Available | R3 | No change for this release | ||||||||||||||||||||||
Healthcheck | API for querying DCAE component healthcheck | Currently Available | R4 | No change for this release | ||||||||||||||||||||||
DCAE Onboarding API | API for publishing DCAE spec into MOD | Currently Available | R6 | No change for this release | ||||||||||||||||||||||
DCAE Inventory | API for CLAMP to retrieve flow information | Currently Available | R6 | No change for this release | ||||||||||||||||||||||
Data Extraction Service (DES) | API for data retrieval and simple computation from DL-Handler maintained storages (For R8, this will be used by DCAE components such Slice-Analyis MS) and UUI | Currently Available | R8 | No change for this release | ||||||||||||||||||||||
PMSH | API support for Subscription/Filters/Measurement group management | Under review (https://gerrit.onap.org/r/c/dcaegen2/+/121898) | R9 M2 | https://gerrit.onap.org/r/c/dcaegen2/+/121898 | ||||||||||||||||||||||
SliceAnalysis | API support for data aggregation based on NSI/NSSI; this will be consumed by OOF | Reviewed | R9 M2 | NSI/NSSI Selection based on resource occupancy levels | ||||||||||||||||||||||
API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) | ||||||||||||||||||||||
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
...
Name | Description | Version |
---|---|---|
NIFI | Apache NIFI | 1.9.x |
Cloudify Manager | cloudifyplatform/community | 19.01.24cloudifyplatform/community-cloudify-manager-aio:5.1.2 |
Consul | 1.0.0 (version based on OOM)OOM | |
In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.
...
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 Honolulu version |
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
...
The milestones are defined at the Release Planning: HonoluluIstanbul and all the supporting project agreed to comply with these dates.
...
Date | Sprint | #No of days | Deliverable | ||
---|---|---|---|---|---|
Key dates for Hononolu Istanbul release - M1 - 105/1120, M2 - 106/2117, M3 - 2/25. RC0 - 3/1108/26, M4- 09/16, RC - 10/14,Signoff - 410/128 | |||||
0105/0420/2021 2021 - 0106/2117/2021 | DCAE Honolulu Istanbul Sprint 1 (Planning)14 |
| |||
06/1801/22/2021 - 02 07/1115/2021 | DCAE Honolulu Istanbul Sprint 2 (Development) | 15 |
| ||
0207/1216/2021 2021 - 03 08/0426/2021 | DCAE Honolulu Istanbul Sprint 3 (Code Freeze) | 15 | M3 - 2 weeks dev + package finalization (container released)
| ||
0308/0527/2021 2021 - 03 09/2516/2021 | DCAE Honolulu Istanbul Sprint 4 (Integration support)Container Release/artifact) | Finalize containers/jars for Istanbul release and submit patch to OOM for revisions | |||
09/17/2021 - 10/14/2021 | Integration | 15 | M3 - |
|
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 Istanbul Documentation
Other Information
Vendor Neutral
...