[slack-digest] [2019-02-19] #random

[OpenWhisk Team Slack]

2019-02-19 12:39:37 UTC - Carlos Santana: 

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

[slack-digest] [2019-02-19] #general

[OpenWhisk Team Slack]

2019-02-19 00:30:16 UTC - Vikash: It didn't work. I am getting a new error.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550536216128700?thread_ts=1550426649.113700=C3TPCAQG1

2019-02-19 00:30:30 UTC - Vikash: 
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550536230128900?thread_ts=1550426649.113700=C3TPCAQG1

2019-02-19 00:31:42 UTC - Rodric Rabbah: Do a gradlew clean 
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550536302129500?thread_ts=1550536302.129500=C3TPCAQG1

2019-02-19 00:34:13 UTC - Rodric Rabbah: Can you run make init-whisk-cli again 
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550536453130200?thread_ts=1550426649.113700=C3TPCAQG1

2019-02-19 00:44:02 UTC - Carlos Santana: WTF?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550537042130600?thread_ts=1550536302.129500=C3TPCAQG1

2019-02-19 03:48:00 UTC - Carlos Santana: thanks that did the trick
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550548080130800?thread_ts=1550536302.129500=C3TPCAQG1

2019-02-19 08:23:58 UTC - Matthias Riml: i get the same init-api-management 
error. I can create an action and invoke it, but it runs on the "whisk.system" 
namespace and not on the guest namespace. Not working like normal
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550564638133000?thread_ts=1550235707.082100=C3TPCAQG1

2019-02-19 08:24:41 UTC - Matthias Riml: 
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550564681133400?thread_ts=1550235707.082100=C3TPCAQG1

2019-02-19 08:28:39 UTC - Matthias Riml: after i run the make init-whisk-cli 
manually, it created the namespace guest. So now it seems to work
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550564919133800?thread_ts=1550235707.082100=C3TPCAQG1

2019-02-19 09:42:35 UTC - Lars Andersson: I'm working on a PR to extend the 
output of the wsk activation list command, and want to hear your opinions about 
the following proposal:
```
$ wsk activation list --limit 10
DatetimeActivation IDKind 
Duration   Status  Entity   
   
2019-02-18 11:56:36 bb55eb213bf04b4b95eb213bf05b4bce ruby:2.5 689ms 
 0   guest/unicodeGalore.ruby2.5:0.0.1  
 
2019-02-18 11:56:35 d630388f422e4f29b0388f422e9f29d7 python:3 210ms 
 0   guest/unicodeGalore.python3:0.0.1  
 
2019-02-18 11:56:33 be745b49c8644804b45b49c864a804ef python:2 155ms 
 0   guest/unicodeGalore.python2:0.0.1  
 
2019-02-18 11:56:31 1ca0af76bab34834a0af76bab35834e0 python   159ms 
 0   guest/unicodeGalore.python:0.0.1   
 
2019-02-18 11:56:30 3435018b521c473cb5018b521ce73c10 php:7.3  54ms  
 0   guest/unicodeGalore.php7.3:0.0.1   
 
2019-02-18 11:56:29 0bdc09898238452b9c09898238352b56 nodejs:10120ms 
 0   guest/unicodeGalore.nodejs10:0.0.1 
 
2019-02-18 11:56:28 ec44f4c40d944cfc84f4c40d94bcfc8e nodejs:8 120ms 
 0   guest/unicodeGalore.nodejs8:0.0.1  
 
2019-02-18 11:56:26 1a476ba4db844791876ba4db84779118 nodejs:6 43ms  
 0   guest/unicodeGalore.nodejs6:0.0.1  
 
2019-02-18 11:56:26 ae47e1baea7b461787e1baea7be61753 java 172ms 
 0   guest/unicodeGalore.java:0.0.1 
 
2019-02-18 11:56:25 ac7068949d574ed3b068949d576ed339 go:1.11  276ms 
 0   guest/unicodeGalore.go1.11:0.0.1  
```

- Are there any more attributes you would like to see? Also available are 
*annotations* and *cause*.
- Are the order of attributes acceptable?
- Is it acceptable to use the ISO date-time format shown?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550569355136300?thread_ts=1550569355.136300=C3TPCAQG1

2019-02-19 11:56:28 UTC - James Thomas: :wave: everyone - tomorrow is the next 
bi-weekly community call.

Please message me with any agenda items you’d like to discuss at the Tech 
Interchange call tomorrow - Wednesday (February 20th).

Call details:

Web Meeting: Tech Interchange (bi-weekly):
- Day-Time: Wednesdays, 11AM EST(Eastern US), 5PM CET (Central Europe),
4PM UTC, 12AM CST (Beijing)
- Zoom: 
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550577388137400

2019-02-19 12:22:37 UTC - Rodric Rabbah: Did you update your git 

Re: Bi-Weekly Tech Interchange tomorrow - add agenda topics here

[James Thomas]

Erez & Matt - that's fine - I'll add you both.

On Tue, 19 Feb 2019 at 15:48, Matt Rutkowski  wrote:

