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/17 07:40:23 UTC
[slack-digest] [2019-04-16] #random
2019-04-16 00:00:16 UTC - Roberto Diaz: I have been checking the composer documentation but I haven't seen any `combinator` in the way of a `switch` I mean, an `if` with multiple `else if` branches, is that possible to implement using combinators?
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1555372816025600
----
2019-04-16 03:25:43 UTC - Rodric Rabbah: you could write your own combinator if it doesn’t exist, pattern after if combinator - @Olivier Tardieu?
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1555385143027100
----
2019-04-16 07:57:47 UTC - Roberto Diaz: I continued diving into the documentation and I found the conductor actions, they are exactly what I need for my case
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1555401467028300
----
2019-04-16 10:10:46 UTC - Roberto Diaz: regarding conductor actions, how are they charged at IBM cloud? are you paying for conductor action during the whole sequence + each individual actions? or are you paying for each conductor call + each individual action?
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1555409446030700?thread_ts=1555409446.030700&cid=C3UDXSFA6
----
2019-04-16 10:17:15 UTC - James Thomas: ^^ @Olivier Tardieu
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1555409835030900
----
2019-04-16 13:26:38 UTC - Carlos Santana: You get charge only for the time for each individual action regardless if they in a sequence, the conductor action might run a couple of times they also get charge as individual actions. You don’t get charge for small think time in a sequence between two actions.
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1555421198033700?thread_ts=1555409446.030700&cid=C3UDXSFA6
----
2019-04-16 13:28:58 UTC - Roberto Diaz: awesome! thanks!
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1555421338035400?thread_ts=1555409446.030700&cid=C3UDXSFA6
----
2019-04-16 13:29:14 UTC - Rodric Rabbah: further iirc the total duration of the composition (billed for sum of the parts) was used for billing (not the sum of costs per part)
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1555421354035900?thread_ts=1555421354.035900&cid=C3UDXSFA6
----
2019-04-16 13:31:59 UTC - Carlos Santana: Yes that affects 100ms granularity, we sum up the individual actions in a single sequence, for example a sequence with 4 actions each 25ms you get charge for 100ms. If you call this actions outside a sequence for example directly with wsk CLI they all get rounded to the 100ms, so you get charge 400ms. Hope this helps
+1 : Rob Allen
https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1555421519039500?thread_ts=1555421354.035900&cid=C3UDXSFA6
----