Azure IoT Edge
Azure IoT Edge moves analytics and logic out of the cloud and onto your on-premises devices. Using a cloud interface, you can deploy either Azure service logic or your own code to devices without having to physically access them. And offline capabilities mean that you can extract business insights anywhere, without worrying about maintaining constant communication with a cloud service.
More details about the services are available in the documentation.
-
Make IoT-Edge (V2+) usable (again) in products which require both OnPrem and OnDemand deploy
In many industries (e.g. medical, energy, aeronautics) companies must produce products that can also be installed in environments where no internet connectivity is available/permitted. These same products however, are also often installed in places where they can leverage cloud (OnDemand) capabilities. If IoT-Edge ist to be applicable for such products, it must (by design) provide for:
1. Installation from download or USB-stick including configuration via config file or local API (as did Edge V1)
2. Provide and abstraction layer to the external communication (as was done via Edge V1 Modules) enabling a configurable routing to use OnPremises endpoits (REST) or…64 votesHi Richard, item #3 has been addressed with the public preview of extended offline feature work. You can find out more about it at the blog post below. The rest of the issues you raise will take longer for us to add to the product.
https://azure.microsoft.com/en-us/blog/extended-offline-operation-with-azure-iot-edge/
-
Store Private key for X.509 based DPS securely on HSM
Use the X.509-based enrollment in DPS in IoTEdge without storing the private key on file system.
The idea is to store the Private Key in a HSM and let it never leave.
At this moment, the x.509 provisioning mode only supports a private key on the file system...
35 votes -
(Cloud-triggered) IoT Edge Runtime Updates
Provide a way of an (automatic) cloud-triggered update mechanism for the IoT Edge Runtime through IoT Hubs Device Management. Providing update capabilities not only for the containers but for the runtime and even the underlying OS is crucial for IoT Scenarios.
26 votesDevice update for IoT Hub is now in public preview and this sample shows how to update an IoT Edge device with ADU.
-
Hierarchy possibilities for edge devices.
The purpose is to have for example 5 incoming sensors in the 'sensor' edge device where we can do some calculations on the edge. The output goes to another edge device, where again we can do some calculations on the edge with input from other similar 'sensor' edge devices. The last edge device in the chain will send the data to the IoT Hub.
25 votesCheck out the public preview for IoT Edge in a nested hierarchy.
-
Support Node.js and Python Edge modules on Windows
Currently Node.js and Python custom Edge modules are only supported in Linux containers and therefore are not supported on Windows IoT or IoT Core platforms/devices as Linux containers are not supported on Windows in production. Linux containers should be supported on Windows (IoT Enterprise and IoT Core) or Python and Node.js modules should compile & run in Windows containers.
15 votesThe path forwards for running Node.js or Python containers on Windows will be to use a Linux container. Please check out the following preview.
-
Any plans to support Yocto on ARM32?
This post: https://docs.microsoft.com/en-us/azure/iot-edge/support indicates that Yocto on ARM32 is not supported. Will it be? And, if so, will the ARM Python SDK for IoT Edge (suggested here: https://feedback.azure.com/forums/907045-azure-iot-edge/suggestions/34976278-arm-python-sdk-for-azure-iot-edge) work on Yocto?
9 votesWe have published preview layers for IoT Edge on Yocto – https://github.com/azure/meta-iotedge. There is still work to be done before this becomes a Tier 1 OS; however you can start playing with it and providing feedback now.
As far as Python support, you should probably be able to build a Yocto image that supports Python. You’ll have to include the layers required by the Python SDK. This SDK is going through a rewrite at the moment; however you can see a preview at – https://github.com/Azure/azure-iot-sdk-python-preview
-
Support for aarch64 based platforms
It would be great if support could be extended for deploying the run time on aarch64 based platforms, a lot of industrial platforms being launched on the market are based on Cortex-A53.
9 votesPreview support for ARM64 is available in the 1.0.8 release.
-
Low bandwidth / partially connected: message delivery priority
For scenarios with low bandwidth and connectivity issues sending messages in the FIFO order of the message cache after being offline is not working. We need a way to specify "important" messages (delivery priority) that needs to be sent before trying to send all other messages from the msg cache. Specifying different TTL values for different priorities would be necessary as well.
8 votes -
ARM Python SDK for Azure IoT Edge
Make the Python SDK for creating IoT Edge Modules also available for ARM cpu's and Windows.
The vast selection of python libraries, and ARM devices with python support, makes it an ideal choice for rapid development of Edge Modules.
8 votesThe Python SDK is going through a rewrite at the moment. Once that is complete it will be supported on both Linux and Windows. You can find a preview of the rewrite at – github.com/Azure/azure-iot-sdk-python-preview
-
Issue iotedge commands from Azure
It would be great to issue iotedge commands from Azure on specific devices. Especially the "iotedge logs" command to see what is happening on a device remotely.
7 votesHere are a couple logging related commands that you can run from the cloud.
https://docs.microsoft.com/en-us/azure/iot-edge/how-to-edgeagent-direct-method
-
Local Edge N+M high availability and scalability (no cloud connection required after setup)
1) Deploy Edges as local clusters such that they can suffer failure and there is a high availability strategy that doesn't require a cloud connection.
2) Edge scalability to horizontally add nodes to the Local Edge Cluster. Maybe it kind of behaves like Docker Swarm. i.e. Say I have a pretty intense preprocessor for data prep before handing it to ML Inference. That could get scaled out across multiple nodes in a Local Edge Cluster.
3 votesOur public preview of IoT Edge integration with Kubernetes is the first step towards running IoT Edge on clusters.
https://docs.microsoft.com/en-us/azure/iot-edge/how-to-install-iot-edge-kubernetes
-
edgehub status in built-in metrics
Hi,
It would be very convenient to have a status of the edgehub regarding the following steps during startup :- starting
- ready
- ... ("problem" or something ?)
For our use case, we need to reboot frequently our edge device and our modules wait edgehub to be ready. For now, we are waiting these messages in logs :
- "Started MQTT head"
- "route: FROM /messages/* INTO $upstream"
When we see those mesages, we know that edgehub is ready for receiving messages and can forward them to iothub. But parsing logs is not a good solution, it would be great to use built-in…
1 voteCheck out version 1.0.10 of IoT Edge. The runtime now produces a bunch of metrics. Please let us know if there are others that you would like to see!
https://docs.microsoft.com/en-us/azure/iot-edge/how-to-access-built-in-metrics
- Don't see your idea?