Page Comparison

Table of Contents

...

Project Name	Enter the name of the project
Target Release Name	London
Project Lifecycle State	Mature. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information
Participating Company	AT&T, Nokia, Wipro, Huawei, DT, Capgemini

...

REQ#	DCAE Commit Status	DCAE Impact Assessment	DCAE JIRA #
REQ-1378 - E2E Network Slicing use case enhancements for London release	YES	AI/ML MS for IBN based closed Loop in E2E Network Slicing • Mainstreaming the ml-prediction-ms(New mS introduction) • Support for multiple slices (sNSSAIs) in training and prediction modules • Use CPS instead of Config DB • Remove RAN Simulator dependency Commitment from Kevin Tang sendil kumar Jaya kumar Ahila P /WIPRO	DCAEGEN2-3067

London Features with DCAE Impact

REQ#<Pending resource/commitment>

REQ#	DCAE Commit Status	DCAE Impact Assessment	DCAE JIRA #
REQ-1351 - External secure communication only via Ingress	NO	No resource/support available from DCAE project; changes likely in OOM charts.
REQ-1349 - Removal of AAF	Stretch-goal		OOM-3068 (DCAE Svc template updates) - Jack Lucas DCAEGEN2-3095 /DCAEGEN2-3336 (RESTConf cert dependency removal) - Kedar Ambekar DCAEGEN2-3335 - VESOpenAPI -	DCAEGEN2-3037 (EPIC) - Story DCAEGEN2-3095 /DCAEGEN2-3336 (RESTConf)

London Spec with DCAE Impact

DCAEGEN2-3335 - VESOpenAPI

REQ-1376 - DMaaP Enhancements for L release

NO

DMAAP BC removal support

BC used mainly for BulkPM flow for Feed provisioning - need assessment on switching DFC/PM-Mapper to use non-secure endpoints.

London Spec with DCAE Impact

Configurable option to enable/disable reprocessing of AAI failed lookup
Log and auto-commit (to remove failed entry) if older than x timeframe
DCAE SDK dmaap-client enhancement to support native kafka interface will be recommended. Depending on env/config/deployment properties, dmaap-client lib can serve a wrapper to switch between native kafka or MR REST api.

Commitment from

REQ#	DCAE Commit Status	DCAE Impact Assessment	DCAE JIRA #
REQ-1379 - Improve DCAE PRH to handle Early PNF Registrations	YES		Enable persistence for PRH reprocessesing DCAE SDK dmaap-client enhancement to support native kafka interface Commitment from Sangeeta Bellara / DT	DCAEGEN2-3312
DCAE MOD retirement	YES	Retired Retire MOD from ONAP/DCAE OOM charts updates Documentation Commitment from Vijay Kumar / AT&T	DCAEGEN2-3278	NA
PM-Mapper Improvement/Bug-fixes	YES	Fix issues of duplicate events handling & DR retry Commitment from Viresh Navalli / Vamshi Namilikonda Capgemini	DCAEGEN2-3315 DCAEGEN2-3313
NA	YES	Sonarcoverage improvements for DCAE components Heartbeat MS, VESCollector Commitment from Vijay Kumar Tony Hansen AT&T	Sub-Jira under EPIC DCAEGEN2-3256
NA	NOPending Assessment	DMAAP SDK standardization for DCAE Microservices (following components are using cambria client) KPI- mS mS (deferred from Kohn; need to be confirmed by Ahila P / Niranjana Y ) SON-Handler mSRESTConf mS (deferred from Kohn; need to be confirmed by Ahila P / Niranjana Y ) RESTConf (No resouce/support available from DCAE project)	DCAEGEN2-3030

London POC (DCAE impact)

