Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 0E3BE200C48 for ; Thu, 6 Apr 2017 14:34:15 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 0CE69160B9F; Thu, 6 Apr 2017 12:34:15 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 2F0A8160B83 for ; Thu, 6 Apr 2017 14:34:14 +0200 (CEST) Received: (qmail 45711 invoked by uid 500); 6 Apr 2017 12:34:13 -0000 Mailing-List: contact dev-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list dev@camel.apache.org Received: (qmail 45700 invoked by uid 99); 6 Apr 2017 12:34:13 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Apr 2017 12:34:13 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 9E640183991 for ; Thu, 6 Apr 2017 12:34:12 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.517 X-Spam-Level: X-Spam-Status: No, score=0.517 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.796, URI_HEX=1.313] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id vwJg1YggyAuc for ; Thu, 6 Apr 2017 12:34:09 +0000 (UTC) Received: from mail-vk0-f44.google.com (mail-vk0-f44.google.com [209.85.213.44]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id E2AB15F39D for ; Thu, 6 Apr 2017 12:34:08 +0000 (UTC) Received: by mail-vk0-f44.google.com with SMTP id z204so38514024vkd.1 for ; Thu, 06 Apr 2017 05:34:08 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=eQyMYZi4MRW9y21lmrCF6pN/giJ6d8I+dv4Py572jBA=; b=N66hGLzSb5tZqbJqnyYbJV3dQpROw1aYpIVQTcD6HWb7Rxrk2BuByecBtq4VHpvwP6 x2md7xn1pyZ60+cR0DHYreC5nAAwENthqQG2lGUGik3VkCU9BplwsUBJqnvIz9NPagRX /Esmcr3R20mGkKERiRHCh4nCpIY3G5kJ0YFWltL0e/wT4QcfzSILSC+Gqeb/0AIonlxo masjd9ep6eP5jwarJe1Obm/N61LuC0PunjQ3zg1xPRPRGYp3lGIueHA3uRGKCvDON5gf 01Jjd4erI1EwXG1CHflslez6A6a1ln4MlBcvrHiX2wo2scKNB4ySJTPa2t9C5AXTh+ra ud9g== X-Gm-Message-State: AFeK/H2B9QCeprvoozqia4ujlL7b4Y57fzC69O4OWx1k47wsFthPBTiSQKdYcZgCtEJsqWMNzFd6SMJTwOiCByea X-Received: by 10.176.66.132 with SMTP id j4mr7789856uaj.103.1491482041471; Thu, 06 Apr 2017 05:34:01 -0700 (PDT) MIME-Version: 1.0 Received: by 10.103.12.197 with HTTP; Thu, 6 Apr 2017 05:34:01 -0700 (PDT) In-Reply-To: References: From: Jens Reimann Date: Thu, 6 Apr 2017 14:34:01 +0200 Message-ID: Subject: Re: Contributing a set of IoT related components To: dev@camel.apache.org Content-Type: multipart/alternative; boundary=001a114a211845687d054c7eb938 archived-at: Thu, 06 Apr 2017 12:34:15 -0000 --001a114a211845687d054c7eb938 Content-Type: text/plain; charset=UTF-8 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. On Thu, Apr 6, 2017 at 1:52 PM, Claus Ibsen 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 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 --001a114a211845687d054c7eb938--