The NotificationProxy is part of the HighPerformanceNetworkInterface.
The NotificationProxy allows subscribing for DeviceNotifications and ControllerNotifications according to the ONF TR-532 definitions.
It encapsulates all necessary formats and communication required for that. This includes:
- It opens the necessary permanent HTTP connections for receiving notifications of all controllers.
- It opens the necessary permanent HTTP connections for receiving notifications of all mounted devices.
- Wherever required, it is translating notification formats (e.g. ODL=>ONF or IETF=>ONF).
- It translates the event stream based method for forwarding notifications applied by OpenDaylight to the webhook based method applied in the MW SDN application layer.
- It removes duplicates potentially caused by the controller architecture.
The NotificationProxy significantly reduces the implementation efforts of every application that requires receiving notifications. This includes not just Closed-Loop-Automation applications, but also very fundamental Inventories.
In order to configure the SDN controller login, you have to edit these lines in the .env file of your docker-compose workspace. There are two basic auth logins for controller notifications resp. device notifications:
CONTROLLER_USER=xxx CONTROLLER_PASSWORD=xxx
DEVICE_USER=xxx DEVICE_PASSWORD=xxx
The v1.0.2 release adds the following specification changes:
- update the specification to use the new ApplicationPattern release 2.1.2
- operation client update for MWDI to the latest MWDI spec version 1.2.0
There were no additions or changes to individual services or other bug fixes.
./.