Anyone else who is a member of the IoT-WG please feel free to join
this mailing list. We have created this new mailing list so it can
focus on the actual collaboration for building the IoT Server
Platform proof of concept.
Ian
On 24/11/2015 4:04 PM, Henryk Konsek
wrote:
Sounds like a plan!
I'd like to join efforts related to #3. How can I
communicate with the other interested parties?
first of all, I want to apologize for not having answered your
messages during the last weeks after having urged everybody
before to engage in the discussion around the IoT Server
Platform. Sorry for that!
However, the good news is that my lack of responsiveness was
not due to a loss of interest but rather the opposite. The
first week of November I was attending EclipseCon Europe in
Ludwigsburg where we had an interesting discussion between
several companies representing the Eclipse IoT Working Group
(including Bosch and Red Hat) and some companies engaged in
the Cloud Foundry Foundation (including SAP, GE) and
leadership form both Cloud Foundry and Eclipse Foundation.
The reason for this meeting was the recent announcement of the
formation of the IoT Special Interest Group (SIG) within the
Cloud Foundry Foundation. Steffen Evers had put a lot of
effort in setting up this meeting, bringing all participants
to Ludwigsburg in order to discuss the intended scope of the
IoT SIG's work and how it relates to the IoT Working Group's
efforts. as part of the discussion I presented our high level
IoT Server Platform architecture diagram [1] and our intention
of evolving the Eclipse IoT projects into the IoT Server
Platform components that could be deployed to arbitrary
execution environments, including Cloud Foundry as well as
Docker based infrastructure.
During the discussion we agreed that this would be indeed
desirable and that the IoT SIG has no intention of building
the components that are part of the IoT Server Platform within
the Cloud Foundry Foundation but would like to support us in
doing so and using the effort to identify IoT specific
requirements for the Cloud Foundry core platform components.
One of the first such requirements identified was UDP support
in the Cloud Foundry router component so that we can deploy
leshan to Cloud Foundry's elastic runtime. All in all we
agreed that the IoT SIG and the IoT Working Group are not
competing but complementary efforts and that we would support
each other in achieving our common goals.
We also identified a first Proof-of-Concept implementation to
be demonstrated at EclipseCon NA 2016 as a common goal and
derived some work items that I would like to invite all of you
to collaborate on:
1. Wrap Eclipse Mosquitto as an MQTT Protocol Adapter and
deploy to Cloud Foundry's elastic runtime
- Interested parties so far: Benjamin Cabe (Eclipse
Foundation), Kai Hudalla (Bosch), Pat Huff (IBM)
2. Connect Eclipse Kura to MQTT Protocol Adapter (see 1)
- Interested parties so far: Benjamin Cabe (EF), Kai Hudalla
(Bosch), Pat Huff (IBM)
3. Wrap leshan as a LWM2M Protocol Adapter and deploy to Cloud
Foundry's elastic runtime
- Interested parties so far: Steve Winkler (GE), Kai Hudalla
(Bosch), Eric Clauer (SAP) and Urs Gleim (Siemens)
@Henryk: I think this would be of particular interest to you
as well since you are already working on this as part of RHIOT
4. Create a first prototypical implementation of the 'IoT
Connector' component using RabbitMQ in Cloud Foundry as
underlying message broker
- Interested parties so far: Kai Hudalla (Bosch), Eric Clauer
(SAP), Steve Winkler (GE); David Ingham (Red Hat) interested
in implementation using alternative messaging platform
Benjamin and I have already started to do some experimental
work wrapping Mosquitto into a "droplet" that can be deployed
to "lattice" [2].
Red Hat and Bosch are also working on an Eclipse project
proposal for the IoT Connector which we would also like to put
to a review here in the IoT Working Group's Wiki so that
interested parties can easily get involved.
For the action items above Cloud Foundry has been defined as
the initial execution environment only because of its
relevance for the participating companies. However, this does
not mean that any of the work should be limited or exclusively
targeted at Cloud Foundry only. Quite to the opposite, I want
to make sure that we also can deploy to Docker based
infrastructure as well while always keeping support for
"vanilla" deployment in other execution environments like a
servlet container or OSGi container. That said, I do not think
that we should spend too much time for now discussing a common
approach to dependency injection to be followed by each of the
IoT Server Platform's components but instead focus on
interoperability and support for configuration using the means
provided by the execution environment at hand. My personal
feeling is that (at least in cloud environments) configuration
is done more and more using simple environment variables being
passed into the process representing the application/service
...
In any case, from my point of view our meeting in Ludwigsburg
was very successful and I am looking forward to collaborate on
the IoT Server Platform with all of you. So if you are
interested in any of the items above, your support and
engagement is more than welcome :-)
