SDN-R goes Sodium and Java11

ODL Information

• latest OpenDaylight Downloads

• Sodium Platform Upgrade

• ONAP Sodium release: SR3

ONAP

• Infrastructure Jenkins => Check
• Migration strategy BingBäng vs. Smooth => Specify
  • SDNC should completely move to J11
  • CCSDK ... J8 and J11?
• ODL Base image with J11

Analysis

• Java 8 compiled ODL runs successfully on base container with Java11 
• SodiumSR3 parents can be created to run to compile with Java8 and Java11
• enforcer plugin shouldn't verify usage of Java 11 in a first version

Status

Done

• Today: neon java 8: 2.0.0
• Step1: alpine-j11-image
• Step2: odl-sodium-image based on ODL Sodium SR3 and alpine-j11-image

Next

• ccsdk-parent-* (binding, odl-parent-light, singlefeatureparent) to Sodium-SR3
  • Question: New name or version 2.0.1-SNAPSHOT 
  • enforcer disabled Java8 and Java11 are accepted.

Problems

• ccsdk-aaf-shiro has hardcoded dependencies to Java8 base libs (javax.ws.*)

SDN-R Code

• Using ODL hints from here: https://docs.opendaylight.org/en/stable-sodium/release-notes/upgrade-process.html#datacontainer-implementedinterface-is-type-narrowed-in-dataobjects
  • POM change: JSR305: Use google findbugs
• Using ODL Parents
• JDK: openJDK 11
• Dev environment for J8 and J11 (for older releases)
• Most changes are in POM files
• A few changes are in the code.

Relevant ODL Changes

• oauth2 removed
  • https://jira.opendaylight.org/browse/AAA-173
  • Who is using this?
  • How to replace?