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 F3194200C7F for ; Wed, 24 May 2017 17:22:36 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id F1D5E160BB4; Wed, 24 May 2017 15:22:36 +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 1BDBB160B9C for ; Wed, 24 May 2017 17:22:35 +0200 (CEST) Received: (qmail 75782 invoked by uid 500); 24 May 2017 15:22:35 -0000 Mailing-List: contact dev-help@edgent.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@edgent.apache.org Delivered-To: mailing list dev@edgent.apache.org Received: (qmail 75763 invoked by uid 99); 24 May 2017 15:22:33 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 May 2017 15:22:33 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 58BF8C0CA1 for ; Wed, 24 May 2017 15:22:33 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.879 X-Spam-Level: * X-Spam-Status: No, score=1.879 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id hY1N-MwKkZlF for ; Wed, 24 May 2017 15:22:32 +0000 (UTC) Received: from mail-wm0-f43.google.com (mail-wm0-f43.google.com [74.125.82.43]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id D3B815F249 for ; Wed, 24 May 2017 15:22:31 +0000 (UTC) Received: by mail-wm0-f43.google.com with SMTP id e127so78445706wmg.1 for ; Wed, 24 May 2017 08:22:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=jrf7d7Fa1JEd3mmdIQMLWDHPSqdieRkPDjIzcGyj3D4=; b=Fs1gPbhyb3Ym8pkkUGhIZAwa09c0OEdk28Y2mfL6fqWffS4CvpJOAruWXFxKEYWbQd jUOXD8fFO3TZEgtyPeWtyXBzun1Ymc1bEwv4C53SvcqY7Y33MaBRSpW+JjwxENc21TwB VQrRxevTeVfwBsi1yxn+DxTw0rA6H3xWrmN5kZNneWvqGk1Z9jDhlzoA2gZ3+Pl3UO9h JZL3G0rcBU0p5qHfOSS0oYpfBNTFYuDCdHwHQbbtd5q9n06/F5iSgNhfhcYG1JnmJD5h VxqLMODzeS7f5fnpGpe14MBZ0IIfRBF/OpGQBNMWSlOply5/Fz401h8/kAzX4lqvF9AD cg6Q== 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=jrf7d7Fa1JEd3mmdIQMLWDHPSqdieRkPDjIzcGyj3D4=; b=lFsvPkZzZv4DoEgcdy8FchJRqxkejiQYyJLI4W62KUvejQOGaQMhyz+dw1LUoXnfF8 aCO9shIBsuo9+g+W3xcgJgMhrxq+da1NAXXn1FKqaMmJlTHlPuhjD5ove5nJYpsxcv68 vtkTnIDbfSFS1c2KbqxrVPbqBdujoPW6qDY+SNp/dlQ227qOBReeL5Kea+2nu15F0m41 c5o1ptTDYkk99dC0oEKgg3/93Aqk8qRgLpw0cfSTEx34G2GheniOWJOXC3Z96MXW/8+b HaDhViFn+RCw7UD8W6uzCE7aiWSXD4yv2BFFD+HEC4JReaM/gggSYdje+6UH9/bqEdZP 4/gA== X-Gm-Message-State: AODbwcBvyXDByxLD1swey5Xi4jmmy7W17vLiX6Zu5AiSaiX9d4b9EYXL xm1je4YOD810GFrUKYOLSSLiwtCYM5Gv X-Received: by 10.80.212.211 with SMTP id e19mr25124231edj.164.1495639350626; Wed, 24 May 2017 08:22:30 -0700 (PDT) MIME-Version: 1.0 Received: by 10.80.152.196 with HTTP; Wed, 24 May 2017 08:22:30 -0700 (PDT) In-Reply-To: <2BF69EC4-F1F4-48D4-B168-7C7A84EE5851@apache.org> References: <2BF69EC4-F1F4-48D4-B168-7C7A84EE5851@apache.org> From: William Marshall Date: Wed, 24 May 2017 08:22:30 -0700 Message-ID: Subject: Re: ApacheCon and Edgent To: dev@edgent.apache.org Content-Type: multipart/alternative; boundary="94eb2c1af9f834d046055046ac73" archived-at: Wed, 24 May 2017 15:22:37 -0000 --94eb2c1af9f834d046055046ac73 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Dale, thanks for the summary. Just thought I'd add a few more points of interest during the event: - I spoke with Sally Khudairi, the head of marketing at Apache. She said a good way to raise awareness about Edgent is to create a blog under blogs.apache.org and to start posting articles about Edgent. We can do this by requesting infra for both the subdomain domain and access. Her advice, in addition to John's, was that we should have examples of integrating into other Apache projects; examples of Spark, Apex, and Flink would be good starting points. - One question after the 50 minute Edgent talk was about whether Edgent had any lifecycle support, as in, if there's a way to update a currently running Edgent app to a newer version. - I went to a talk by Carlos Santana about OpenWhisk. He mentioned they're thinking about adding integration with NodeRed to execute topologies through OpenWhisk (still unclear as to exactly what that means), so I asked whether such integration with Edgent were possible, and he seemed open to the idea. Carlos is an OpenWhisk committer and IBMer. - During one of the introductory Keynotes, Edgent was mentioned as one of the contributed IBM projects. - To expand on what Dale said, we had a talk with two MyNewt contributors, one is Aditi Hilbert (a committer), and the other is James Pace (ceo of runtime). They expressed an interest in some form of Edgent integration. MyNewt is a real time OS which can run on natively on small microprocessors, but it can also run as a VM in a gateway, so there's some opportunity to have Edgent communicate with MyNewt in a gateway. Smaller points of interest: - Jim Jagilski, one of the Shark Tank judges, said he wouldn't be surprised if we had a "floodgates opening" kind of moment. The project should have more attention that it does given its position in the IoT space. Pretty encouraging! For me, the takeaway with respect to outreach was that we should be writing articles on the Apache blog about how we can integrate with different Apache projects. -Will On Tue, May 23, 2017 at 9:29 AM, Dale LaBossiere wrote= : > Hi all, > > Will and I attended ApacheCon 2017 and gave a talk =E2=80=9CVideo Analyti= cs at the > Edge: Fun with Apache Edgent, OpenCV and a Raspberry Pi=E2=80=9D. > > Here=E2=80=99s my take on the conference wrt Edgent: > > Overall, I think it was very good for raising awareness of / interest in > Edgent. > - we had our talk right after lunch on the first day. > The room was pretty full - ~50 people? seemed to go well. > The next day an attendee approached me at breakfast and said he found > the talk > to be the most interesting to him so far. > - Will, a brave guy, did an Edgent presentation in the =E2=80=9CApache Sh= ark Tank=E2=80=9D > session > - Will also did a 5min =E2=80=9CLightening Talk=E2=80=9D plug for Edgent > - We noticed a few folks with the Edgent website open on their laptops > - Edgent was now getting mentioned in some other talks later in week > - Building a SCADA system > - Verbal mention in Transportation IoT stack talk > - I plugged it the =E2=80=9CIgnite & Spark=E2=80=9D talk > - While mentioned in the =E2=80=9CApache and RPi=E2=80=9D talk=E2=80= =99s abstract, the author > hadn=E2=80=99t yet played with it > - Will had a chat with some OpenWisk folks re being able integrate an > Edgent app with openwork > - We had a chat with Mynewt folks. There seems to be an integration > opportunity - e.g., Edgent app running on an IoT gateway ingesting events > from connected Mynewt-based sensors. > - We had a discussion with John Ament regarding the project as a whole. > More to come there. > > That said, most of the ApacheIoT talks showing (Apache) IoT stacks showed > devices ~directly connected to the data center, ingesting =E2=80=9Craw=E2= =80=9D sensor > reading values into Kafka, and such and going up the stack from there. T= he > talks were mostly at the =E2=80=9Cdata center=E2=80=9D components level, = sometimes focusing > on ingest volume/speed. Don=E2=80=99t think I heard / saw anyone mention > explicitly concentrating devices into an IoT Gateway. > > There were some lower level IoT talks on Mynewt (RTOS and environment for > micro controller sized devices), Juston=E2=80=99s OpenSource HW talk, Jus= tin=E2=80=99s > =E2=80=9CBecome a [device level] IoT Developer=E2=80=9D talk. > > A couple of interesting slides/comments in a (VC) Keynote speaker=E2=80= =99s IoT > presentation: > Macro trends > Exponential growth in devices > Exploding data volume > Smarter =E2=80=9Cthings=E2=80=9D, lower cost > Realtime Machine-2-Machine, no human in the loop > Hence > Realtime, Streaming > Event Driven > Running on the Edge > Summary > Early days in a large mkt > Real use cases are (finally) emerging > Tech stack is mature > Investors are cautiously optimistic > > =E2=80=94 Dale --94eb2c1af9f834d046055046ac73--