Page Comparison

...

• Michas and Herberts topics
  • When odlsli-image is available with 1.0.1-SNAPSHOT artifacts?
  • All CCSDK/* repositories should use the same version number
    • (ccsdk/distribution)/odlsli/odlsli-alpine specifies one property for ccsdk artifacts "ccsdk.features.version" 
    • <ccsdk.features.version> replaces: <ccsdk.sli.core.version> <ccsdk.sli.adaptors.version> <ccsdk.sli.northbound.version> <ccsdk.sli.plugins.version><ccsdk.oran.a1adapter.version>
  • SDNC build logic
    • sdnc-image bases on odlsli-image
    • odlsli-image should contain
      • all artifacts from ccsdk repos
      • Repository location for ODL added to "featuresRepositories" in Dockerfile 
    • sdnc-image sets "featuresBoot" via startODL.sh script
    • only artifacts from sdnc repos are added into sdnc-image
    • Documentation: SDN-C/SDN-R images
  • • Java11 status and open points
      • Overview: 

        Jira Legacy
        server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key CCSDK-2422

      • Open issues, support requested
        • ccsdk/apps .. J8 fails
  how can work 
  • • • • who can work on this?
        • ccsdk/oran .. situation not clear 
      • First test: odlsli Running -if ccsdk-aafshiro excluded
        • Proposal: exclude "ccsdk-aafshiro" and handle as a bug (

          Jira Legacy
          server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key CCSDK-2692

          )
      • Next to proceed
        • remove all JAVA_HOME ENV in derived images
        • JENKINS: Adapt or create J11 Jenkins jobs .. who can do this?
        • use: odlsli-image based on J11
  • New Rocketchat channel for coordinating commits/issues: ccsdk-sdnc
  Open Discussion