Overview
Project Name | Enter the name of the project |
---|---|
Target Release Name | Jakarta |
Project Lifecycle State | Mature. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information |
Participating Company | AT&T, Nokia, Ericsson, Wipro, Samsung, Huawei, DT |
Scope
What is this release trying to address?
Release Focus
DCAE Focus for R10 is on following
- Complete DCAE transformation to Helm
- Common Template Enhancement for dcaegen2-services-common (filebeat removal + general add-on capabilities)
- Continue removal of Consul dependency & application config standardization via configmap
- MOD Support for Helm chart generation/distribution
- Deprecate Cloudify and related Handlers from ONAP deployment
- Integration Testsuite migration to use helm chart
- TSC/SECCOM Global requirements
- STDIO complaince for Heartbeat and SNMPTRap MS
- TSC/SECCOM Best Practice
- Integration base image alignment for VES/RESTConf/SliceAnalysis MS
- Reducing DCAE backlogs & security fixes
- Microservice enhancements in support for ONAP usecases/features
Jakarta Usecases with DCAE impact
REQ# | DCAE Commit Status | DCAE Impact Assessment | DCAE JIRA # |
TBC | 1. Slice selection taking into consideration resource occupancy levels Commitment from WIPRO | ||
TBC |
Commitment from WIPRO | ||
TBC |
Jakarta Features with DCAE Impact
REQ# | DCAE Commit Status | DCAE Impact Assessment | DCAE JIRA # |
TBC | DCAE impacts requires clarification | ||
YES | Cloudify/platform-handlers deprecation; MOD helm integration |
Jakarta Spec with DCAE Impact
REQ# | DCAE Commit Status | DCAE Impact Assessment | DCAE JIRA # |
REQ-935 Bulk PM / PM Data Control Improvements | YES | PMSH functional enhancement and support for dynamic filter/subscription change via API Commitment from Ericsson | |
TBC | CMPv2 Enhancement - support for VES/DFC/HV-VES cert dynamically | ||
NA | TBC | VES 7.2.1 support for DCAE Microservices (outside of collectors) | |
NA | Stretch-goal | DMAAP SDK standardization for DCAE Microservices | |
NA | TBC | Migrate DCAE MS to use standard topics (i.e unauthenticated) - PM-Mapper, Slice-Analysis, KPI-MS This will aid in Dmaap/Strimzi migration/Servicemesh complaincy and addressing Multiple subscriber issue (DCAEGEN2-2937) | |
NA | TBC | ServiceMesh Compatibility - Switch components deployment default to HTTP |
Jakarta POC (DCAE impact)
REQ# | DCAE Commit Status | DCAE Impact Assessment | DCAE JIRA # |
NA | YES | Trial use of the black formatting and pylint checking tools on python code Commitment from AT&T | |
NA | Stretch-goal | AAF certificate dependency to be removed by making it a configurable property for MS | |
Best Practices/GLOBAL Requirements
REQ# | DCAE Commit Status | DCAE Impact Assesment | DCAE JIRA # |
REQ-443 - CONTINUATION OF CII BADGING SCORE IMPROVEMENTS FOR SILVER LEVEL Global-REQ | YES | CII badging score improvement | |
REQ-439 - CONTINUATION OF PACKAGES UPGRADES IN DIRECT DEPENDENCIES Global-REQ | YES | Tcagen2, DFC, RESTConf, MOD-runtimeAPI, Mapper, PM-Mapper, PRH, SON-Handler, KPI-Computation MS, Slice-Analysis MS | DCAEGEN2-3006 |
REQ-437 - COMPLETION OF PYTHON LANGUAGE UPDATE (v2.7 → v3.8) Global-REQ | YES | (No new impact for DCAE in J release) | DCAEGEN2-3020 |
REQ-438 - COMPLETION OF JAVA LANGUAGE UPDATE (v8 → v11) Global-REQ | No |
Exception will be filed with SECCOM for waivers due to upstream (NIFi) dependency | DCAEGEN2-3019 |
REQ-432 - IPv4/IPv6 dual stack support in ONAP | YES | Enhance ONAP common-service template - add IPv4/IPv6 support (No new impact for DCAE in J release) | OOM-2749 |
REQ-1070 - LOGS MANAGEMENT - PHASE 1: COMMON PLACE FOR DATA - JAKARTA RELEASE Global-REQ | YES | Healthcheck and SNMPTRap container | DCAEGEN2-2958 |
REQ-1073 - Using basic image from Integration | TBC | VESCollector, RESTConf, Slice-Analysis MS need to be switched to use integration base image |
|
Note: The above commitment should be consistent with Jakarta Impact View per Component at M2.
Platform Maturity
Platform Maturity (i.e., S3P items) Jakarta 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
Following platform component will be continued to be deployed via helm until all DCAE MS are migrated to new Config management solution via SDK
- ConfigBinding Service
- Consul
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
Complete DCAE transformation initatives and backlog items.
- 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
- DCAE MOD support for Java11 compatibility
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 |
configbinding | SourceCode/Docker image |
policy side-car | SourceCode/Docker image |
dcae-healthcheck | SourceCode/Docker image |
dcae-mod | SourceCode/jar/Docker image/Documentation |
VES Collector | SourceCode/Docker image/helm charts |
HV_VES Collector | SourceCode/jar/Docker image/helm charts |
PRH | SourceCode/jar/Docker image/helm charts |
TCA-GEN2 | SourceCode/jar/Docker image/helm charts |
DFC | SourceCode/Docker image/helm charts |
RESTConf | SourceCode/Docker image/helm charts |
PM-MAPPER | SourceCode/Docker image/helm charts |
VES-MAPPER | SourceCode/Docker image/helm charts |
DL Components (DES, DL-ADMIN, DL-FEEDER) | SourceCode/Docker image/helm charts |
SLICE ANALYSIS | SourceCode/Docker image/helm charts |
KPI-MS | SourceCode/Docker image/helm charts |
HEARTBEAT MS | SourceCode/Docker image/helm charts |
SON-HANDLER MS | SourceCode/Docker image/helm charts |
PMSH | SourceCode/Docker image/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.
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/CLAMP - Policy - For managing application configuration policy.
- 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.
DCAE Interfaces
Platform Maturity
Jakarta 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+ |
| |
Scalability | 1 | 1 |
| |
Manageability | 1 | 1+ (Except logging, all other requirements are met) |
| |
Usability | 1 | 1+ |
|
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) |
---|---|---|---|---|
Policy Engine | API for retrieving configuration policy updates via Policy Sidecar | 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 | This will be replaced with CPS for Jakarta |
CPS | Used by SON-handler and 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 | |
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 |
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 | R10 M2 | https://gerrit.onap.org/r/c/dcaegen2/+/121898 |
SliceAnalysis Ms | API support for data aggregation based on NSI/NSSI; this will be consumed by OOF | Reviewed | R10 M2 | NSI/NSSI Selection based on resource occupancy levels |
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 |
Consul | 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.
- Functional test plan
- 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 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.
Gaps identified | 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).
Risk identified | Mitigation Plan | Contingency Plan |
---|---|---|
Due to upstream dependency on NIFI project, some of MOD (NiFI) components (designtool/gen-processor/nifi-registry) will remain in java 8 | Request exception for SECCOM. Assess migration to use new MOD2 standalone components for onboarding (based on community resource/support) |
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: Jakarta and all the supporting project agreed to comply with these dates.
Team Internal Milestone
This section is optional and may be used to document internal milestones within a project team or multiple project teams. For instance, in the case the team has made agreement with other team to deliver some artifacts on a certain date that are not in the release milestone, it is erecommended to provide these agreements and dates in this section.
It is not expected to have a detailed project plan.
Date to be completed by | Sprint | #No of days | Deliverable |
---|---|---|---|
Key dates for Jakarta release - Release Planning: Jakarta | |||
M2 | DCAE Jakarta Sprint 1 (Planning) |
| |
M2-M3 | DCAE Jakarta Sprint 2 (Development) |
| |
M3 | DCAE Jakarta Sprint 3 (Code Freeze) |
| |
M4 | DCAE Jakarta Sprint 4 (Container Release/artifact) | Finalize containers/jars for Jakarta release and submit patch to OOM for revisions | |
RC | Integration/Sign-Off |
|
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
Other Information
Vendor Neutral
If this project is coming from an existing proprietary codebase, ensure that all proprietary trademarks, logos, product names, etc. have been removed. All ONAP deliverables must comply with this rule and be agnostic of any proprietary symbols.
Free and Open Source Software
FOSS activities are critical to the delivery of the whole ONAP initiative. The information may not be fully available at Release Planning, however to avoid late refactoring, it is critical to accomplish this task as early as possible. List all third party Free and Open Source Software used within the release and provide License type (BSD, MIT, Apache, GNU GPL,... ). In the case non Apache License are found inform immediately the TSC and the Release Manager and document your reasoning on why you believe we can use a non Apache version 2 license.
Each project must edit its project table available at Project FOSS.
Charter Compliance
The project team comply with the ONAP TSC Charter OBSOLETE 7 1 CLEAN.pdf.