DCAEGEN2-3037 (EPIC) - Story DCAEGEN2-3095 /DCAEGEN2-3336 (RESTConf)

DCAEGEN2-3335 - VESOpenAPI

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.

DCAEGEN2-3278

DCAEGEN2-3315

DCAEGEN2-3313

DCAEGEN2-3030

REQ-443 - CONTINUATION OF CII BADGING SCORE IMPROVEMENTS FOR SILVER LEVEL

Global-REQ 

DCAE passed silver badging; Gold badging improvements dependent on LF wide policy/infra updates.

(No new impact for DCAE)

NA

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

Global-REQ

REQ-438 - COMPLETION OF JAVA LANGUAGE UPDATE (v8 → v11)

Global-REQ

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

(No new impact for DCAE)

REQ-441/REQ-1070 - LOGS MANAGEMENT - PHASE 1: COMMON PLACE FOR DATA - London RELEASE

Global-REQ

Tracked under DCAEGEN2-3067

REQ-1073 - Using basic image from Integration  

(No new impact for DCAE in London release)

NA

REQ-1072 - Standardized logging fields REQ-1341 - Standardized logging fields - Java London release 

Will need updates to several DCAE java component - no resource

(only vescollector updates committed by AT&T)

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

• 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

No change for this release

https://git.onap.org/dcaegen2/tree/docs/sections/apis/pmsh_swagger.json

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