Versions Compared

Old Version 8

changes.mady.by.user Vijay Venkatesh Kumar

Saved on

compared with

New Version 9

changes.mady.by.user Vijay Venkatesh Kumar

Saved on

Key

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

...

REQ#DCAE Commit StatusDCAE Impact AssesmentDCAE JIRA #

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

Global-REQ 

YES

CII badging score improvement

Commitment from AT&T 

DCAEGEN2-3192

REQ-439 - CONTINUATION OF PACKAGES UPGRADES IN DIRECT DEPENDENCIES

Global-REQ

TBC

<Pending SECCOM analysis/report>

Commitment TBD

TBA

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

Global-REQ

YES

(No new impact for DCAE in K release)

NA

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

Global-REQ

No
  • dcaemod-designtool
  • dcaemod-nifi-registry

Exception will be filed with SECCOM for waivers due to upstream (NIFi) dependency

DCAEGEN2-3019 (J)
REQ-432 - IPv4/IPv6 dual stack support in ONAPYES

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

(No new impact for DCAE in J release)

OOM-2749 

REQ-441/REQ-1070 -  LOGS LOGS MANAGEMENT - PHASE 1: COMMON PLACE FOR DATA - JAKARTA KOHN 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 

Tracked under DCAEGEN2-3067

REQ-1073 - Using basic image from Integration  

YES

(No new impact for DCAE in J release)

NA

REQ-1072 - Standardized logging fieldsYES (for new Ms only)

No change planned for existing DCAE microservice. New mS (ml-prediction-mS) will be developed to be complaint to this Best-practice requirement. 

Commitment from Wipro

Tracked under DCAEGEN2-3067

...

The milestones are defined at the Release Planning: JakartaKohn and all the supporting project agreed to comply with these dates.

...

Date to be completed bySprint#No of days Deliverable 
Key dates for Jakarta KOHN release - Release Planning: JakartaKohn
M2DCAE Jakarta Kohn Sprint 1 (Planning)
  • Finalize DCAE scope and committment
  • API definition formalized and shared with impacted teams
M2-M3DCAE Jakarta Kohn Sprint 2 (Development)
  • 50% or more of Functional delivery completed
  • Atleast 60% of release/compliance (coverage & security)
  • Integration test plan completed
  • CSIT/automated test delivery
  • SDK version to be baselined and released
  • Documentation repo updates (API updates & new MS/component) -  Jakarta Kohn Documentation
M3 DCAE Jakarta Kohn Sprint 3 (Code Freeze)
  • All code intended for release MUST be submitted into gerrit
  • Minimum 80% code coverage
  • 100% of release/compliance (coverage & security)Global Requirement & Best-Practice) 
  • Validate deployment/integration with ONAP/DCAE deploy
  • Update OOM chart/blueprint/documentation to reflect correct version
  • Documentation update for deployment/configuration/architecture/logging
M4DCAE Jakarta Sprint 4  Kohn Sprint 4  (Container Release/artifact)

Finalize containers/jars for Jakarta release and submit patch to OOM for revisions

RCIntegration/Sign-Off
  • Fix Integration blockers and high priorty issue
  • Demo for new components introduced
  • Pair-wise testing
  • Branching

  • 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

           Jakarta Kohn Documentation

Other Information

    • Vendor Neutral

...