Integration/Distribution

Major Features

odl-integration-all

odl-integration-compatible-with-all

odl-distribution-version

Karaf 3 distribution archive

Karaf 4 distribution archive

Documentation

Security Considerations

  • Karaf 3 exposes ssh console on port 8101. The security basically 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

Migration

  • Version feature works exactly the same as in Boron. After migration the versions are set to the new default, configurable in runtime or via configfile. The Boron configfile would work, but users are advised to consider reporting a bumped version.
  • No upgrade path for other features.

Compatibility

  • No API changes in Karaf 3.
  • Karaf features are not compatible with Boron.
    • even odl-distribution-version depends on different version of Config Subsystem.

Bugs Fixed

  • Bug 4296: At the time of Boron release, the default versions were not being set properly. Now they are.
  • Bug 7255: During Carbon deveopment -all- jobs for NETCONF started to fail. Turns out NETCONF provides two NETCONF topology managers (single node or cluster) which are incompatible with each other. Fixed by moving both out of odl-integration-compatible-with-all.
  • Bug 7493: Controller briefly used Artery, but distribution scripts were not compatible with that. After all, Artery is not used in Carbon release, but the scripts now contain information how to make them compatible if needed.
  • Bug 4219: Karaf 4 features and archives are available, but in experimental state only. NETCONF server and NETCONF connectors do not work. RESTCONF works only up to attempted re-install.

Known Issues

  • No known issues for Karaf 3.
  • Karaf 4 is highly experimental.

End-of-life

No features/APIs which are EOLed, deprecated, and/or removed in this release.

Standards

No standard implemented directly (see upstream projects).

Release Mechanics

  • Release plan
  • Major shifts in release schedule
    • Karaf 4 was running late due to difficulty of making CSIT work. Eventually Karaf 4 was moved to experimental status.
    • Team Lead was often busy, neglecting status updates.