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/04/09 07:36:14 UTC
[slack-digest] [2019-04-08] #random
2019-04-08 00:00:13 UTC - Jin Choi: I don't find any version numbers in `wsk -i action list` if it's related to each action version.
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1554681613065500?thread_ts=1554681613.065500&cid=C3UDXSFA6
----
2019-04-08 01:05:23 UTC - Jin Choi: Also, I am curious if the `apiversion` flag in wsk command is effective currently
```$ wsk -h
...omit...
Flags:
...omit...
--apiversion VERSION whisk API VERSION
...omit...```
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1554685523066700?thread_ts=1554685523.066700&cid=C3UDXSFA6
----
2019-04-08 03:27:52 UTC - Neeraj Mangal: @Jin Choi, its related to each action version and you can see that with ‘wsk -i action get <actionName>’.
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1554694072067000?thread_ts=1554681613.065500&cid=C3UDXSFA6
----
2019-04-08 03:29:08 UTC - Neeraj Mangal: AFAIK, --apiversion, is global flag which determines the whisk API version in backend like v1/v2 which CLI uses to make request and its not related to action versions.
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1554694148067200?thread_ts=1554685523.066700&cid=C3UDXSFA6
----
2019-04-08 04:06:10 UTC - Jin Choi: Thanks for the reply. In which case would I have an action of other version than 0.0.1 ?
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1554696370067500?thread_ts=1554681613.065500&cid=C3UDXSFA6
----
2019-04-08 04:16:48 UTC - Jin Choi: I mean, how can I register an action with, say, `1.0.2` with wsk command?
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1554697008068100?thread_ts=1554681613.065500&cid=C3UDXSFA6
----
2019-04-08 04:17:44 UTC - Jin Choi: One openwhisk system can have multiple versions? How can I do it?
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1554697064068300?thread_ts=1554685523.066700&cid=C3UDXSFA6
----
2019-04-08 04:20:15 UTC - Neeraj Mangal: Currently I don’t see an option there but version got updated on each action update command.
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1554697215068500?thread_ts=1554681613.065500&cid=C3UDXSFA6
----
2019-04-08 04:26:59 UTC - Rodric Rabbah: There’s currently only v1
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1554697619068900?thread_ts=1554685523.066700&cid=C3UDXSFA6
----
2019-04-08 04:27:19 UTC - Rodric Rabbah: If you added api/v2 this flag would allow you to change that routing
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1554697639069600?thread_ts=1554685523.066700&cid=C3UDXSFA6
----
2019-04-08 04:27:58 UTC - Rodric Rabbah: The version currently cannot be set by the user.
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1554697678070400?thread_ts=1554681613.065500&cid=C3UDXSFA6
----
2019-04-08 05:13:52 UTC - Jin Choi: @Rodric Rabbah So there is no way to add api/v2 for now, right?
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1554700432070600?thread_ts=1554685523.066700&cid=C3UDXSFA6
----
2019-04-08 05:14:58 UTC - Jin Choi: @Rodric Rabbah any case I would see a different version, such as 0.0.2, in any case, currently?
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1554700498070800?thread_ts=1554681613.065500&cid=C3UDXSFA6
----
2019-04-08 05:16:02 UTC - Rodric Rabbah: As noted above every action update bumps the version
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1554700562072600?thread_ts=1554681613.065500&cid=C3UDXSFA6
----
2019-04-08 05:16:29 UTC - Rodric Rabbah: Caveat. If you delete and recreate the action you start at 0.0.1 again.
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1554700589073800?thread_ts=1554681613.065500&cid=C3UDXSFA6
----
2019-04-08 05:17:23 UTC - Rodric Rabbah: OpenWhisk has only one api version today but you can certainly add new version in the api controller. What are you trying to do
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1554700643075900?thread_ts=1554685523.066700&cid=C3UDXSFA6
----
2019-04-08 05:19:54 UTC - Jin Choi: Great, I got you.
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1554700794077100?thread_ts=1554681613.065500&cid=C3UDXSFA6
----
2019-04-08 05:25:57 UTC - Jin Choi: I am trying to understand the cold/prewarm/warm state of a runtime container.
I read through this great article: <https://medium.com/openwhisk/squeezing-the-milliseconds-how-to-make-serverless-platforms-blazing-fast-aea0e9951bd0> (Thanks, @Markus Thömmes)
So I did an experiment on my vagrant machine. ( only 1 invoker there is)
I ran a simple hello world nodejs6 action. I expected the system to reuse any one of the two prewarmed nodejs6 containers for my invocation.
```179defbc9cd9 wsk00_5_prewarm_nodejs6 0.00% 16.23MiB / 256MiB 6.34% 912B / 0B 5.42MB / 0B 7
57f5ccc1397e wsk00_4_prewarm_nodejs6 0.00% 15.79MiB / 256MiB 6.17% 1.03kB / 0B 2.02MB / 0B 7```
But the system ran another nodejs6 container for an action invocation.
```179defbc9cd9 wsk00_5_prewarm_nodejs6 0.00% 16.23MiB / 256MiB 6.34% 1.1kB / 0B 5.42MB / 0B 7
57f5ccc1397e wsk00_4_prewarm_nodejs6 0.00% 16.94MiB / 256MiB 6.62% 2.7kB / 1.03kB 2.99MB / 0B 7
b5ebbbc7c5ef wsk00_7_prewarm_nodejs6 2.47% 16.07MiB / 256MiB 6.28% 258B / 0B 1.05MB / 0B 7```
Would you help me to understand the mechanism, and why another nodejs6 container here?
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1554701157080200
----
2019-04-08 05:27:20 UTC - Rodric Rabbah: Stem cell containers (prewarmed) are replenished as they’re used.
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1554701240081000
----
2019-04-08 05:28:06 UTC - Jin Choi: And updating an action should replace the code in CouchDB inplace, right? When my `hello` action becomes version 0.0.2 I can't invoke the action of version 0.0.1 anymore. Do I get it alright?
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1554701286081100?thread_ts=1554681613.065500&cid=C3UDXSFA6
----
2019-04-08 05:29:30 UTC - Rodric Rabbah: You can’t at user level, no. But a system under load may have queued activations for the older version. Those should execute fine for a short window of time.
thankyou : Jin Choi
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1554701370083200?thread_ts=1554681613.065500&cid=C3UDXSFA6
----
2019-04-08 07:28:30 UTC - Jin Choi: Sound effective @Rodric Rabbah.
If so, my best guess is as follows:
1. the replenished container would stay idle once it got launched. It's because it's not launched for the very action invocation but for the possibly upcoming invocations in the near future.
2. Judging by the memories of those two containers, wsk00_5_prewarm_nodejs6 and wsk00_4_prewarm_nodejs6, wsk00_4 rising by +0.71MB when wsk00_6 staying the same as before, the wsk00_4 must have been the runtime used for the hello action invocation. (Again, it was not the replenished container which executed the action invocation request)
3. The replenished one would disappear when it stays idle enough.
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1554708510091300
----
2019-04-08 07:28:51 UTC - Jin Choi: Did I get it all right?
white_check_mark : Rodric Rabbah, Jin Choi
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1554708531091800
----
2019-04-08 07:38:21 UTC - Jin Choi: I am just curious if I am missing some features. I stumbled upon the flag, `--apiversion`, and got wondering if there was some option for deployment for versioning.
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1554709101092100?thread_ts=1554685523.066700&cid=C3UDXSFA6
----
2019-04-08 07:40:46 UTC - Jin Choi: I think it would be a nice feature to have, so we can upgrade the system safely with the backward portability. If that's where the project is heading
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1554709246092300?thread_ts=1554685523.066700&cid=C3UDXSFA6
----
2019-04-08 20:03:30 UTC - Rodric Rabbah: since i posted krish’s demise of cf article, it’s appropriate to post this <https://www.techrepublic.com/article/cloud-foundrys-embrace-of-kubernetes-is-business-as-usual-not-a-demise/>
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1554753810093000
----
2019-04-08 20:03:55 UTC - Rodric Rabbah: _the fact that Cloud Foundry has been changing the technologies that power its platform is immaterial to customer success with that platform._
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1554753835093500
----