2019-02-20 06:50:59 UTC - Lars Andersson: @dubee All tests seem to have passed.
This was not a modification to the API, just how the output was rendered by the
client-go component.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550645459149600?thread_ts=1550569355.136300&cid=C3TPCAQG1
----
2019-02-20 11:17:20 UTC - Satwik Kolhe: Need help with this : What is the
concurrency min/max/std limit mentioned in values.yaml
(whisk.limits.actions.concurrency) while deploying openwhisk using helm? How is
this different from whisk.limits.actionsInvokesConcurrent?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550661440150900
----
2019-02-20 13:21:46 UTC - Dominic Kim: @Satwik Kolhe I think the first one is
intra-container concurrency, while the second one is action concurrency.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550668906000700
----
2019-02-20 13:22:52 UTC - Dominic Kim: So you can invoke 3 invocations
concurrently with 3 `actionsInvokesConcurrent` and can invoke 3 invocations
using one container with 3 `whisk.limits.actions.concurrency`
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550668972001800
----
2019-02-20 13:23:41 UTC - Satwik Kolhe: Cool. Thanks.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550669021002100
----
2019-02-20 14:35:16 UTC - Satwik Kolhe: @Michele Sciabarra I found a way to
deploy ow using persistent storage (following our last discussion of using rook
to deploy ow) - by creating pv using "data" storageclass. This essentially
works like volume-mount in docker. You need to define pv and pvc before
deploying ow using helm (in the same namespace in which pvc's are created). And
when redis, couchdb etc spin-up and use pvc, all the specified directories are
created on appropriate k8s nodes, and your data is stored locally (which can be
mounted on nfs as well). Its the simplest form of providing pv to pods in k8s.
Additionally I had to edit the helm/openwhisk/templates/*-pvc.yaml to use use
existing (already created) pvc for the ow deployment.
Please check the yaml below for reference.
```kind: PersistentVolume
apiVersion: v1
metadata:
name: couchdb-pv
spec:
storageClassName: data
capacity:
storage: 5Gi
claimRef:
namespace: enfn-stage-1
name: couchdb-pvc
accessModes:
- ReadWriteMany
hostPath:
path: "/ow-data/couchdb/"
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: couchdb-pvc
namespace: enfn-stage-1
spec:
storageClassName: data
accessModes:
- ReadWriteMany
resources:
requests:
storage: 5Gi```
Please let me know if this is of any help for the community!
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550673316008800
----
2019-02-20 15:00:20 UTC - Slackbot: Reminder: Web Meeting: Tech Interchange
(bi-weekly):
* Day-Time: Wednesdays, 11AM EST (Eastern US), 5PM CET (Central Europe), 4PM
GMT, 12AM (midnight) BST (Beijing)
* Zoom: <https://zoom.us/my/asfopenwhisk>
* Google Calendar (click entry to add): <http://bit.ly/2FHien6>
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550674820000100
----
2019-02-20 15:32:45 UTC - James Thomas:
<https://twitter.com/openwhisk/status/1098243977839607812>
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550676765000400
----
2019-02-20 16:00:27 UTC - Matt Rutkowski: STARTING NOW! Apache OpenWhisk
project Tech. Interchange meeting:
<https://zoom.us/my/asfopenwhisk>
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550678427000700
----
2019-02-20 16:01:04 UTC - Rodric Rabbah: hahah Whiskers Assemble
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550678464000900
----
2019-02-20 16:23:34 UTC - Rodric Rabbah: @Matt Rutkowski, question for post
zoom: instead of modifying the runtime to bypass init, did you consider leaving
the runtime alone and modifying the invoke protocol so that for some annotated
actions it skips calling `/init`. I understood from the presentation that the
code is bundled into the container already — like our blackbox/docker images
where init is just a no-op. Does this reduce some of the complexity in
“forking” the runtimes?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550679814002000
----
2019-02-20 16:24:38 UTC - Rodric Rabbah: ah… from the demo maybe i
misunderstood… did the “run” receive the function code?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550679878002400
----
2019-02-20 16:37:12 UTC - Carlos Santana: Finally someone wrote the tool I
always wanted :raised_hands: <https://github.com/IBM/overhead> :whisking:
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550680632003200
----
2019-02-20 16:38:19 UTC - Rodric Rabbah: bad name :smile:
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550680699003400
----
2019-02-20 16:38:31 UTC - Rodric Rabbah: ibm ovehead is _____
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550680711003900
----
2019-02-20 16:39:02 UTC - Rodric Rabbah: but def looking like a great tool for
measuring openwhisk perf and normalizing experiments perhaps
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550680742004600
----
2019-02-20 16:39:27 UTC - Rodric Rabbah: glad to see the ibm github org is
finally open for hosting actual projects from ibm!
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550680767005000
----
2019-02-20 16:40:31 UTC - Carlos Santana: yeah we can rename it to FaaSt or
something like that
grinning : Neeraj Mangal
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550680831005400?thread_ts=1550680831.005400&cid=C3TPCAQG1
----
2019-02-20 16:41:08 UTC - Rodric Rabbah: :yay:
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550680868005600
----
2019-02-20 16:41:32 UTC - Carlos Santana: I should work on branding, I don't
know what I'm doing on engineering
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550680892006000
----
2019-02-20 16:41:55 UTC - Carlos Santana: :moneybag:
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550680915006300
----
2019-02-20 16:46:50 UTC - Rodric Rabbah: @Erez Hadad you might know about this
already <https://github.com/apache/incubator-openwhisk/issues/2614>
re benchmarking rule performance
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550681210007000
----
2019-02-20 17:03:34 UTC - Matt Rutkowski: @Rodric Rabbah in regard to skipping
init, short answer (as you heard on Zoom) was no…
we could look at leaving /init registered, but with “build” so easy to do it
seems like it would end up with more code overhead leaving it exposed (and
perhaps increase the need/consideration for security testing, etc.).
In addition, what I did not say on the call was that with the conditional
“build” we can build for other target platforms like Lambda quite easily as
well. As you add support for more platforms the “contracts”/caps. change and
then you end up with lots of spaghetti code IF-THEN-ELSE, plus in knative you
can inspect the build logs and see the code itself (with permissions) and it
would be nice to see only the logic you are familiar with for your platform
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550682214010900
----
2019-02-20 17:03:45 UTC - Matt Rutkowski: and for debug/profiling builds as
well the extra logic could end up being confusing (and a tiny drag on code
execution).
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550682225011200
----
2019-02-20 20:16:12 UTC - mmarth: underhead
joy : Carlos Santana
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550693772011700?thread_ts=1550680831.005400&cid=C3TPCAQG1
----
