Report Issue

Integration/Distribution

Major Features

odl-integration-all

odl-integration-compatible-with-all

Managed distribution archive

Full distribution archive

Documentation

Security Considerations

  • Karaf 4 exposes ssh console on port 8101. The security is basically the same as in upstream Karaf of corresponding versions, except library version overrides implemented in odlparent:karaf-parent. See Securing the Karaf container

Quality Assurance

CSIT job: https://jenkins.opendaylight.org/releng/job/distribution-csit-1node-userfeatures-all-fluorine

No additional manual testing was needed.

Migration

Every distribution formal release comes with new and deprecated project features as well as new Karaf version. Because of this it is recommend to perform a new ODL installation.

Compatibility

Test features change every release but these are only intended for distribution test.

Bugs Fixed

Known Issues

  • ODLPARENT-110

    Successive feature installation from karaf4 console causes bundles refresh.

    Workaround:

    • Use –no-auto-refresh option in the karaf feature install command.

      feature:install --no-auto-refresh odl-netconf-topology
      
    • List all the features you need in the karaf config boot file.

    • Install all features at once in console, for example:

      feature:install odl-restconf odl-netconf-mdsal odl-mdsal-apidocs odl-clustering-test-app odl-netconf-topology
      
  • ODLPARENT-113

    The ssh-dss method is used by Karaf SSH console, but no longer supported by clients such as OpenSSH.

    Workaround:

    • Use the bin/client script, which uses karaf:karaf as the default credentials.

    • Use this ssh option:

      ssh -oHostKeyAlgorithms=+ssh-dss -p 8101 karaf@localhost
      

    After restart, Karaf is unable to re-use the generated host.key file.

    Workaround: Delete the etc/host.key file before starting Karaf again.

End-of-life

Version feature is removed in Fluorine release.

Standards

No standard implemented directly (see upstream projects).

Release Mechanics

See Managed Release