Encode special characters in credentials for the alarm package.

2020-02-25 Thread Dominic Kim
Hi folks.

There is one PR[1] open to encode special characters in credentials.
We have tested it with CouchDB but not with Cloudant.

Please give any concerns or feedback if you have.
Otherwise, I will merge the PR in 48 hours with silent assent.

[1]: https://github.com/apache/openwhisk-package-alarms/pull/155

Thanks
Dominic


Move the ack implementations to the common package

2020-02-25 Thread 김건희
Hi Whiskers.

I've submitted a PR [1] to move the ack implementations to the common
package.

The ack logic that responds to kafka messages to the controller can be used
by other components in the downstream.
However, because it's currently included in InvokerReactive, it's not
available to other components, so I moved that logic to the common package.

[1] https://github.com/apache/openwhisk/pull/4837

Any feedback is welcome.

Thanks!
KoenHee


Re: Welcome new committer: Dan McWeeny

2020-02-25 Thread Devarajan Ramakrishnan
Congratulations Dan!!!

Regards,
Ramki.


From: Dragos Dascalita Haut 
Sent: Wednesday, February 26, 2020 1:02 AM
To: dev@openwhisk.apache.org 
Subject: 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 welcoming Dan to his new role on the project !

Being a committer enables easier contribution to the project
since there is no need to go via the patch submission process.
This should enable better productivity.
Being a PMC member enables assistance with the management
and to guide the direction of the project.


dragos



Re: Welcome new committer: Dan McWeeny

2020-02-25 Thread Chetan Mehrotra
Congratulations and Welcome Dan!!
Chetan Mehrotra

On Wed, Feb 26, 2020 at 1:03 AM Dragos Dascalita Haut
 wrote:
>
> 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 welcoming Dan to his new role on the project !
>
> Being a committer enables easier contribution to the project
> since there is no need to go via the patch submission process.
> This should enable better productivity.
> Being a PMC member enables assistance with the management
> and to guide the direction of the project.
>
>
> dragos
>


Re: Welcome new committer: Dan McWeeny

2020-02-25 Thread Bill Zong
Congratulations Dan!

Re: Welcome new committer: Dan McWeeny

2020-02-25 Thread Neeraj Mangal
Congratulations Dan!! 


> On 26-Feb-2020, at 1:03 AM, Dragos Dascalita Haut  
> wrote:
> 
> 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 welcoming Dan to his new role on the project !
> 
> Being a committer enables easier contribution to the project
> since there is no need to go via the patch submission process.
> This should enable better productivity.
> Being a PMC member enables assistance with the management
> and to guide the direction of the project.
> 
> 
> dragos
> 


wskdebug: npm module name?

2020-02-25 Thread Alexander Klimetschek
Hi everyone,

the newly contributed wskdebug [1] project needs a new npm module name.

Currently it is available under the npm name `@adobe/wskdebug` [2] so users 
install the cli tool using:

npm install -g @adobe/wskdebug

Obviously with the move to openwhisk this cannot be used/updated anymore.

What should be the new name? Some candidates:

  1.  wskdebug
  2.  openwhisk-wskdebug
  3.  @openwhisk/wskdebug
  4.  @apache/wskdebug

Note that @scopes in npm require accounts, so 3 and 4 are probably a bit more 
complicated to setup. Both do not exist yet afaics.

Existing npm modules from openwhisk are:

  *   openwhisk
  *   openwhisk-composer

Personally I would prefer the one that is most simple for users to type, which 
is 1.

[1] https://github.com/apache/openwhisk-wskdebug
[2] https://www.npmjs.com/package/@adobe/wskdebug


Cheers,
Alex


Re: Welcome new committer: Dan McWeeny

2020-02-25 Thread Cosmin Stanciu
Woohoo! Congrats Dan!

On 2/25/20, 12:44 PM, "Tyson Norris"  wrote:

Woohoo! Welcome Dan!

On 2/25/20, 11:33 AM, "Dragos Dascalita Haut"  
wrote:

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 welcoming Dan to his new role on the project !

Being a committer enables easier contribution to the project
since there is no need to go via the patch submission process.
This should enable better productivity.
Being a PMC member enables assistance with the management
and to guide the direction of the project.


dragos







Re: Welcome new committer: Dan McWeeny

2020-02-25 Thread Mihai Corlan
Double the woohooo! Congrats Dan!

 
=Mihai

On 2/25/20, 12:44, "Tyson Norris"  wrote:

Woohoo! Welcome Dan!

On 2/25/20, 11:33 AM, "Dragos Dascalita Haut"  
wrote:

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 welcoming Dan to his new role on the project !

Being a committer enables easier contribution to the project
since there is no need to go via the patch submission process.
This should enable better productivity.
Being a PMC member enables assistance with the management
and to guide the direction of the project.


dragos







Re: Welcome new committer: Dan McWeeny

2020-02-25 Thread Tyson Norris
Woohoo! Welcome Dan!

On 2/25/20, 11:33 AM, "Dragos Dascalita Haut"  
wrote:

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 welcoming Dan to his new role on the project !

Being a committer enables easier contribution to the project
since there is no need to go via the patch submission process.
This should enable better productivity.
Being a PMC member enables assistance with the management
and to guide the direction of the project.


dragos





Re: Welcome new committer: Dan McWeeny

2020-02-25 Thread Matt Rutkowski
Welcome Dan!  

Very grateful for all your contributions and glad to have your experience which 
will help guide us as we take OW to the next level.

-mr


Re: Welcome new committer: Dan McWeeny

2020-02-25 Thread Rodric Rabbah
Congrats Dan!

On Tue, Feb 25, 2020 at 2:33 PM Dragos Dascalita Haut
 wrote:

