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 2 Next »

Topics:

  • Michas and Herberts proposals
    • 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:  CCSDK-2422 - Getting issue details... STATUS
      • Open issues, support requested
        • ccsdk/apps .. J8 fails how can work 
        • ccsdk/oran .. situation not clear 
      • 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



  • No labels