06-13-2019 11:01 AM
06-13-2019 11:01 AM
IoT Edge is now GA on Windows Server ‘19
IoT Edge 1.0.8 RC was released this past week
Downstream devices can connect to an IoT Edge device with a x.509 cert
GA on Windows Server ‘19
IoT Edge is now GA on Windows Server 2019 using IoT Edge 184.108.40.206. Windows IoT Core remains in public preview and will hit GA soon.
Azure IoT Edge continues to drive a lot of excitement for Azure IoT. Our presence at the //Build/ conference this past month reinforced our momentum. The product was featured prominently in Sam George’s IoT keynote, had its own breakout session, received a lot of foot traffic at the floor booth dedicated to the product, and packed a series of hands on labs. It was exciting to share all the great work our team has been doing with Microsoft developers and humbling to have Forbes call our Kubernetes integration as one of the 10 most interesting announcements at the conference.
Edge + x.509
Devices can use a x.509 cert to authenticate and connect to an IoT Edge device acting as a transparent gateway. Both thumbprint and certificate authority methods of authentication are supported. Before, the only way devices authenticated to IoT Edge acting as a transparent gateway was through SAS tokens. You can find out details about how to use this feature in our documentation.
IoT Edge 1.0.8 RC
A release candidate for IoT Edge 1.0.8 was published this past week.
Features contained in the 1.0.8 RC include the following:
Linux ARM64 (preview)
Artifacts for RCs must be installed manually:
SDK - 1.0.8 has been tested against the 1.2.1 Client SDK. We recommend updating your modules to use this version.
1.0.8 RC contains a fix that allows Edge Hub to utilize all cores when emptying message queues to the cloud. This provides a 6x-8x improvement in our IoT Edge tests.
These types of perf numbers are seen when using an IoT Edge device as a transparent gateway and NOT doing any intermediate processing (in a module) on messages sent from downstream devices to the cloud. Edge Hub hits a single threaded bottleneck once you start passing messages between modules. This single threaded pipelining is necessary to maintain message ordering guaranteed by IoT Hub and Edge Hub.
New direct method to publish module logs to blob store (experimental)
The edge agent has a new direct method that can be invoked which will upload desired logs to the specified blob store location. This is an experimental feature and it is subject to change. We're sharing here for early feedback