> 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 welcoming Dan to his new role on the project !
>
> Being a committer enables easier contribution to the project
> since there is no need to go via the patch submission process.
> This should enable better productivity.
> Being a PMC member enables assistance with the management
> and to guide the direction of the project.
>
>
> dragos
>
>


Welcome new committer: Dan McWeeny

2020-02-25 Thread Dragos Dascalita Haut
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 welcoming Dan to his new role on the project !

Being a committer enables easier contribution to the project
since there is no need to go via the patch submission process.
This should enable better productivity.
Being a PMC member enables assistance with the management
and to guide the direction of the project.


dragos



Tech interchange 2/19 notes

2020-02-25 Thread Rodric Rabbah
hi,

I have posted the last tech interchange slides and meeting notes to the
wiki.
We could not record the presentation as it seems only Matt can do this and
alternate recording was proving difficult that day despite attempts by
others on the call.

I wrote down the minutes that I can remember from memory. There were 9
people on the call, but I could not recall everyone. If you were on the
call please edit the page to add your name and any worthwhile notes that I
left out.

https://cwiki.apache.org/confluence/x/JQ7cC

Thanks to Justin for volunteering to host the next call on March 4.

-r


[slack-digest] [2020-02-24] #general

2020-02-25 Thread OpenWhisk Team Slack
2020-02-24 08:55:22 UTC - Alvaro Lopez: Hi all, I have made a quick issue 
search about hardcoded action limits (similar to this one, only for memory: 
) to no avail. Are there any 
plans to support the configuration of other actions' limits? (e.g. parameter 
size or result size). Is there any reason to have it hardcoded to 1M?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1582534522004500?thread_ts=1582534522.004500=C3TPCAQG1

2020-02-24 12:27:43 UTC - Rodric Rabbah: 

https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1582547263006000?thread_ts=1582534522.004500=C3TPCAQG1

2020-02-24 12:30:40 UTC - Rodric Rabbah: the parameter and annotation limit for 
what’s attached on an action is hardcoded at 1MB.

so while at invocation time you can pass a large payload to an action, 
statically you can attach up to 1MB. (for example i think ibm cloud lets you do 
5MB at invoke time.)

if you’d like to factor this out into a deployment config, we welcome 
contributions
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1582547440006200?thread_ts=1582534522.004500=C3TPCAQG1

2020-02-24 13:15:02 UTC - Justin Halsall: You can clean up the last one by 
running `make destroy` and then restarting everything with docker compose by 
running `make quick-start` (you can find more docs here: 
)
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1582550102006600?thread_ts=1582454319.002800=C3TPCAQG1

2020-02-24 13:30:41 UTC - Markus Thömmes: @Martin Henke @chetanm do you mind 
having a "relook" at ? Stuff 
seems to finally work :smile:
heavy_check_mark : chetanm
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1582551041007300

2020-02-24 16:41:17 UTC - Tom Barber: So abstract question here
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1582562477007800

2020-02-24 16:41:34 UTC - Tom Barber: There's about a 4 second spin up time for 
an action
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1582562494008200

2020-02-24 16:41:41 UTC - Tom Barber: who has any tips on how to bring that 
down?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1582562501008500

2020-02-24 16:44:34 UTC - Tom Barber: thats on a cold start
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1582562674008900

2020-02-24 16:44:46 UTC - Tom Barber: on a warm start there is basically no 
overhead
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1582562686009300

2020-02-24 16:46:18 UTC - Tom Barber: 
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1582562778009600

2020-02-24 16:46:25 UTC - Tom Barber: I don't see how it figures out if its 
going to be cold or warm
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1582562785010100

2020-02-24 16:46:29 UTC - Tom Barber: it seems like its pot luck
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1582562789010300

2020-02-24 16:57:51 UTC - Tom Barber: yeah I can't figure it out, I've got 
loads of prewarmed python containers, but if I run an action whether it hits a 
warm one or not seems entirely random
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1582563471011100

2020-02-24 17:00:15 UTC - Rodric Rabbah: some thoughts, Tom.
1. you might want to grab the latest python runtime updates if not already 
using those - they make the python runtime generally faster
2. you can add stem cells for the runtime you use often to create containers 
ahead of time in the container pool
3. how big is the action (is this a zip file)? consider augmenting the runtime 
with required libraries so the zip unpacking time is shorter
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1582563615012900

2020-02-24 17:02:11 UTC - Tom Barber: so on #2 stem cells are all these 
prewarmed containers, right?
white_check_mark : Rodric Rabbah
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1582563731013400

2020-02-24 17:02:26 UTC - Tom Barber: cause I've got like 50 of them 
:slightly_smiling_face:
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1582563746013700

2020-02-24 17:02:44 UTC - Tom Barber: and no load on the system, which is why 
i'm surprised its not reusing warm ones
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1582563764014100

2020-02-24 17:04:04 UTC - Rodric Rabbah: cold start doesn’t mean not using a 
prewarmed container, it means the container had to be initialized with the 
user’s code
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1582563844014900

2020-02-24 17:04:59 UTC - Rodric Rabbah: not sure why you wouldn’t get reuse 
:confused:
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1582563899015800

2020-02-24 17:05:21 UTC - Rodric Rabbah: 

[slack-digest] [2020-02-24] #random

2020-02-25 Thread OpenWhisk Team Slack
2020-02-24 09:25:57 UTC - mmarth: Fyi wasm  openwhisk 

https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1582536357000500

2020-02-24 12:34:04 UTC - Rodric Rabbah: thanks for sharing this link - do you 
know the author (or his group?)
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1582547644001100?thread_ts=1582547644.001100=C3UDXSFA6

2020-02-24 13:35:39 UTC - mmarth: yes, we have been in touch on some OW 
projects (but not this particular one)
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1582551339001200?thread_ts=1582547644.001100=C3UDXSFA6