Contents

Major Features

• USC Agent provides proxy and agent functionality on top of all standard protocols supported by the device. It initiates call-home with the controller, maintains live connections with the controller, provides demux/mux for packets with the USC header, and authenticates the controller.

• USC Plugin is responsible for communication between the controller and the USC agent . It responds to call-home with the controller, maintains live connections with the devices, acts as muxer/demuxer for packets with the USC header, and provides support for TLS/DTLS.

• USC Manager handles configurations, high availability, security, monitoring, and clustering support for USC.

• USC UI is responsible for displaying a graphical user interface representing the state of USC in the OpenDaylight DLUX UI.

Target Environment

For Agent

• The USC Agent C Code is available at https://github.com/rchuppala/usc_agent

• Follow the README instructions to build, install, and execute.

For Execution

• Requires Java 7 compliant runtime environment.

• Follow the OpenDaylight Beryllium installation and user guide documentation to install OpenDaylight Beryllium including USC features.

For Development

• Requires Java 7 compliant runtime environment, Maven version 3.1.1.

• Follow the OpenDaylight Beryllium installation and user guide documentation to install OpenDaylight Beryllium including USC features.

• USC UI development requires DLUX set up in developer mode: DLUX Developer Mode

Known Issues and Limitations

• 3402: USC features has configuration issues with 3-node cluster environment.

Testing methodology

• Code is covered by unit and integration tests

• System Tests are performed by CSIT jobs using java test agent.

Changes Since Previous Releases

External facing functionality not changed since previous release, including external user facing API and configurations.

Bugs Fixed in this Release

Bug Report

Migration from Previous Releases

Nothing beyond general Beryllium migration requirements.

Compatibility with Previous Releases

Nothing beyond general Beryllium compatibility constraints.

Deprecated, End of Lifed, and/or Retired Features/APIs

Nothing deprecated, EOL.