Support adding ASA modules

[jackt-moran]

Out of curiosity, where does this currently stand? I recently ran into issues running an ASA module with the dev tools and am wondering if this is a known issue. For context, the ASA container starts without issue, but it cannot download and start it's job.

[marianan]

Hello @LazarusX , thanks for your request. I have a few questions to help me understand the scope and priority of your request:

1. How are ASA modules related to your scenarios? What would an end to end use case look like?
2. Are there any workarounds to support the implementation of your scenario today given the lack of support in iotedgedev? Thanks

[konichi3]

Hi @LazarusX @jackt-moran

Just to ensure we are on the same page here. ASA module means Azure Stream Analytics module we presume. We have certified ASA edge module that can be deployed to an IoT Edge device.

https://azuremarketplace.microsoft.com/en-us/marketplace/apps/Microsoft.StreamAnalyticsJob?tab=Overview

It would be good if you can provide the repro steps and the exact issue you are encountering

[jackt-moran]

Hi @konichi3, I can confirm that by ASA I'm referring to the Azure Stream Analytics module. I will have to get back to you with more details, if needed, but roughly the reproduction steps/issue are as follows:

1. Create an IoT Edge deployment with a published ASA Edge Job as a part of the deployment.
2. Use iotedgedev to run the deployment locally.
3. The containers should all start up without issue.
4. The ASA container will not be able to download the job definition (and it will continue trying forever).

Ultimately, the issue is step 4. Here is where I can provide more specific logs in the future. From memory, it seemed like the issue was related to the ASA container/module not having access to the internet, although I'm not familiar with the inner-workings of iotedgedev so this is only a theory at this point. Overall the repro should be straightforward, especially if you are familiar with publishing/deploying ASA IoT Edge modules.

[jackt-moran]

It may also be worth pointing out that I do have a workaround in place for my local development environment, although it is sub-optimal. Essentially we bypass ASA entirely using a script that modifies our deployment template for local development purposes. This is less than ideal because we need a script to create a development version of our deployment template and we have no way to test our ASA Edge Jobs locally.

[konichi3]

Hi @jackt-moran

Thank you very much for additional information. If you don't mind, can you expand step #1 to help us reproduce the issue in-house?

Do we need to deploy the Azure Stream Analytics module to the IoT Edge? (https://azuremarketplace.microsoft.com/en-us/marketplace/apps/Microsoft.StreamAnalyticsJob?tab=Overview)

Create an IoT Edge deployment with a published ASA Edge Job as a part of the deployment

Any further details would be greatly appreciated.

Thank you!