> Priti and I would like to share our progress, findings and plans for
> making our OpenWhisk runtimes work (NodeJS primarily) with Knative (build
> and serving) with minimal impacts with the hopes it will get our comm.
> thinking about what are the essential differentiators of OW to carry
> forward on a Kube/Knative stack.
>
> Kind regards,
> Matt
>
>
>
> From:   James Thomas 
> To: dev@openwhisk.apache.org
> Date:   02/19/2019 06:01 AM
> Subject:Re: Bi-Weekly Tech Interchange tomorrow - add agenda
> topics here
>
>
>
> That should be "Wednesday (February 20th)."
>
> On Tue, 19 Feb 2019 at 11:55, James Thomas  wrote:
>
> > Hi,
> >
> > Please add to this thread any agenda items you'd like to discuss at the
> > Tech Interchange call tomorrow - Wednesday (February 19th).
> >
> > Call details:
> >
> > Web Meeting: Tech Interchange (bi-weekly):
> > - Day-Time: Wednesdays, 11AM EST(Eastern US), 5PM CET (Central Europe),
> > 4PM UTC, 12AM CST (Beijing)
> > - Zoom:
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_my_asfopenwhisk=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=6zQLM7Gc0Sv1iwayKOKa4_SFxRIxS478q2gZlAJj4Zw=EjhW8S-FqgHC1fjj5A000Vec_CnxYfUZLjxLz4VBR0o=MtC2AY2iR-Rek_ED143FEsuYjmlFxPs9W1m3dALg1Yo=
>
> >
> > --
> > Regards,
> > James Thomas
> >
>
>
> --
> Regards,
> James Thomas
>
>
>
>
>

-- 
Regards,
James Thomas

Re: Bi-Weekly Tech Interchange tomorrow - add agenda topics here

[Matt Rutkowski]

Priti and I would like to share our progress, findings and plans for 
making our OpenWhisk runtimes work (NodeJS primarily) with Knative (build 
and serving) with minimal impacts with the hopes it will get our comm. 
thinking about what are the essential differentiators of OW to carry 
forward on a Kube/Knative stack.

Kind regards,
Matt 



From:   James Thomas 
To: dev@openwhisk.apache.org
Date:   02/19/2019 06:01 AM
Subject:Re: Bi-Weekly Tech Interchange tomorrow - add agenda 
topics here



That should be "Wednesday (February 20th)."

On Tue, 19 Feb 2019 at 11:55, James Thomas  wrote:

> Hi,
>
> Please add to this thread any agenda items you'd like to discuss at the
> Tech Interchange call tomorrow - Wednesday (February 19th).
>
> Call details:
>
> Web Meeting: Tech Interchange (bi-weekly):
> - Day-Time: Wednesdays, 11AM EST(Eastern US), 5PM CET (Central Europe),
> 4PM UTC, 12AM CST (Beijing)
> - Zoom: 
https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_my_asfopenwhisk=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=6zQLM7Gc0Sv1iwayKOKa4_SFxRIxS478q2gZlAJj4Zw=EjhW8S-FqgHC1fjj5A000Vec_CnxYfUZLjxLz4VBR0o=MtC2AY2iR-Rek_ED143FEsuYjmlFxPs9W1m3dALg1Yo=

>
> --
> Regards,
> James Thomas
>


-- 
Regards,
James Thomas

Re: change the default action context to omit api key

[Rodric Rabbah]

Thanks to all the input here and on the PR - I think we ended up somewhere
positive. Here's a summary:

1. for pre-existing actions that are already deployed, they're
grandfathered in and will continue to behave in a way where they receive
the api key on activation. This is done by detecting the absence of the new
annotation.
2. the annotation is added on newly created actions only.
3. on update of pre-existing actions, the annotation is not added.

The latest code which now passes all the previous and tests (for backward
compatibility is here):
https://github.com/apache/incubator-openwhisk/pull/4284

-r


On Thu, Feb 14, 2019 at 9:37 PM Rodric Rabbah  wrote:

> I've implemented changes to the PR
> https://github.com/apache/incubator-openwhisk/pull/4284 for backward
> compatibility --- such that, actions which do not have the annotation will
> still get the api key injected.
>
> The annotation is added by the controller when an action is created or
> updated unless already present. The default value for the annotation is
> "false", meaning no key is injected to the action context.
>
> Furthermore comments and feedback is appreciated.
>
> -r
>

Re: updated CLI go vendors

[James W Dubee]

+1

-Rodric Rabbah  wrote: -
To: dev@openwhisk.apache.org
From: Rodric Rabbah 
Date: 02/16/2019 12:33PM
Subject: updated CLI go vendors

The following PR is the result of the a suggestion from homebrew

https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_incubator-2Dopenwhisk-2Dcli_pull_411=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=mNYL3iRkIHSpena7hJD92ihAR7Np-_j5HhizqqbvOHE=P6MBz9UmATt_8GRdWXcdsE3n-gZ25OE_hplEyW1l8pg=nkcebXcVtCgnX1vkhKsla0Gx2SA9Bd3SHHDk075ryPc=

