Contents
Project Name
Unified Secure Channel
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 with the controller, acts as a demuxer/muxer 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 a 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.
Non-Code Aspects (user docs, examples, tutorials, articles)
Architectural Issues
Security Considerations
Quality Assurance (test coverage, etc)
- JUNIT: Code is covered by unit and integration tests, but Sonar does not currently track test coverage correctly. USC covered by 41 unit test cases.
- Manual: External System Tests are performed manually in Lithium (will automate in Beryllium).
End-of-life (API/Features EOLed in Release)
Bugzilla (summary of bug situation)
- Bug List
- 3402: Cast failure on exception branch in view channel rpc request. Workaround: A null shard service throws this exceptions, so wait until shard service is available before using the view channel API.
- 3291: Remote channel request should use same controller for same session. Workaround: Use same controller for all sessions.
- 3290: Remote session id conflicts with the local session id using same channel. Workaround: Suggest to restart usc if this edge case occurs due to session id conflicts.
Standards (summary of standard compliance)
Schedule (initial schedule and changes over the release cycle)