You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwhisk.apache.org by OpenWhisk Team Slack <ra...@apache.org> on 2019/10/03 09:01:39 UTC

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

2019-10-02 02:39:40 UTC - Mayank Jha: is there a shortcut to replace the existing runtimes for a different cpu architecture say arm64 ?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1569983980071300?thread_ts=1569983980.071300&cid=C3TPCAQG1
----
2019-10-02 02:40:16 UTC - Rodric Rabbah: I don’t understand what you mean. 
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1569984016071700?thread_ts=1569983980.071300&cid=C3TPCAQG1
----
2019-10-02 02:40:31 UTC - Rodric Rabbah: Like a different container base image?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1569984031072200?thread_ts=1569983980.071300&cid=C3TPCAQG1
----
2019-10-02 02:42:23 UTC - Mayank Jha: So in the runtimes.json manifest file we have names of the various docker images (to be used by invoker) like nodejs, go etc. right ? All of it are amd64 based images. I wanted arm64 images.  Any shortcut to get that ?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1569984143072500?thread_ts=1569983980.071300&cid=C3TPCAQG1
----
2019-10-02 02:47:00 UTC - Rodric Rabbah: Ah. Just add another entry or change one of the ones there. 
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1569984420073100?thread_ts=1569983980.071300&cid=C3TPCAQG1
----
2019-10-02 02:47:46 UTC - Rodric Rabbah: once you update that file redeploy controllers/invokers and you should be able to use the new runtime for functions. 
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1569984466074100?thread_ts=1569983980.071300&cid=C3TPCAQG1
----
2019-10-02 02:53:50 UTC - Mayank Jha: But the pain is for stuff like nodejs, go, I have to actually build the arm64 images. Cannot find it on dockerhub :disappointed: Any workaround for that ?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1569984830074300?thread_ts=1569983980.071300&cid=C3TPCAQG1
----
2019-10-02 02:57:28 UTC - Mayank Jha: Even the testaction image is failing out of architecture incompatibility. Any clue where i can build it ?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1569985048074500?thread_ts=1569983980.071300&cid=C3TPCAQG1
----
2019-10-02 03:10:22 UTC - Rodric Rabbah: I don’t think we have arm builds. You want to build all the images for arm?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1569985822075500?thread_ts=1569983980.071300&cid=C3TPCAQG1
----
2019-10-02 03:15:41 UTC - Mayank Jha: Yep
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1569986141075700?thread_ts=1569983980.071300&cid=C3TPCAQG1
----
2019-10-02 03:15:57 UTC - Mayank Jha: As I am needing to run openwhisk on arm.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1569986157075900?thread_ts=1569983980.071300&cid=C3TPCAQG1
----
2019-10-02 03:22:09 UTC - Rodric Rabbah: Each of the runtimes is in its own repo, witg docker files and build scripts. You’d have to build them all from source. 
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1569986529077000?thread_ts=1569983980.071300&cid=C3TPCAQG1
----
2019-10-02 03:22:26 UTC - Rodric Rabbah: You could download the releases from the Apache project page too I suppose. 
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1569986546077600?thread_ts=1569983980.071300&cid=C3TPCAQG1
----
2019-10-02 14:37:10 UTC - Matt Rutkowski:  set up a reminder “Tech Interchange Web Meeting (bi-weekly) https://zoom.us/my/asfopenwhisk” in this channel at 10AM every other Wednesday (next occurrence is October 9th), Eastern Daylight Time.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1570027030078300
----
2019-10-02 14:38:04 UTC - Matt Rutkowski:  set up a reminder “Tech Interchange Web Meeting (bi-weekly) https://zoom.us/my/asfopenwhisk” in this channel at 10AM every other Wednesday (next occurrence is October 16th), Eastern Daylight Time.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1570027084078400
----
2019-10-02 14:45:42 UTC - Rodric Rabbah: Has anyone looked at typescript enablement in the node runtime yet?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1570027542079000
----
2019-10-02 19:41:53 UTC - Adrian Schuepbach: Dear all

I have a small cluster of 8 nodes with 32 cores and 96GB RAM each.
I run Kubernetes on the nodes and deployed OpenWhisk on Kubernetes.

I implemented an OpenWhisk function and invoke it 64 times
in a burst. I set the timeout to 5min and the memory limit to 2GB.
I noticed that only one function container gets spawned on OpenWhisk.

It would be great, if at least a container per node would be started
or even multiple containers per node to increase parallel execution.

Another function, which I install with a memory limit of 512MB,
spawns 4 containers in parallel.

It the reason for only having one container a configurable limit?
A memory limit? Do I need to change some configuration?

Thanks Adrian
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1570045313080000
----
2019-10-02 20:19:55 UTC - Dave Grove: in `helm/openwhisk/values.yaml` `whisk.containerPool.userMemory` has a default of 2048m.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1570047595081100
----
2019-10-02 20:21:44 UTC - Dave Grove: when you deploy openwhisk, change this to be appropriate for your system.  You probably also want to change `invoker.containerFactory.kubernetes.replicaCount` to be more than the default value of `1` as well.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1570047704082600
----
2019-10-02 20:23:53 UTC - Dave Grove: There’s a discussion of this buried in <https://github.com/apache/openwhisk-deploy-kube/blob/master/docs/configurationChoices.md#invoker-container-factory>, but it is easy to overlook.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1570047833083000
----
2019-10-02 20:53:44 UTC - Adrian Schuepbach: Thanks a lot, this solved it!

btw: for the "kubernetes" containerFactory implementation I set `agent: enabled: true`, as the documentation says. I indeed see two agents, but they keep crashing or actually do not even fully start. It seems that I cannot get logs with `kubectl logs` or `kubectl logs --previous`, so I don't really know, why they are crashing. Still, the actions get executed.

This is how the status looks like:

```
owdev-invoker-agent-54rxm                           0/1     Init:CrashLoopBackOff   79         7h4m
owdev-invoker-agent-lz77j                           0/1     Init:CrashLoopBackOff   80         7h4m
```

It regularly tries to restart.

How could I best look into the issue?
Thanks
Adrian
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1570049624086600
----
2019-10-02 21:40:20 UTC - Dave Grove: sorry, I should update the documentation on the invoker-agents.  they are experimental and we moved away from using them by default.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1570052420088800
----
2019-10-02 21:42:55 UTC - Dave Grove: looks like they rotted.   you don’t need them unless you want to pause/unpause “idle” user action containers to prevent users from running background work “for free” between invocations of actions
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1570052575091200
----
2019-10-02 22:00:17 UTC - Adrian Schuepbach: thank you for the explanation, good to know, so I will just disable the invoker-agents.

Thanks a lot!
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1570053617091900
----
2019-10-02 22:06:42 UTC - Dave Grove: i suspect the issue is that your Kubernetes cluster is using containerd as the underlying container engine, not docker.  The invoker-agent is playing some dirty tricks (like the DockerContainerFactory does) to go around Kubernetes and talk to the docker daemon on the worker node directly.  no docker daemon, and it will go into a crash loop
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1570054002094000
----
2019-10-02 22:45:09 UTC - Adrian Schuepbach: aha, yes, that explains it, indeed, I am running containerd. Actually, I did not pay attention, whether it uses containerd or docker, when deploying kubernetes...
so it seems that for OpenWhisk -- or at least some services/functionalities of OpenWhisk -- it would be ideal to run docker and not containerd
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1570056309095700
----