Closed vkorn closed 1 year ago
Hi Glen,
Thank you for the comments!
each service in its own directory under examples/edge/services
Ok, will change that. What about testing? To test it we need to run mqtt + server. Just use server service only for the travis tests?
clear instructions to explain usage
Will add more details
Also, I think you should remove the Agent software install instructions in horizon/RPi.md as these do not belong in any of the examples
Initial idea was to run client ("recording" part) on the rpi which requires agent installation. I can remove it of course.
Do you support arm64
I didn't make a target for it, but it should work, I don't have a device to test.
Your client and server Dockerfiles are hard-coding ENV settings, e.g
Those are just a list of setting available for each service. Each setting is exposed through userInput
As discussed over the phone, below is the list of further changes we want to see in the service (will go as a separate PR):
I've put together some basic documentation for installing the example service.
I think we're now ready for @dabooz to review.
Do you support arm64? I am trying to set this up on my Jetson TX2 but I think i just discovered that you don't support arm64? I'll move to another machine.
@TheMosquito arm64 should be supported. When you build, you need to specify that you're building specifically for arm. Are you saying that the arm support is only for arm32?
@dabooz and @t-fine going back through this PR, it may have addressed your changes? If so, can we merge it?
Example of horizon services: MQTT based system to analyze audio samples using FFT. Contains two horizon services:
To make testing easier, simple console client is made which is using pre-recorded samples and sending them in a random order to the server through MQTT.
Per email discussion we are using docker manifests instead of separate images per arch.
Please let me know if I should change docker_id from my personal to openhorizon.