Azure IoT Edge
155 Ideas
Vote
Microsoft
6 years ago
Removing unused modules from IoT Edge devices
I am successfully able to add and remove custom modules from a deployment. However, I notice that modules that I remove through a deployment, remain on the device, occupying space. So at some point, the device's storage will get filled up with junk (outdated or unnecessary modules), leading to a system crash.This is the response I received from Microsoft - Thanks for your feedback @baharw . That is by design - you can easily integrate a direct method for example that would be responsible to remove all unused docker images on your edge device. I nevertheless suggest that you request that feature here with a business justification so others can vote.So by design, there is no cleanup of modules, and at some point, the system will crash. Industrial IoT devices are expected to run for years without a reboot. Often they are in-service for 5-10 years. During which time they may receive several updates. If there is no automatic cleanup, then by design, the system is bound to fail.I believe this is a design flaw, and not a cool to have feature.
Completed
Deploying ModulesCompleted
Microsoft
Company Response
2 years agoThank you for your feedback. We're pleased to report we've prioritized this feature and it is now available in the v1.4 release.
See docs for more details: https://docs.microsoft.com/azure/iot-edge/production-checklist?view=iotedge-1.4#configure-image-garbage-collection
Vote
Microsoft
7 years ago
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 OnDemand endpoints (e.g. via IoT-Hub), also via a restrictive corporate proxy (only https:443 permitted)Long-term operation in the above (1. and 2.) context without the necessity of cloud connectivity.The above 3 features wouls allow hybrid-environment product developers to use IoT-Edge as a single-source sollution.I am sure that this scenario comprises (or will soon comprise) many thousands of product companies.
Completed
Installing IoT Edge runtineCompleted
Microsoft
Company Response
Hi 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/
Vote
Microsoft
7 years ago
Azure blob file upload
We are planning to upgrade an existing production application from V1 to V2. In addition to streaming data (as messages to Azure IotHub), we also upload hourly aggregated data to Azure blob store. Can you share approximate time-lines when V2 can have support for Azure blob upload?
Completed
Developing Customer ModulesCompleted
Microsoft
Company Response
2 years agoPlease see the documentation for details on the blob storage module.
Vote
Microsoft
5 years ago
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...
Completed
Developing Customer ModulesCompleted
Microsoft
Company Response
2 years agoThe capability to do this was first introduced with 1.2 as part of the identity service and support for PKCS11 and is now also part of the latest 1.4 LTS release. For an E2E example of using this to implement the zero-touch provisioning blueprint, take a look at https://aka.ms/iotedge-tpm2cloud.