Releases: PelionIoT/maestro
Releases · PelionIoT/maestro
v3.0.0
v2.10.0
v2.9.0
Release notes -
- Gateway capabilities - Allows gateways to advertise the features supported by the platform. Maestro utilizes Edge Core's GRM JSON-RPC APIs to add to the gateway device's LwM2M resources. The registered resources are added under Pelion's reserved FeatureMgmt LwM2M object - 33457 with 3 resources - 0 - featureID, 1 - enabled, 2 - config.
- Remote config management via LwM2M - FeatureMgmt config resource allows users to remotely view the current configuration of the feature and also push a config update using the LwM2M cloud service APIs. Maestro, on receiving an update, writes the content to the file path specified in the respective parameter config_filepath.
- Removed parsing and generation of self-signed certificates. Also removed the platforms rp200 and wwrelay which are no longer supported.
Known issue -
The FeatureMgmt config resource is initialized with max 3.8KB of file content. The remaining file content is truncated during initialization. This is most likely due to limitation of gorilla/websocket library, but needs further investigation. Although, Pelion DM users can still push a file size of max 64KB via cloud service APIs.
v2.8.0
always finalize DNS when networking changes This addresses a problem where maestro is configured to manage only a subset of network interfaces on the system, maestro is configured to add/remove nameserver info, and for whatever reason the maestro-managed interface doesn't have an IP address, such as lack of DHCP server on the network connected to the maestro-managed interface.
v2.7.0
v2.6.0
- CI Improvements: Multi-machine vagrant testing
- VM disk space increase
- Coverity tests
- Moved feature tests to dev-pelion-edge repository
- Feature: DNS management
- Maestro-shell endpoint to add/delete/get DNS
- Restore DNS settings on maestro boot
- Default route flag changes