It updates the go vendors with missing packages.

-r

Re: switch docker compose to "lean"?

[Rodric Rabbah]

> That makes sense. I see a lot of people having issues with the quick-start
> due to the number of components. Would need to document this change and
> explain how to change back as well.

I looked into the failures this past weekend. They’re either related to mimio 
or couch - I don’t understand the former but suspect the latter is just slow 
startup.

But agree generally that fewer moving parts is good with an initial experience: 
Three fewer images to pull and launch with lean.  

-r

Re: Bi-Weekly Tech Interchange tomorrow - add agenda topics here

[Erez Hadad]

Hi James,

I would like a slot to present the overhead benchmark tool which I 
announced earlier.

Regards,
-- Erez

Erez Hadad, PhD
Cloud System Technologies
IBM Research - Haifa
email: er...@il.ibm.com
phone: +972-4-829-6509





From:   James Thomas 
To: dev@openwhisk.apache.org
Date:   19/02/2019 14:03
Subject:Re: Bi-Weekly Tech Interchange tomorrow - add agenda 
topics here



That should be "Wednesday (February 20th)."

On Tue, 19 Feb 2019 at 11:55, James Thomas  wrote:

> Hi,
>
> Please add to this thread any agenda items you'd like to discuss at the
> Tech Interchange call tomorrow - Wednesday (February 19th).
>
> Call details:
>
> Web Meeting: Tech Interchange (bi-weekly):
> - Day-Time: Wednesdays, 11AM EST(Eastern US), 5PM CET (Central Europe),
> 4PM UTC, 12AM CST (Beijing)
> - Zoom: 
https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_my_asfopenwhisk=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=Oo9B0p_tCCWIIum5GpjjqA=RWf-e0Or5X6gaYAtL8c9wVQ9n_W3sxlBkBNGAYNhu3E=zRSWsBOFi_QsARgPRsosUk_xwKfq5ymOXvWvPvfBXBc=

>
> --
> Regards,
> James Thomas
>


-- 
Regards,
James Thomas

Re: switch docker compose to "lean"?

[James Thomas]

That makes sense. I see a lot of people having issues with the quick-start
due to the number of components. Would need to document this change and
explain how to change back as well.

On Sat, 16 Feb 2019 at 22:56, Carlos Santana  wrote:

> Yes +1 make compose lean
>
> - Carlos Santana
> @csantanapr
>
> > On Feb 16, 2019, at 1:21 PM, Rodric Rabbah  wrote:
> >
> > A PR we recently merged add the ability to deploy openwhisk in a lean
> > configuration - without kafka/zookeeper (thanks Pavel!). Should the make
> > quick-start target for docker compose use it by default?
> >
> > I'm trying to reproduce failures reported in the slack channel for
> > docker-compose/make quick-start and it occurred to me we can startup even
> > faster with the lean configuration.
> >
> > -r
>


-- 
Regards,
James Thomas

Re: Bi-Weekly Tech Interchange tomorrow - add agenda topics here

[James Thomas]

That should be "Wednesday (February 20th)."

On Tue, 19 Feb 2019 at 11:55, James Thomas  wrote:

> Hi,
>
> Please add to this thread any agenda items you'd like to discuss at the
> Tech Interchange call tomorrow - Wednesday (February 19th).
>
> Call details:
>
> Web Meeting: Tech Interchange (bi-weekly):
> - Day-Time: Wednesdays, 11AM EST(Eastern US), 5PM CET (Central Europe),
> 4PM UTC, 12AM CST (Beijing)
> - Zoom: https://zoom.us/my/asfopenwhisk
>
> --
> Regards,
> James Thomas
>


-- 
Regards,
James Thomas

Bi-Weekly Tech Interchange tomorrow - add agenda topics here

[James Thomas]

Hi,

Please add to this thread any agenda items you'd like to discuss at the
Tech Interchange call tomorrow - Wednesday (February 19th).

Call details:

Web Meeting: Tech Interchange (bi-weekly):
- Day-Time: Wednesdays, 11AM EST(Eastern US), 5PM CET (Central Europe),
4PM UTC, 12AM CST (Beijing)
- Zoom: https://zoom.us/my/asfopenwhisk

-- 
Regards,
James Thomas

Proposing a new performance benchmark tool for OpenWhisk - overhead

[Erez Hadad]

Hi folks,

I'm seeking feedback on a new performance benchmark tool called overhead, 
that I'm proposing for OpenWhisk. This tool contains several new 
capabilities beyond exiting tools (wrk/gatling), such as benchmarking 
rules (trigger-to-action) in addition to action invocations (sync and 
async), deeper profiling without special setup/instrumentation (Kamino), 
based on timestamps from the activation records, and more. Please have a 
look at the README.md for details.

https://github.com/IBM/overhead

Please review, use the tool, and comment - I'd like to contribute this 
tool to the OW repo.
 
Regards,
-- Erez

Erez Hadad, PhD
Cloud System Technologies
IBM Research - Haifa
email: er...@il.ibm.com
phone: +972-4-829-6509