That's the idea, yes. However, we are currently implementing support for using Apache Kafka as an alternative messaging infrastructure (i.e. replacing Dispatch Router and Artemis). This is already available in Hono 1.9 as a tech preview and I guess in the upcoming 1.10.0 version we will declare this fully supported ...
Yes. For that purpose we have also defined kafka based versions of the north bound APIs (e.g. https://www.eclipse.org/hono/docs/1.9/api/kafka-api/ and https://www.eclipse.org/hono/docs/1.9/api/telemetry-kafka/ and https://www.eclipse.org/hono/docs/1.9/api/command-and-control-kafka/)
Hi all, I've question concerning the quarkus images. Some time ago I noticed the quarkus images didn't do what I expected. Yesterday I installed the latest hono version on our test cluster and the quarkus images were used automatically. However, it seems some configuration is not passed to the container. I can't seem to find where the configuration (in code) is coming from. I found
QuarkusMqttProtocolAdapterProperties but couldn't find where this was populated. Do I have to provide the configuration in a different way for these quarkus containers?
17 replies
Short feedback after all my struggle with the initial setup and getting everything right in my tooling we finally start to use Hono and really like it. Very well done guys (special thanks to @sophokles73 for all the help). I try to prepare a little PR with some minor updates in the documentation (things that confused me) to help others to ease their „onboarding"
@sophokles73 Of course. We have a SaaS Offering for Machine Builders (not Factories) where we give them their own whitelabeled „Portal“ to communicate with their machines as well as their clients. So one part of the system is a little bit like the Azure IoTHUB / Boschs IoT Suite but more focused on Metadata and their relation with the Machine and so on. Another crucial part for us is the data history so we rely heavily on Apache IoTDB (there were / are also discussions in the #eclipse/ditto channel about some possibilities to integrate timeseries storage with Ditto in some way)
But simply put.. we have gateways that read data from machinery (a bit like Kura) and sends them via Messaging (currently MQTT only) to our backend where we then do several things with it
And we now decided to migrate to Hono for simple scaling reasons. Not about the infrastructure but the device management as our customer base (luckily) grows : )
@samrose It is possible. There used to be deployment scripts for Docker Swarm, but they were removed a long time ago. The deployment of the sandbox VM was still running on Docker Swarm until recently. That can still be found in the Git history for inspiration: https://github.com/eclipse/hono/tree/5505c3c6f6d4cb2ba70828188c9e38af2d02f1de/deploy/src/main/sandbox
thank you!
Hi, I was trying to run the quarkus images just now (version 1.10.0) and I stumbled upon a change in the lora adapter. In the spring lora adapter I'm not obliged to confugre following property:
As you might imagin, I would not like to change my deploy because I'm adding a new tenant. Why can't the lora adpater look at the gateways with a commandEndpoint and add those dynamically to the used tenants?
hono.lora.commandEnabledTenants. I was wondering why this is required in the quarkus version?As you might imagin, I would not like to change my deploy because I'm adding a new tenant. Why can't the lora adpater look at the gateways with a commandEndpoint and add those dynamically to the used tenants?
This is probably a bug in the
LoraProtocolAdapterOptions configuration class where the corresponding property is not optional. Anyway, it looks like LoraProtocolAdapterProperties.getCommandEnabledTenants() is never used anywhere in the Lora adapter so I guess we can simply remove the configuration property altogether.
@/all I would like to start planning for Hono 2.0.0. Most imminent questions FMPOV are: 1) release time frame and 2) breaking changes.
Personally, I would like to see the 2.0.0 release by end of Q1 2022. At a minimum I would like to remove the already deprecated components/modules like the
Personally, I would like to see the 2.0.0 release by end of Q1 2022. At a minimum I would like to remove the already deprecated components/modules like the
client module, the Device Connection service, the File based registry and the Spring Boot based variants of the components. However, we should also take the opportunity to introduce other breaking changes to existing external APIs that we consider helpful/necessary. Thoughts?
Oh, and I think we should remove support for Java 8 from the
core module and upgrade to Java 17 code level.
@b-abel There are currently four PRs addressing #2837 and it is kind of hard to keep track. Are they all still relevant/required or can you maybe close some of them?
2 replies
Hi all, as you know we are installing our IoT solution on customers private clouds. This means we also would like to rely on the managed kafka cluster from the customer. However, this means we won't always have access to create topics (which used by the adapter for the internal topics). My understandig is that it is currently not possible to provide the used topics for internal commands. Is this correct? If so, might it be an idea to provide these topics somehow so the customer can manually create the topics and we do not need the permission to create them automatically? WDYT?
@b-abel That was indeed one of the discussed options, in particular for use cases where you do not expect that many commands to be sent and therefore can afford to simply ignore the commands in adapter instances that the target device is not connected to. However, IIRC we decided to start with implementing the more general approach that we now have. Maybe you can add a pointer to the original issue in #2920 ?
@sophokles73 Is https://github.com/eclipse/hono/issues/2273#issuecomment-718418108 what you have in mind?
This is not supported. Hono uses the fixed topic names and AMQP addresses that are part of its API. If you want to use different MQTT topics, you could use a Protocol Gateway. You'll find a template for an MQTT Protocol Gateway in https://github.com/eclipse/hono-extras/tree/master/protocol-gateway/mqtt-protocol-gateway-template
With MQTT you can also use a property bag that you append to the topic name as outlined here. This way, you can for example include a content-type that you can then use for message routing in your downstream application. With AMQP 1.0 it is easier as it natively supports message properties (including content-type and other standard properties).
@JulianFeinauer Hi Julian, have you seen the new Eclipse Kanto project proposal? Given your interest in ioFog in the past, I wonder if this might be of interest to you as well? Let me know if you would like to know more about it. I can then get you in touch with the project lead ...