From dev-return-2318-archive-asf-public=cust-asf.ponee.io@openwhisk.apache.org Thu Jul 26 19:43:37 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 5B2C1180621 for ; Thu, 26 Jul 2018 19:43:37 +0200 (CEST) Received: (qmail 76911 invoked by uid 500); 26 Jul 2018 17:43:36 -0000 Mailing-List: contact dev-help@openwhisk.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openwhisk.apache.org Delivered-To: mailing list dev@openwhisk.apache.org Received: (qmail 76899 invoked by uid 99); 26 Jul 2018 17:43:35 -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; Thu, 26 Jul 2018 17:43:35 +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 50526C0C18 for ; Thu, 26 Jul 2018 17:43:35 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.299 X-Spam-Level: * X-Spam-Status: No, score=1.299 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.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 JPCEUx1IRmID for ; Thu, 26 Jul 2018 17:43:34 +0000 (UTC) Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 2ACA45F385 for ; Thu, 26 Jul 2018 17:43:34 +0000 (UTC) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.west.internal (Postfix) with ESMTP id B17DC287 for ; Thu, 26 Jul 2018 13:43:32 -0400 (EDT) Received: from web5 ([10.202.2.215]) by compute2.internal (MEProxy); Thu, 26 Jul 2018 13:43:32 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=fR1MwG HnE/LZLCtcm1n71uuJwjk0xu5tJjPTlg9Rn9w=; b=EnJczwgpbF+lPk3ttEB09u 9ULFSnnDghQXxFyQDFNF5ULm10fcD1eGBXUtpVKfKOZ2ENEpPxei2WG6XunOub8z ZZ0UF39TF+19xxL49yjz78JAexVfKEHe8STV2H+3bs/5SU1iJYImxbUQoC8Ba6X/ tMUzi1GL+Op5lAlD6FmYEvmbTfZ5xwKW0X/l1sHM16UKrA5pGMFlyvnqjydBkipi g314wDwDGztuD7b/n9G/qFd2MLbXxNkovbHRt0Ot5uJ37jo0BfALs+RGcYqCYkxO cgq9ppO+4O5UV9kiUSoEbYdV7C1zRUGLP0KTRYHLvb/50OgGnGL1JGCPkDCqFi6w == X-ME-Proxy: X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id F41899E0F5; Thu, 26 Jul 2018 13:43:31 -0400 (EDT) Message-Id: <1532627011.3615381.1453967968.11629717@webmail.messagingengine.com> From: Michele Sciabarra To: dev@openwhisk.apache.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: multipart/alternative; boundary="_----------=_153262701136153812" X-Mailer: MessagingEngine.com Webmail Interface - ajax-0843ff3e References: <1532530582.1678689.1452516472.2F03B07F@webmail.messagingengine.com> Date: Thu, 26 Jul 2018 19:43:31 +0200 In-Reply-To: Subject: Re: MiniWhisk: what you think? --_----------=_153262701136153812 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" Share the code and let=E2=80=99s collaborate. If you remember I started the Openwhisk runtime from your code, there are still a few lines of code left :) -- Michele Sciabarra michele@sciabarra.com On Thu, Jul 26, 2018, at 7:38 PM, James Thomas wrote: > Michele, > > I'd also started a project this month called "miniwsk" around local > development - great minds! :) > > I had a similar idea about an instance of the platform that > would spin up> containers locally. My approach was to implement the OpenW= hisk > platform API> using a stub server that would execute the actions using Do= cker in > the host> system. I also wanted to use Go lang for the mock server so that > it would> be a simple binary I could start on demand. Implementing the > API means I> can just use all the normal OpenWhisk tools without modifica= tion by > pointing them to localhost. > > It's still in the super-early stages of development so I'm not > sure when> I'll have it ready for publishing... I wasn't going to handle = re- > build go> based stuff as your idea does. It was purely a stub server to i= nvoke > containers on demand. > > On 25 July 2018 at 15:56, Michele Sciabarra > wrote:> > > Hello, in the process of developing some examples for the > > goproxy, I> > realized I want a tool to make easier developing go actio= ns > > locally. While> > it is generally acceptable to deploy your actions str= aight to the > > IBM Cloud> > for example when you code in Javascript (or Python) it is = less > > desiderable> > for Go because compilation time in the cloud is not so f= ast as it > > is when> > compiled locally, and you have the additional time of upload= ing a > > binary> > that is generally bigger than javascript actions. > > > > SO I ended up with this idea of the "miniwhisk". I am posting here > > to see> > if it is acceptable or... there are better solutions. > > > > My idea of the miniwhisk is a "single action " executor. It > > should work> > more or less this way: > > > > $ miniwhisk /path/of/action -runtime openwhisk/actionloop-go- > > v1.10:master> > -watch *.go -build make -action demo > > > > This command will launch the runtime "openwhisk/actionloop-go- > > v1.10:master"> > using docker run, then will watch the files specified = with "-w". > > When a> > file changes, it will execute the build command (-build) and = then > > execute> > and "init" of the action runtime, post the action to the run= time as > > an init.> > > > Additional (and most importantly) it starts a webserver that will > > listen> > to /path/of/action for GET and POST and will then translate > > requests in> > appropriate /run posts for the runtime. > > > > Basically it is a tool to develop an action in go locally > > simulating what> > would happen when run in the real OpenWhisk. > > > > > > How does sound the idea? Is it worth the effort? > > > > > > > > > > > > > > > > -- > > Michele Sciabarra > > openwhisk@sciabarra.com > > > > > > -- > Regards, > James Thomas --_----------=_153262701136153812--