[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [iot-wg] Integrating Eclipse IoT projects
- From: "Hudalla Kai (INST/ECS4)" <kai.hudalla@xxxxxxxxxxxx>
- Date: Tue, 15 Jan 2019 17:20:37 +0000
- Accept-language: en-US, de-DE
- Delivered-to: firstname.lastname@example.org
- Thread-index: AQHUq+FErcvctQdHcUiCNtdRReEoaaWuzPmAgAG3wgA=
- Thread-topic: [iot-wg] Integrating Eclipse IoT projects
- User-agent: Evolution 3.30.1-1build1
thanks for your detailed response :-) I have added some comments below ...
On Mon, 2019-01-14 at 14:06 +0000, Bob Claerhout wrote:
> Hi Kai,
> It's nice to see this call. We, at Aloxy, are currently moving towards a more
> secure, scalable, performant and future proof IoT backend application. We have
> a great interest in all Eclipse IoT projects, especially the ones for the
> backend since we already have device and gateway software which is really
> customized towards our application.
That's great to hear!
> We already started integrating and currently we have connected Eclipse Hono
> with Eclipse Ditto. Everything runs on OKD and enMasse is used as the messaging
> framework. We still have following challenges ahead:
> Implement a production worthy auth service for Eclipse Hono.
At Bosch we are using KeyCloak for that purpose. Since it is also used by
enMasse, it is an obvious option for that purpose.
> Implement a production worthy device registry service for Eclipse Hono.
I cannot promise anything (yet) but our friends from RedHat are also working in
this direction, so I guess there is an excellent opportunity for collaboration.
> Implement a front-end to manage:
So far we have deliberately chosen to not put any work into this because it would
be tightly coupled with the management API exposed by the device registry
implementation. Since this API is not in Hono's scope, there is no such thing yet
in Hono. However, this might be a good topic to discuss in the wider context of
> Create one place where everything is configured. Currently we have to configure
> a tenant in Eclipse Ditto as well as in Eclipse Hono (and afterwards maybe even
> in Kapua as well, although we probably won't use it if this is the case). It
> would be nice to have one configuration service/database. This would greatly
> reduce the configuration effort.
I agree that it would be great to have a common "provisioning API" shared by Hono
and Ditto. However, an implementation of this API would (again) depend on the
management API of the device registry used by Hono so there (currently) is not
much room for a "standard" implementation. This seems to be a topic that is
bothering many people, though, so it also seems to be a good topic to discuss in
the context of integration.
> We didn't have a thorough look into Eclipse Kapua yet but maybe Eclipse Kapua
> help us tackling (some of) the described challenges.
> We are happy to discuss this and test functionality if we can. We might even
> contribute depending on the occasion.
> Kind regards,
> Bob Claerhout
> Software Developer
> On 1/14/19 9:15 AM, Hudalla Kai (INST/ECS4) wrote:
> > Dear IoT Working Group members,
> > during the working group's meeting at last year's EclipseCon Europe in
> > Ludwigsburg, the Eclipse Kapua folks told us about the efforts of integrating
> > Eclipse Hono with Kapua in order to use Hono as an alternative to Kapua's
> > default
> > device integration layer. During the meeting we agreed that it would be
> > helpful
> > for users to better understand, which technologies/projects are related and
> > could
> > be used together in order to implement certain use cases.
> > As part of this endeavor, we would like to continue our work on integrating
> > Hono
> > with Kapua, but more importantly, we would also like to discover new
> > opportunities to create more value by integrating some of the (other) Eclipse
> > IoT
> > projects with each other. This is where you come into play. Have you already
> > thought about trying to use one of the other Eclipse IoT projects with the
> > project you are involved in? Can you think about a "better together" scenario
> > but
> > haven't found the time (or collaborators) to start the integration work yet?
> > Then
> > it would be great if you could share your ideas with us on the mailing list.
> > Based on your feedback and ideas, we would like to set up a face-to-face
> > "kick-
> > off" meeting for the next integration round (probably hosted by Bosch
> > Software
> > Innovations in Berlin in March).
> > Looking forward to hearing your ideas :-)
> iot-wg mailing list
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit