[slack-digest] [2019-07-11] #random

2019-07-11 01:52:12 UTC - Rodric Rabbah: https://openwhisk-team.slack.com/archives/C3UDXSFA6/p1562809932025100 2019-07-11 04:54:04 UTC - chetanm: This is pretty powerful! Bringing similar model like `docker run` for vms. And

[slack-digest] [2019-07-11] #general

2019-07-11 07:45:37 UTC - Adam Varsano: Hi all, I start developing my business via openwhisk. I deployed the openwhisk on rancher via helm chart: The issue is that every few days/weeks something fall like zoo keeper pod. Then it doesn't

Execute OpenWhisk action via Ignite and Firecracker VM (pr #4556)

Hi Team, Seeing the recent Weave Ignite announcement [1] I tried to implement a quick prototype for integrating it with OpenWhisk [2]. So far the results are good and OpenWhisk can create and launch ignite/firecracker based vm for action invocation. Currently the cold startup times have few issue

devtools and make-quickstart

this issue was opened against devtools and raises an important point: https://github.com/apache/incubator-openwhisk-devtools/issues/273 "On a separate note, will these builds eventually be versioned or will they continue to be tagged in a backwards incompatible way? I am trying to create a build p

Re: devtools and make-quickstart

+1 on the first point. I've seen other issues in the past with the devtools project based on image versioning stuff. Given devtools is more for experimental and first-steps than production usage - switching to the standalone controller seems like a good idea. On Fri, 12 Jul 2019 at 16:15, Rodric

Re: devtools and make-quickstart

"...we should pin all the dependent images etc and make a release available" +1 I also like the standalone JAR. Should we consider adding to that the API Management features made available through OW GW, or for that we should keep the docker-compose route ? On Fri, Jul 12, 2019 at 8:53 AM Jam

Re: devtools and make-quickstart

> I also like the standalone JAR. Should we consider adding to that the API Management features made available through OW GW, or for that we should keep the docker-compose route ? I did get the API gateway to run (in the container) with standalone openwhisk. I ran the ansible playbook (wskdev apig