Could it be an idea to start with the "milo" component. And push the other two (of mine) two to 2.20.
I personally think that Milo is the most beneficial one anyway. On Fri, Apr 7, 2017 at 9:39 AM, Claus Ibsen <claus.ib...@gmail.com> wrote: > On Thu, Apr 6, 2017 at 2:34 PM, Jens Reimann <jreim...@redhat.com> wrote: > > I personally don't know this protocol. So I can't say much about it. > > > > But I guess adding a bunch of IoT related Camel components in one release > > would make sense. > > > > We are closing down on Camel 2.19 and intend to cut the RC in week 16 > so there is very little time if we need to get something in this > release. However the next 2.20 is scheduled for Q3 2017 so there would > be plenty of time. > > It also gives more time for people in the community and other Camel > committers / PMC to share their thoughts on having IoT components here > at Apache Camel. > > > > On Thu, Apr 6, 2017 at 1:52 PM, Claus Ibsen <claus.ib...@gmail.com> > wrote: > > > >> Hi > >> > >> Welcome to the Apache Camel community. > >> Thanks for taking the time to explain this for us on the @dev mailing > list. > >> > >> If you guys can help support and maintain these IoT specific > >> components that would be really good. > >> AFAIR we only have Henryk Konsek as a Camel committer whom has been > >> playing and doing IoT stuff. > >> > >> There is another user whom created an IoT component that wanted to > >> donate it here as well. I wonder if you guys could take a quick peak > >> at this component and see if this is something that makes sense to > >> bring in together with your components so we have more IoT stuff and > >> more people to help with the source and Camel end users whom are using > >> it? > >> http://camel.465427.n5.nabble.com/Migrate-camel-pubnub- > >> component-tp5796056.html > >> > >> > >> > >> > >> On Thu, Apr 6, 2017 at 11:33 AM, Jens Reimann <jreim...@redhat.com> > wrote: > >> > Hi everyone, > >> > > >> > As just mentioned on IRC, I would like to contribute a bunch of IoT > >> related > >> > Camel components I made to Apache Camel. Those are independent of each > >> > other, so please consider them separately. > >> > > >> > ---- > >> > > >> > ## Milo > >> > > >> > Eclipse Milo is an OPC UA protocol implementation. This component > >> provides > >> > a client and server integration of Milo for Camel. [1] > >> > > >> > OPC UA is a protocol for industrial IoT [2] > >> > > >> > ## IEC 60870 > >> > > >> > This component wraps the Eclipse NeoSCADA IEC 60870-5-104 protocol > >> > implementation into a Camel component. It provides client and server > [3]. > >> > IEC 60870 is an industrial IoT protocol mainly used in the energy > sector. > >> > > >> > ## OpenTSDB Collector > >> > > >> > A Camel component for collecting telemetry data in OpenTSDB [5]. > OpenTSDB > >> > is a time series database used to store large amount of telemetry data > >> [6]. > >> > > >> > ## Why at Apache Camel? > >> > > >> > NeoSCADA and Milo are both Eclipse projects under the IoT top level > >> > project. That would mean splitting up those Camel components under two > >> > different projects. When Camel updates both projects would need to be > >> > updated. > >> > > >> > On the other hand Apache Camel seems to me like the integration point, > >> > Camel would consume Milo and NeoSCADA protocol implementations and > >> provide > >> > the Camel components for them. But at a single location. > >> > > >> > --- > >> > > >> > So what do you think? > >> > > >> > Thanks > >> > > >> > Jens > >> > > >> > --- > >> > > >> > [1] https://github.com/ctron/de.dentrassi.camel.milo > >> > [2] https://en.wikipedia.org/wiki/OPC_Unified_Architecture > >> > [3] https://github.com/ctron/de.dentrassi.camel.iec60870 > >> > [4] https://en.wikipedia.org/wiki/IEC_60870#IEC_60870-5 > >> > [5] > >> > https://github.com/ctron/de.dentrassi.iot/tree/master/de. > >> dentrassi.iot.opentsdb.collector.camel > >> > [6] http://opentsdb.net/ > >> > > >> > > >> > -- > >> > Jens Reimann > >> > Senior Software Engineer / EMEA ENG Middleware > >> > Werner-von-Siemens-Ring 14 > >> > 85630 Grasbrunn > >> > Germany > >> > phone: +49 89 2050 71286 > >> > ____________________________________________________________ > >> _________________ > >> > > >> > Red Hat GmbH, www.de.redhat.com, > >> > Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, > >> HRB > >> > 153243, > >> > Managing Directors: Paul Argiry, Charles Cachera, Michael Cunningham, > >> > Michael O'Neill > >> > >> > >> > >> -- > >> Claus Ibsen > >> ----------------- > >> http://davsclaus.com @davsclaus > >> Camel in Action 2: https://www.manning.com/ibsen2 > >> > > > > > > > > -- > > Jens Reimann > > Senior Software Engineer / EMEA ENG Middleware > > Werner-von-Siemens-Ring 14 > > 85630 Grasbrunn > > Germany > > phone: +49 89 2050 71286 > > ____________________________________________________________ > _________________ > > > > Red Hat GmbH, www.de.redhat.com, > > Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, > HRB > > 153243, > > Managing Directors: Paul Argiry, Charles Cachera, Michael Cunningham, > > Michael O'Neill > > > > -- > Claus Ibsen > ----------------- > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 > -- Jens Reimann Senior Software Engineer / EMEA ENG Middleware Werner-von-Siemens-Ring 14 85630 Grasbrunn Germany phone: +49 89 2050 71286 _____________________________________________________________________________ Red Hat GmbH, www.de.redhat.com, Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Paul Argiry, Charles Cachera, Michael Cunningham, Michael O'Neill
