2019-11-20 11:33:51 UTC - volo: hi, does openwhisk have commercial support? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1574249631362700 ---- 2019-11-20 13:28:03 UTC - Logan Marks: I’m fairly sure the yml that deploys the alarm container hasn’t been changed from what we took off of git originally https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1574256483362800?thread_ts=1574092437.343400&cid=C3TPCAQG1 ---- 2019-11-20 13:28:35 UTC - Logan Marks: I know for sure the alarm container _is_ deployed as I can see it running, but it doesn’t appear to be giving us any useful logs https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1574256515363000?thread_ts=1574092437.343400&cid=C3TPCAQG1 ---- 2019-11-20 16:56:46 UTC - Rodric Rabbah: this question has come up a few times recently - we should create a page about commercial support and link to consultants or companies that are/can offer this. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1574269006363900 ---- 2019-11-20 16:56:50 UTC - Rodric Rabbah: i’ll bring this up to the dev list https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1574269010364200 ---- 2019-11-20 17:10:17 UTC - giusdp: Hey there, what's the difference between blackbox and managed invocation? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1574269817364600?thread_ts=1574269817.364600&cid=C3TPCAQG1 ---- 2019-11-20 17:29:59 UTC - Rodric Rabbah: Blackbox means it’s a container built by the end user and deployed to their registry.
A managed runtime means just the code (file or zip file or jar) which is injected into an appropriate container/runtime by the system. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1574270999366600?thread_ts=1574269817.364600&cid=C3TPCAQG1 ---- 2019-11-20 17:30:28 UTC - Rodric Rabbah: Welcome @Abel Berenstein heart : seonghyun https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1574271028367200 ---- 2019-11-20 17:35:00 UTC - giusdp: Ok thank you. I was looking at the sharding container load balancer and saw it differentiates the two. Do you think it would be possible to modify the load balancer to have a queue for each invoker? (From there a loadbalancer could enqueue invocations for different invokers using some sort of heuristic) https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1574271300367300?thread_ts=1574269817.364600&cid=C3TPCAQG1 ---- 2019-11-20 17:46:11 UTC - Rodric Rabbah: They’re differentiated because the docker images are pulled on demand and so have different startup costs and footprints. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1574271971368500?thread_ts=1574269817.364600&cid=C3TPCAQG1 ---- 2019-11-20 17:46:35 UTC - Rodric Rabbah: You can do that, sure. Depends on your goals. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1574271995369200?thread_ts=1574269817.364600&cid=C3TPCAQG1 ---- 2019-11-20 20:53:55 UTC - Abel Berenstein: Hi. I want to deploy function as blackboxes with wskdeploy but cannot find any example of manifest for deploying of already dockerized functions. Has anybody a pointer to a manifest to deploy blackbox? TIA. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1574283235374200?thread_ts=1574283235.374200&cid=C3TPCAQG1 ---- 2019-11-20 20:57:57 UTC - Jason Peterson: actually, if the error you pasted above regarding `ENOTFOUND` above is coming from the action then it is not related to the alarms container https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1574283477374300?thread_ts=1574092437.343400&cid=C3TPCAQG1 ---- 2019-11-20 20:58:07 UTC - Jason Peterson: the action does not talk to the alarms container. only to the web action which in turns talks to the alarms DB https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1574283487374500?thread_ts=1574092437.343400&cid=C3TPCAQG1 ---- 2019-11-20 20:59:03 UTC - Jason Peterson: sounds like an issue with the web action still https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1574283543374800?thread_ts=1574092437.343400&cid=C3TPCAQG1 ---- 2019-11-20 21:01:58 UTC - Jason Peterson: doubt it is specific to alarms though https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1574283718375000?thread_ts=1574092437.343400&cid=C3TPCAQG1 ---- 2019-11-20 21:02:28 UTC - Rodric Rabbah: is it a misconfiguration of the feed package during installation? the host is `http` no api host, port, etc. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1574283748375200?thread_ts=1574092437.343400&cid=C3TPCAQG1 ---- 2019-11-20 21:03:08 UTC - Rodric Rabbah: maybe taking a look at what parameters are bound to the package/action can help https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1574283788375500?thread_ts=1574092437.343400&cid=C3TPCAQG1 ---- 2019-11-20 21:15:20 UTC - Jason Peterson: I agree. probably related to parameters for action and or web action install https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1574284520375800?thread_ts=1574092437.343400&cid=C3TPCAQG1 ---- 2019-11-20 21:16:50 UTC - Jason Peterson: for some reason, I thought I read that they had seen this same error when they were not using their own actions. threw me off track https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1574284610376000?thread_ts=1574092437.343400&cid=C3TPCAQG1 ---- 2019-11-20 22:02:08 UTC - Abel Berenstein: Aren't managed invocations started up on demand as well, rr? How are startup costs compare between them? TIA. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1574287328376200?thread_ts=1574269817.364600&cid=C3TPCAQG1 ---- 2019-11-20 22:49:26 UTC - Rodric Rabbah: they are but the container images are known in advance so they are readily available - they can also be speculatively started so that a colde start could be < 10ms. you can’t do that with a blackbox image without taking on more risk. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1574290166376400?thread_ts=1574269817.364600&cid=C3TPCAQG1 ----
