2019-05-19 16:28:13 UTC - Michele Sciabarra: actually it is already there
https://openwhisk-team.slack.com/archives/C9HCXAKJ4/p1558283293004300?thread_ts=1558112407.001400&cid=C9HCXAKJ4
2019-05-19 16:31:25 UTC - Michele Sciabarra: the code but I realized it is not
published openwhisk/actionlo
Michele,
I like the idea to make the ActionLoop based runtimes to be runnable on Knative.
My thoughts on this:
- I second Markus concern to implement the invocation API onto Knative instead
of just using Knative service syntax.
- I would have concerns to make it dependent on Gloo which is kind o
On Mon, May 20, 2019 at 2:07 PM Martin Henke wrote:
> ...As Knative Build seems be on a dead end...
Wow, already? That stuff seems to be competing with JavaScript
frameworks in terms of short lifetimes these days ;-)
-Bertrand
Bertrand,
I am not directly involved in Knative Build or Tekton so I might be wrong on my
dead end sentence.
For what I got ,I think It was realised that a build pipeline on Kube and the
task to build docker containers from a given source
is a general problem to solve and in most ways independe
>Michele,
>I like the idea to make the ActionLoop based runtimes to be runnable on
>Knative.
>
>My thoughts on this:
>- I second Markus concern to implement the invocation API onto Knative instead
>of just using Knative service syntax.
Can you elaborate this? I do not understand.
>- I would hav
I strongly echo Chetan's statements and also put my own words below.
[CS50] *All "important" discussions happen asynchronously in written form
on ..."
1. All significant project communication for the project has and is
happening asynchronously and in writing: on GitHub with attention solicited
fr
Yes but... Knative is supposed to define some "standards" for bulding, serving
and eventing.
Also I do not look after any "decent" UI, building in OpenWhisk is (and must
be) a hidden detail.
You send the sources and run the image. ActionLoop images are already able to
precompile. The difference
> On 20. May 2019, at 14:55, Michele Sciabarra wrote:
>
>> Michele,
>
>> I like the idea to make the ActionLoop based runtimes to be runnable on
>> Knative.
>>
>> My thoughts on this:
>> - I second Markus concern to implement the invocation API onto Knative
>> instead of just using Knative
Good discussion, thanks!
Can we try to define what the desired end-goal is here? I'm a bit unclear
what resembling the OpenWhisk API actually buys us.
To me, the desired end-state would be to run OpenWhisk actions as-is on a
Knative cluster (similar to OpenFaaS' and Azure's integration). There's
Ok great, I see the discussion is starting to bring ideas.
Yes my goal is basically to run existing actions in Knative, create and invoke.
And possibile retain the ability of an action to invoke another action.
I understand the different way they expose services, so I am rethinking the
idea of
Tekton is different but very very similar. You get a lot of DejaVus. No big
learning Curve.
Martin
> On 20. May 2019, at 17:00, Michele Sciabarra wrote:
>
> Ok great, I see the discussion is starting to bring ideas.
>
> Yes my goal is basically to run existing actions in Knative, create and
For background:
Tekton has emerged out of the former Knative Build-Pipelines project. The
Build API connection will be dropped in Serving v1beta1. Tekton is the way
to go if any.
Cheers,
Markus
Am Mo., 20. Mai 2019 um 17:03 Uhr schrieb Martin Henke :
> Tekton is different but very very similar.
>>> - I second Markus concern to implement the invocation API onto Knative
>>> instead of just using Knative service syntax.
>> Can you elaborate this? I do not understand.
>Knative service syntax:https://action)>../
>OW invocation https:///api/v1/namespaces//actions/
>(I personally so no wor
Thanks for the clarification Betrand. I'd actually thought I'd opened a
DISCUSS already (but obviously not...). I did want to do this, will send it
out now.
On Sat, 18 May 2019 at 09:13, Bertrand Delacretaz
wrote:
> Hi,
>
> On Fri, May 17, 2019 at 6:42 PM Carlos Santana
> wrote:
> > ...I didn’t
Further to the previous email thread, does anyone have anything they want
to add about a potential release for the Apache OpenWhisk Runtime Node.js?
The main feature I want to get out in this release is Node.js v12 support.
I'll wait a few days before re-opening the VOTE thread.
https://github.co
Hi,
This is a call to vote on releasing version 0.10.0-incubating release
candidate rc1 of the following project module with artifacts built from the
Git repositories and commit IDs listed below.
* OpenWhisk API Gateway: 1f46de9
https://github.com/apache/incubator-openwhisk-apigateway/commits
[x] +1 Approve the release
[x] Download links are valid.
[x] Checksums and PGP signatures are valid.
[x] DISCLAIMER is included.
[x] Source code artifacts have correct names matching the current release.
[x] LICENSE and NOTICE files are correct for each OpenWhisk repository.
[x] All
Thanks for bringing up Tekton; I was going to suggest taking a look at
it since knative was brought up. I'd definitely recommend that over
knative-build as it's getting a lot more attention from external
contributors from other related projects like Jenkins X, GCP, etc.
On Mon, 20 May 2019 at 10:1
18 matches
Mail list logo
