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 10 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

possible solutions


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

ccsdk-parent (version):
  neon java 8: 2.0.0
  sodium java 11: 2.0.1
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
  • Piece by piece migration path
cons
  • Java code and libs are not compatible
    • Code adaptions for J11 are necessary
    • Compilation also necessary (question)
  • 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?

SDN-R Code

Relevant ODL Changes


  • No labels