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.
-
Support X.509 certificates in IoT Edge for Raspbian (Linux) and the Device Provisioning Service (DPS)
We are using a Raspberry Pi Zero W for a large-scale IoT sensor rollout. Our plan is to use IoT Edge on Raspbian (Linux) to run our Python software on the devices and leverage the IoT hub to deploy our code via modules to our devices. We also want to use the IoT hub Device Provisioning Service to further automate the rollout of newly added devices. The goal is to make this scalable to 1.000 devices as a Proof of Concept, and in a production phase scale up to 50.000-100.000 devices.
We've tried to follow the tutorial by Microsoft to…
55 votes -
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…50 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/
-
Support Ubuntu Core
Add Ubuntu Core as supported Operating Systems. It is becoming a preferred "secure by default" OS which is preinstalled on many IoT Gateways. E.g. Dell Edge Gateways
35 votesWe are aware of this OS and want to get to it; however CentOS 7.5 and Yocto are currently higher on our priority list.
-
More options, or configuration parameters, of storeAndForwardConfiguration
storeAndForwardConfiguration has a parameter, timeToLiveSecs to specify offline period to retain data.
Preferable to add following 3 parameters to storeAndForwardConfiguration
1. Limit the amount of disk usage to be used for SnF feature.
2. Specify the directory/path of storage for SnF feature
3. Flush un-forwarded messages in SnF memory out to specified files9 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.
7 votesWe completely agree with you that this feature will significantly improve the Azure IoT Edge experience.
-
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?
5 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.
4 votesPreview support for ARM64 is available in the 1.0.8 release.
-
Raspbian Buster
Support Raspbian Buster and Raspberry Pi 4
2 votes -
Need better parent child relationship with IoT Edge
• The Parent/Child relationship between edge and leaf devices is too restrictive for our application. We have customers that are load balanced across and within physical locations, and our devices need to roam both with and without internet connectivity. If the child device concept could be extended to contain entire deployment groups based on a certificate chain, that would be preferred. Then each of our customers could have their own intermediate certificate with each of their devices as a leaf; and that intermediate certificate could be tied to each of their Edge appliances
2 votes -
Allow installation of IOT Edge (runtime) on Windows to a different directory and drive location.
In an enterprise environment we are often restricted to where we are allowed to install software. For example all installed software should be on the D drive in Programs directory.
This is currently not possible with the iot edge runtime without modifying the IOT Edge standard installation scripts.
1 vote -
Installing IoT Edge Runtime on Core OS.
CoreOS is one of the popular container OS in the market.It will be great idea to install Azure IoT Edge Runtime(EdgeAgenet,EdgeHub,iotedged bootstrap security daemon) on Core OS.
As per https://docs.microsoft.com/en-us/azure/iot-edge/support#operating-systems CoreOS is neither in Tier-1 nor tier-2 OS list for IOT EDGE RUNTIME.
1 vote -
Iot Edge on Windows 10 Iot Core on RaspBerry Pi 3B
Windows ARM architecture is not yet supported by IoT Edge. AMD64-based IoT Core platforms should work. I want the iot edge can work anywhere iot core was installed.
1 vote -
Error occurred in apt repository
In Debian Stretch and Ubuntu 16.04, the following error occurs with the apt-get update command.
I think that the creation method of apt repository is strange.■Debian 9
root@obsiot:~# apt-get update
Hit:1 http://security.debian.org stretch/updates InRelease
Ign:2 http://ftp.plathome.co.jp/pub/OBSVX2/debian/stretch ./ InRelease
Hit:3 http://ftp.plathome.co.jp/pub/OBSVX2/debian/stretch ./ Release
Ign:4 http://ftp.jp.debian.org/debian stretch InRelease
Hit:5 http://ftp.jp.debian.org/debian stretch-updates InRelease
Hit:6 http://ftp.jp.debian.org/debian stretch Release
Get:7 https://packages.microsoft.com/debian/9/prod stretch InRelease [3232 B]
Get:10 https://packages.microsoft.com/debian/9/prod stretch/main amd64 Packages [38.0 kB]
Err:10 https://packages.microsoft.com/debian/9/prod stretch/main amd64 Packages
Writing more data than expected (38208 > 37999)
Hashes of expected file:
- Filesize:37999 [weak]
- SHA512:194ded11a350aab88b7fc1c5fee5dd6746a6bd0136ee96ad2290fc9459086daf75fbeda376ab00c0455cbeab6e64fa405f82ef0991b28322f29f30dab2aaaede
- SHA256:369f15b8a43c29e6adf6db3329576366123c6bb749ee311f5099752de06474ea
- SHA1:87f67045f0db46ee582998ba1d432b47900f5992 [weak]
- MD5Sum:38eeded94abf10a911e570233047151b [weak]
Release file…1 vote -
Support powerpc architecture
Does Azure Iot Edge Support powerpc architecture ?
If not, do you plan to support it ?1 vote -
Provision of IoT Edge Security Damon package for Tire 2 system
For the Tier 1 system, the latest IoT Edge Security Damon package is provided in the package repository (https://packages.microsoft.com/)
But for the Tire 2 system, it is not provided.
For example, for Ubuntsu 18.04 of Tire 1, iotedge_1.0.4-1_amd64.deb is provided, Regarding Debian 9, it still iotedge_1.0.0-1_amd64.deb yet.
Our products use Debian 9, and we are asked to provide packages that fix bugs from customers.
We will to build it localy and provide it at our own repository, What do you think?1 voteWe plan on hosting the Debian packages on packages.micrsoft.com once we move Debian to Tier 1 support.
I like your temporary workaround of publishing them to your own repository. You don’t even need to build them locally. We provide them with each release. For example, you can find the rpms for the 1.0.6 release at – https://github.com/Azure/azure-iotedge/releases/tag/1.0.6.1
-
Azure IoT Edge Tier 1 support for Ubuntu running on ARM32
ARM32 is by far the most popular hardware platform for edge devices, because of low cost and high reliability.
Ubuntu Core is growing in popularity. (https://www.ubuntu.com/download/iot)
It is surprising to me that there is no Tier 1 support for Ubuntu Core and ARM32.
I think that Tier 1 support for the most popular HW-SW combination would be a win-win, for Microsoft and for IoT OEMs.
1 voteSupporting Ubuntu Core is of interest for us; however there are other OS that we’re prioritizing higher. For example:
- supporting CentOS provides installers for all RPM based Linux systems.
- supporting Yocto is necessary for folks creating custom images for small devices.
I anticipate that we’ll get to Ubuntu Core once some of these other systems have been supported.
-
need a video explaining all security conceots the blog and docs are not doing as much a video can do ...
i read the docs at https://docs.microsoft.com/en-us/azure/iot-edge/iot-edge-security-manager this needs further details in form a video as this important and in form as it stands today in docs we may be missing the details …
So please shoot a good video explaining concepts and describing best practices...1 vote -
Run Edge runtime on Service Fabric
Currently Edge runtime runs on Docker. In some cases (for example: an Edge Gateways hosting some logic to support disconnected scenario) it's desirable to run Edge Runtime on Service Fabric. This would allow the Edge devices to form a reliable cluster, and take advantage of extra features of Service Fabric.
1 vote -
Environment variable $IOTEDGE_CONF needed instead of hard-coded path in scripts and executables
With respect to your declared environment variables (given in "./edgelet/iotedged/src/lib.rs", and "./edgelet/iotedge/src/main.rs"), they cover almost every aspect, except, an environment variable, which could replace the hard-coded path "-c /etc/iotedge/config.yaml" to something like "-c $IOTEDGE_CONF". The variable could either be set in scripts, or the iotedged service/daemon/manager, itself, with a default path, if its value is not already given by an argument or defined in an environment variable.
1 vote
- Don't see your idea?