Welcome new committer: Neeraj Mangal

The Project Management Committee (PMC) for Apache OpenWhisk has invited Neeraj to become a committer and we are pleased to announce that he has accepted. Please join me in welcoming Neeraj to his new role on the project ! Neeraj has been contributing to the Kube deployment, the CLI, and the main

Welcome new committer: Dan McWeeny

It is my pleasure to share that the OpenWhisk PPMC has elected Dan McWeeny as a Committer, based on his ongoing and valuable contributions to the project, the most recent ones being around moving to Java 11, and encrypting default params. Dan has accepted the invitation. Please join me in

Welcome new committer: Cosmin Stanciu

It is my pleasure to share that the OpenWhisk PPMC has elected Cosmin Stanciu as a Committer, based on his ongoing and valuable contributions to the project, especially around user events, monitoring and kubernetes deployment. Cosmin has accepted the invitation. Please join me in welcoming

Re: Reminder: Tech Interchange meeting tomorrow, Wed Aug 15th

Unfortunately I'm in a flight during the meeting and I won't be able to attend. RE AI Actions I agree with Rodric: the time might have been a bit short. I'm incorporating the feedback I'm receiving into the wiki page and hopefully it will be in a better shape for our next meeting. If anyone

Re: logging baby step -- worth pursuing?

"...we should be able to fully process the logs offline and in a streaming manner and get the needed activation id injected into every logline..." +1 IIRC for concurrent activations Tyson Norris and Dan McWeeney were going down this path as well. Having this natively supported by all OpenWhisk

Re: Proposal on a future architecture of OpenWhisk

Markus, I appreciate the enhancements you mentioned in the wiki, and I'm very much inline with the ideas you brought in there. "...having the ContainerManager be a cluster singleton..." I was just in process to reply with the same idea :) In addition, I was thinking we can leverage Akka

AI Actions as a first-class citizen in OpenWhisk

Once you've experienced FaaS, you don't wanna go back. This has been my experience with AI and FaaS. In particular, running AI inferences in FaaS proved to be a great match: - Each function processes one request at a time. A model usually takes 1 data input and produces 1 data output. -

Re: [RESULT][VOTE] Release Apache OpenWhisk 0.9.0-incubating rc2: main OpenWhisk module

"...Please count my vote as well (binding)..." Same for me. From: Matt Rutkowski Sent: Tuesday, July 10, 2018 4:11:23 PM To: dev@openwhisk.apache.org Subject: Re: [RESULT][VOTE] Release Apache OpenWhisk 0.9.0-incubating rc2: main OpenWhisk module Please count

Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating rc2: main OpenWhisk module

I vote +1 for Release as Apache OpenWhisk 0.9.0-incubating Checklist for reference: [X] Download links are valid. [X] Checksums and PGP signatures are valid. [X] Source code artifacts have correct names matching the current release. [X] LICENSE and NOTICE files are correct for each OpenWhisk

Re: Invoker HA on Mesos

"... Interacting with the Kubernetes API server to do a labeling operation takes around 10ms, so we couldn't do this on a truly hot path" I was gonna make a similar comment for this "data plane" part, imagining that a performance optimized LB would be interested to have this visibility in

Re: Install Api Gateway in dcos

"...Is there any place I have to define the url?..." We usually configure a DNS entry like *.gw. and have it pointing to the LB for the Public Mesos Agents. The Gateway then looks at the Host header and routes to the specific Marathon app. "...DC/OS VERSION: 1.9.4..." Are you planning to run

Re: How to share an action but not its code, nor parameters

belonging to a group, including specific permissions. Right now a package is either private, either shared with everybody. WDYT ? @Rodric<mailto:rod...@gmail.com>, feel free to add to what I missed. Thanks, dragos From: Dragos Dascalita Haut <ddas

Re: How to share an action but not its code, nor parameters

"... pursuing the fine grained rights approach. ..." I was also re-reading your email and I was thinking... it would actually be v nice to have this in openwhisk. In this way developers can fully control what they want to do with the action. Another use-case I once had was to share an action

Re: How to share an action but not its code, nor parameters

"...The obvious path with composer is to create a combinator for invoking a URL, which could treat web actions intrinsically" How would this work with Composer ? I.e a 3rd party developer wants to author a composition like: compose.sequence( "/other-namespace/pkg/action1",

How to share an action but not its code, nor parameters

I think some openwhiskers have this use-case and I'm thinking to start a thread to see what are the current options. and see if we can land a PR if we want to support this use-case. The need is to share an action with 3rd party developers, while retaining the intellectual property of the

Re: Introducing myself as an incubation mentor

A warm welcome Bertrand ! From: mcweeney Sent: Thursday, February 8, 2018 7:56:24 AM To: dev@openwhisk.apache.org Subject: Re: Introducing myself as an incubation mentor +1 and thanks for agreeing to step in and help us out. On

Securing Action Container communication

I'm starting this thread based on our conversations in Slack [1]. This is a sensitive aspect, at least 2 folds: 1. Container isolation. making sure action containers can't invoke other containers directly, nor other system components directly (db, kafka, kube api, mesos api). What are the

Re: http enablement in nginx for local development

Hi Rodric, "...without running the full test suite against both HTTP and HTTPS deployments, I for one can't say what will and will not work" I assume you're referring to the test suite for the CLI, right ? So the argument is that we can simplify the CLI tests by removing NGINX from the

Openwhisk @ MesosCon North America

oundation.org> Sent: Thursday, July 20, 2017 2:15 PM To: Dragos Dascalita Haut Subject: ANNOUNCING Program for MesosCon North America; Save $200 - Register Now! Expires in 5 Days. #MESOSCON | LOS ANGELES, CA | SEPTEMBER 13-15, 2017 [The Linux Foundation]<https://na01.safelinks.protection.ou

Re: simplifying the URLs for API calls

Rodric this is a great idea to support it as part of `/v1`. A quick comment on: * get by id /api/v2/activations/?id= Is this a search or a get, in which case we could maybe use: GET /api/v2/activations/{id} also what about providing a vanity URL to the latest activation of an

Re: Browsing the mailing lists and hostnames

I've also noticed the 2 email addresses @openwhisk.apache.org and the other one with "incubator". Are we supposed to use both, or either one is fine ? Thanks, dragos From: Carlos Santana Sent: Monday, January 9, 2017 1:20:01 PM To:

Re: Passing a context object to actions

Rodric, thanks for sharing more info. I've been thinking at it over the weekend. I'm reading in the Gist comment that the idea is to do: 1. json_data.event = data; 2. json_data.context = ... I'm wondering what do we do when "data" comes in a binary format. Binary formats could easily come

Passing a context object to actions

tity.* would be something reserved for the OpenWhisk API Gateway to populate and it could also be based on special headers like "X-GW-Identity". What I like about this approach with Headers is that no intermediary process needs to understand the body of the request; we could also suppor