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 63E70200BEF for ; Wed, 4 Jan 2017 18:39:39 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 63901160B3A; Wed, 4 Jan 2017 17:39:39 +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 AD852160B21 for ; Wed, 4 Jan 2017 18:39:38 +0100 (CET) Received: (qmail 92823 invoked by uid 500); 4 Jan 2017 17:39:37 -0000 Mailing-List: contact user-help@karaf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@karaf.apache.org Delivered-To: mailing list user@karaf.apache.org Received: (qmail 92813 invoked by uid 99); 4 Jan 2017 17:39:37 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Jan 2017 17:39:37 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 6B2E01A0905 for ; Wed, 4 Jan 2017 17:39:37 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.479 X-Spam-Level: X-Spam-Status: No, score=0.479 tagged_above=-999 required=6.31 tests=[RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id YmEbyLi6wvjA for ; Wed, 4 Jan 2017 17:39:35 +0000 (UTC) Received: from mail-oi0-f50.google.com (mail-oi0-f50.google.com [209.85.218.50]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 083AD60E83 for ; Wed, 4 Jan 2017 17:39:35 +0000 (UTC) Received: by mail-oi0-f50.google.com with SMTP id b126so551513698oia.2 for ; Wed, 04 Jan 2017 09:39:34 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:references:in-reply-to:subject:date :message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=FT4zXjHr7okxX6+oMhjHuyJOonW9BKA2riTdqrKwQcc=; b=Ru8bq3mss6tPRAxukUv5XcuEMKAlHYKLxM5IaDg8vcPXSlIszBYczS5rLWSdGfeY3Y Rx8/rOBNkFCKZPgAiGJGbCHJSdDhphQHn4mWjOmhlXrHestLet31HD8T22nuxxZwGReX L2ZIggyjZ+AwxvHgnVaiRHdmVMmDemmpFuB77vbUlqCvLZKSQFb1jH3YHhqYqFxeRyRM Bj7ql6eA7PLyXUCl1fyFtpyFRRc7OWrxV3h8WYKx8697XKDf/PSQY1JIyeklgu59QodS bop79uSWmk0rDdTA/dUoIfo9v1gk6KTf8ayVtOnOowd3PwwY88t9a3Sx0q6XgSNlN3tc 1Reg== X-Gm-Message-State: AIkVDXITzgM2RdN68EXfwGGO6nIQAqbBX9kJNPRPJeoJuu6dfmLxZAqC4pFIpw/KjC+g+64e X-Received: by 10.157.25.139 with SMTP id k11mr38880018otk.265.1483551574175; Wed, 04 Jan 2017 09:39:34 -0800 (PST) Received: from Lightweight (cpe-173-174-112-236.austin.res.rr.com. [173.174.112.236]) by smtp.gmail.com with ESMTPSA id w48sm22302502otw.33.2017.01.04.09.39.33 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 04 Jan 2017 09:39:33 -0800 (PST) From: "Brad Red Hat" To: References: <000a01d26490$6bcbeb00$4363c100$@redhat.com> <006c01d26506$eafd8ca0$c0f8a5e0$@redhat.com> <00dc01d2652f$5ec12430$1c436c90$@redhat.com> <1fd5622b-4e94-d202-2560-1f37f13f9f87@composent.com> In-Reply-To: <1fd5622b-4e94-d202-2560-1f37f13f9f87@composent.com> Subject: RE: Karaf IoT Date: Wed, 4 Jan 2017 11:39:33 -0600 Message-ID: <03b201d266b1$82cc3030$88649090$@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQIACW+anOp4uegC0s2tYJSLMq68BAH5IawYAdvx/7wCMPnXsQOWRK6+Axt1pLgCwcwlCaBRf0sg Content-Language: en-us archived-at: Wed, 04 Jan 2017 17:39:39 -0000 I'll certainly look at that a bit more. My concerns about Kura project have as much to do with the project's level of abstraction and I can bring it up there. I did ask about their intentions with service interfaces. As I've dug into it deeper and thought about "the vision thing", to quote a US president, I laid out some of those thoughts. https://enjekt.org/2017/01/04/iot-and-the-abstraction-of-things/ Because it is an Eclipse project I wasn't sure that they'd be interested in Karaf/Felix but can check. I've heard that they have, in fact, opened a Jira ticket about it. So they may be interested. It isn't just about a Karaf implementation although it is certainly about that as well. I'm also concerned about the intermediary libraries/services that abstract developers away from low level details of pin outs in order to make application code portable. Obviously the intermediate level concerns really don't belong with Kura or Karaf so I won't discuss those here. Suffice it to say I'd like to see that intermediate set of libraries become a "sticky" place where developers and sensor/actuator manufacturers go to add new high level device specific bundles for use in applications. Brad -----Original Message----- From: Scott Lewis [mailto:slewis@composent.com] Sent: Tuesday, January 3, 2017 9:33 PM To: user@karaf.apache.org Subject: Re: Karaf IoT On 1/2/2017 11:35 AM, Brad Red Hat wrote: > I certainly understand the "short of time" problem. It just happens > that I have a bit of a window right now and would like to get into it a bit deeper. > > > Whether a Karaf/PAX/Felix implementation is more appropriate under the > aegis of Kura or as a separate project that leverages the Kura driver > bundles is hard to say. I guess that would depend on a couple of things. > > 1. How amenable they are to a more top down approach that starts with > OSGi service mechanics and drives down to meet the driver bundles? > 2. Does an Eclipse foundation project have any interest in an Karaf > branch project? The ECF project would be interested in such an effort [1]. We have been/are distributing our impl of the OSGi Remote Services/RSA specs [2] as Karaf features [3] and have recently been exploring using remote services for Karaf management [4]. Also, in my interaction with some of the Kura committers it's become clear that they are doing some prototyping of running Kura services on Karaf [5]. I don't know whether they have release plans around that work, but I know that it has been going on. It might be useful to convey to them directly what your desires/criticisms are, and perhaps contribute to that work. Scott [1] http://www.eclipse.org/ecf [2] https://wiki.eclipse.org/Eclipse_Communication_Framework_Project#OSGi_Remote _Services [3] https://wiki.eclipse.org/EIG:Install_into_Apache_Karaf [4] https://wiki.eclipse.org/Karaf_Remote_Management_with_Eclipse [5] https://dev.eclipse.org/mhonarc/lists/kura-dev/