Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

ODL Information

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

Plan

ccsdk-parent (version):

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

possible solutions


Solution 1 (versioning)Solution 2(artifcat-suffix)

ccsdk-parent (version):

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

features:
  neon java 8: 1.0.X
  sodium java 11: 1.1.X

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

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

this has impacts on
  • docker image names:
    • sdnc-j11-image
pros
  • Java code and libs are compatible
  • Piece by piece migration path
cons
  • different artifacts with same function in nexus
  • feature names for container to start will be renamed
open points
  • neon version code compatible with sodium j8? No

SDN-R Code

Relevant ODL Changes


  • No labels