2021-01-21 17:40:49 UTC - Mina Michael: Hi guys. We're trying to find documentation for "wsk action create". Where can we find documentation for the openwhisk client? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1611250849000700?thread_ts=1611250849.000700&cid=C3TPCAQG1 ---- 2021-01-21 17:57:43 UTC - Mina Michael: Okay so we're using `wsk action create --help` . https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1611251863000800?thread_ts=1611250849.000700&cid=C3TPCAQG1 ---- 2021-01-21 20:15:41 UTC - Mina Michael: Hi again. So we have a custom Kubernetes scheduler running. What I'm trying to do is attach some metadata to actions. Our scheduler can see information about the pod that gets created when an action is invoked. I can see the name of the pod for example. I want to be able to attach things to the function (maybe at creation time) which I would then be able to retrieve.
We've taken a look at the "wsk action create" documentation. We've tried the `--annotation-file` flag and the `--param-file` flag. We have a json file with a test key-value pair. But we can't see it in the pod information that we have. Any ideas? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1611260141005400?thread_ts=1611260141.005400&cid=C3TPCAQG1 ---- 2021-01-21 21:03:15 UTC - Rodric Rabbah: there is a doc here <https://github.com/apache/openwhisk/blob/master/docs/actions.md> if you’re looking for usage instructions. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1611262995005500?thread_ts=1611250849.000700&cid=C3TPCAQG1 ---- 2021-01-21 21:03:35 UTC - Rodric Rabbah: did you end up figuring out the scheduler/controller property? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1611263015005700?thread_ts=1611260141.005400&cid=C3TPCAQG1 ---- 2021-01-21 21:04:30 UTC - Rodric Rabbah: So you want to attach metadata to the action and make it visible to your scheduler? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1611263070005900?thread_ts=1611260141.005400&cid=C3TPCAQG1 ---- 2021-01-21 22:47:57 UTC - Alessandro Banfi: Hi everyone, I am testing my actions on Openwhisk standalone and I'm not able to execute more than 4 instances of the same action at the same time. The action in object is a dummy one developed in golang that sleeps for 100 seconds before return. I'm experiencing the same issue both using the standalone installation with and without the --all option, with and without the playground ui and after increasing the system limits. In order to do my tests I checked out version 1.0.0. It seems like the action invocations are cached and also invoking them in bunches of 10, just 4 containers are started up and the others are invocated just after the previous 4 are shut down. I don't know if I misunderstood how Openwhisk works or I missing something, let me know if it is the case. I uploaded a video of my last test where I invoked several times the same action and just 4 containers are started up. On the testing machine I should have enough cpu and memory (125GB) to run all the invoked actions. Thank you for your time! https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1611269277018900?thread_ts=1611269277.018900&cid=C3TPCAQG1 ---- 2021-01-21 23:30:36 UTC - Rodric Rabbah: i think that’s expected - the default configuration is 4 container on a core. You can override this by providing a `container-pool` configuration with a higher `user-memory` value https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1611271836019200?thread_ts=1611269277.018900&cid=C3TPCAQG1 ----
