Versions Compared

Key

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

...

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 with SDN-R bundles run 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
  • Da

Plan

...

  • Infrastructure Jenkins => Check

Status

Done

  • Today: neon java 8: 2.0.0
  • Step1: neon java 11: 2.0.1alpine-j11-image
  • Step2: sodium java 11: 2.0.2
  • Step3: sodium java 11+enforcer:2.0.3

possible solutions

...

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

...

ccsdk-parent (artifactId):
  java 8: unchanged
  java 11: <artifactId>-j11

features:
  java 8: unchanged
  java 11: <artifactId>-j11

    • 1-SNAPSHOT 
    • enforcer disabled Java8 and Java11 are accepted.

Problems

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

...

  • docker image names:
    • sdnc-j11-image

...

  • Java code and libs are compatible

...

  • Piece by piece migration path

...

  • different artifacts with same function in nexus
  • feature names for container to start will be renamed

...

SDN-R Code

...