REQ#	DCAE Commit Status	DCAE Impact Assessment	DCAE JIRA #
REQ-1072 - Standardized logging fields TO DO Image ModifiedREQ-1345 - Standardized logging fields - Python London release	NO	No resources for POC	NA

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	DCAE passed silver badging; Gold badging improvements dependent on LF wide policy/infra updates. (No new impact for DCAE)	NA
REQ-439/REQ-1211- CONTINUATION OF PACKAGES UPGRADES IN DIRECT DEPENDENCIES Global-REQ	Stretch-goal	DCAE Wiki - DCAE R12 London Vulnerability - SECCOM Report Commitment: DT London DCAE DCAE Wiki - DCAE R12 London Vulnerability - SECCOM Report Commitment: Kedar Ambekar / DT Team (TCAGEN2/RESTConf/PM-Mapper, DataFileCollector, VESMapper, SDK, VES-OpenAPI manager) SliceAnalysis - Shuting Qing SON-handler - Shuting Qing Following are OPEN (pending resource/commitment) PRH - Sangeeta Bellara	DCAEGEN2-3318
REQ-437 - COMPLETION OF PYTHON LANGUAGE UPDATE (v2.7 → v3.8) Global-REQ	YES	Existing DCAE python components are already compliant; New mS (ml-prediction-mS) will also meet this requirement when delivered. Covered under REQ-1378 (Commitment from Wipro Kevin Tang Ahila P /WIPRO )	NA
REQ-438 - COMPLETION OF JAVA LANGUAGE UPDATE (v8 → v11) Global-REQ	YES	Complaint with DCAEMOD deprecation. Java17 upgrade pilot targetted for PM-Mapper in London (supported by Kedar Ambekar/DT Team)	NA
REQ-432/REQ-760 - IPv4/IPv6 dual stack support in ONAP	YES	Enhance ONAP common-service template - add IPv4/IPv6 support (No new impact for DCAE)	OOM-2749
REQ-441/REQ-1070 - LOGS MANAGEMENT - PHASE 1: COMMON PLACE FOR DATA - London RELEASE Global-REQ	YES	New mS (ml-prediction-mS) will be complaint to the requirement. All other DCAE mS area already complaint STDOUT logging Commitment from Wipro Covered under REQ-1378 (Commitment from Kevin Tang Ahila P /WIPRO )	Tracked under DCAEGEN2-3067
REQ-1073 - Using basic image from Integration	YES	(No new impact for DCAE in London release)	NA
REQ-1072 - Standardized logging fields REQ-1341 - Standardized logging fields - Java London release	Stretch-goalNO	Will need updates to several DCAE java component - no resource (only vescollector updates committed by AT&T)	DCAEGEN2-3257
REQ-1342 - Retirement of unmaintained repos	YES	DCAE MOD will be retired in London release Commitment from Vijay Kumar / AT&T	DCAEGEN2-3278

Best Practices

REQ#	DCAE Commit Status	DCAE Impact Assesment	DCAE JIRA #
REQ-396 - Clearly split ONAP code and use case code	YES	No new impact; already compliant	NA
REQ-399 - ONAP Projects dealing with GUI must provide GUI test suites	NO	DL Admin is only DCAE component with UI No resource/commitment	NA
REQ-1073 - Using basic image from Integration	YES	No new impact; already compliant	NA
REQ-1346 - Software BOMs	YES	No new impact; already compliant	NA

Note: The above commitment should be consistent with London Impact View per Component at M2.

...

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+

...

Jira Legacy

server	System Jira
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues	20
jqlQuery	project =dcaegen2 and issuetype in (epic) and fixversion='Kohn Release' = DCAEGEN2 AND fixVersion = "London Release" AND type = Epic AND status not in (Closed) AND labels not in (relman)
serverId	4733707d-2057-3a0f-ae5e-4fd8aff50176

...

Jira Legacy

server	System Jira
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues	20
jqlQuery	project=dcaegen2 and issuetype in (story) and fixversion = 'Kohn Release' =dcaegen2 and issuetype in (story) AND fixVersion = "London Release" AND status not in (Closed) AND labels not in (relman)
serverId	4733707d-2057-3a0f-ae5e-4fd8aff50176

...

Indicate where your project fit within the Amsterdam architecture diagram_1.0.0.pptx.

Image RemovedImage Added

DCAE Interfaces

Image RemovedImage Added

Platform Maturity

...

Area	Actual Level	Targeted Level for current Release	Comments
Performance	1	1	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)
Stability	2	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
Resiliency	2	2	0 – none 1 – manual failure and recovery (< 30 minutes) 2 – automated detection and recovery (single site) 3 – automated detection and recovery (geo redundancy)
Security	1	1+	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
Scalability	1	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
Manageability	1	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
Usability	1	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

...

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)
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	Currently Available	R10	No change for this release https://git.onap.org/dcaegen2/tree/docs/sections/apis/pmsh_swagger.json
SliceAnalysis Ms	API support for data aggregation based on NSI/NSSI; this will be consumed by OOF	Currently Available	R10	No change for this release https://git.onap.org/dcaegen2/tree/docs/sections/apis/swagger_slice_analysis.json https://wikilf-onap.onapatlassian.orgnet/wiki/download/attachments/11774039616493831/slice-analysis-swagger.yaml?version=1&modificationDate=1640159785000&api=v2

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

1.9.x

Name	Description	Version	NIFI	Apache NIFI		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.
    - https://sonarcloud.io/organizations/onap/projects?search=dcaegen2
  - Functional test plan
    - DCAE R12 London 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 R12 London 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 flowMOD

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.

...

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)

MOD retirement under assessment

DCAEGEN2-3019 (J) Documented under London Risks

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

...

Versions Compared

Old Version 4

New Version Current

Key

London Features with DCAE Impact

London Spec with DCAE Impact

London Spec with DCAE Impact

London POC (DCAE impact)

Best Practices/GLOBAL Requirements

Best Practices

DCAE Interfaces

Platform Maturity

Third Party Products Dependencies

Testing and Integration Plans

Gaps

Resources