-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: Native Python Support for Edge X Device Services #1
Comments
Hi Neelay,
Thanks for your message. Great to hear the guide has been useful!
*In regard to creating a separate Device service for your video analytics: *
If the current implementation does the job and gives satisfactory
performance I'd probably leave it as-is (if it's not broken - don't fix
it). However, if you'd like to reduce the number of hoops your data has to
pass through and possibly improve performance (as well as learn more about
the innards of EdgeX) it'd certainly be an option to create your own.
Please note that I haven't been involved with EdgeX for a long time now
since Dell Tech reduced the focus on IoT. Cloud, on CC, may be able to
offer better insights than I'm able.
*In regard to a Python SDK;*
To my knowledge there aren't any initiatives to provide a Python
SDK. However, since I'm not directly involved with the development I don't
have the latest information. I've CC'd Cloud Tsai at IOTech who likely
knows a lot more about this.
Hi Cloud,
Would you happen to know if there's an SDK for Python in the works? I
talked to Jim about it a couple of years back but haven't heard
anything since then.
All the best,
Jonas
…On Sat, 30 Jan 2021 at 23:27, Neelay Shah ***@***.***> wrote:
I really appreciated the time and thought you put into the tutorial and
was pleasantly surprised that you added python scripts to create devices as
well as send sensor data to EdgeX. Are there any plans to provide this as
an SDK for EdgeX similar to the C and Go device service sdks?
Maybe a separate question, we have been working on a video analytics
microservice based on OpenVINO and DLStreamer, and one of our samples uses
the MQTT Device Service to send in detection results to Edge X.
https://github.com/intel/video-analytics-serving/tree/master/samples/edgex_bridge
If you have any feedback on the approach - would be interested. I've also
thought that removing the MQTT bridge and using a native device service
would be another approach - but had stopped short because of the lack of a
supported python sdk. After coming across your tutorial - I'm rethinking
that approach.
Thanks!
Neelay
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIRJZSX55AXFYP3CTHTZFYTS4QJMFANCNFSM4W2LLBDA>
.
|
@jonas-werner thanks for the reference. We are working with Intel closely. Please let me know if you are interested in the commercial offering. |
@jonas-werner @cloudxxx8 Thanks for the information! We met with Jim last fall, I'll reach out to see where things are headed in regards to an OpenVINO / DL Streamer device service. |
It would be nice to see a python SDK also. |
I really appreciated the time and thought you put into the tutorial and was pleasantly surprised that you added python scripts to create devices as well as send sensor data to EdgeX. Are there any plans to provide this as an SDK for EdgeX similar to the C and Go device service sdks?
Maybe a separate question, we have been working on a video analytics microservice based on OpenVINO and DLStreamer, and one of our samples uses the MQTT Device Service to send in detection results to Edge X.
https://github.com/intel/video-analytics-serving/tree/master/samples/edgex_bridge
If you have any feedback on the approach - would be interested. I've also thought that removing the MQTT bridge and using a native device service would be another approach - but had stopped short because of the lack of a supported python sdk. After coming across your tutorial - I'm rethinking that approach.
Thanks!
Neelay
The text was updated successfully, but these errors were encountered: