Re: Preview of a OpenWhisk IDE & Debugger... and an help request
Yes. As I wrote, ngrok is optional. It's all described in the "how it works" section [1]. The default mechanism requires action concurrency though, which not all Openwhisk deployments have (apparently IBM cloud functions do not yet (?)). Alternatively there is a third option that should always work, but is slow. It uses tricks with activation records. This is picked automatically if concurrency is not available. There is currently still a bug [2] where this detection doesn't work in all cases. [1] https://github.com/adobe/wskdebug#how-it-works [2] https://github.com/adobe/wskdebug/issues/30 Cheers, Alex From: Michele Sciabarra Sent: Wednesday, February 19, 2020 10:04 To: dev@openwhisk.apache.org Subject: Re: Preview of a OpenWhisk IDE & Debugger... and an help request But is it possible to use without ngrok? I mean, if I have to run everything behind a firewall with the standalone openwhisk, does it work? -- Michele Sciabarra mich...@sciabarra.com - Original message - From: Alexander Klimetschek To: "dev@openwhisk.apache.org" Subject: Re: Preview of a OpenWhisk IDE & Debugger... and an help request Date: Wednesday, February 19, 2020 7:02 PM Bertrand wrote: > IIUC there's no bundling of ngrok with wskdebug and users have to download > ngrok separately? Not quite. Their npm client library is bundled with wskdebug, and this is licensed under BSD-2-Clause. When you run wskdebug you have the option to specify —ngrok on the command line which will by default use their free tier service, or you could also use their paid plans if you want to (I think). Free tier is enough for wskdebug though. Cheers, Alex
Re: Wskdebug, does it work in a docker image?
> Unfortunately wskdebug assumes I can contact the debugging server in
> localhost:9229. This is the case if I am running wskdebug OUTSIDE docker but
> not if I am running INSIDE.
wskdebug needs to be able to run docker containers. If you are inside a
container, you might be able to solve this using
docker run -v /var/run/docker.sock:/var/run/docker.sock ...
when you run the outer docker container. That creates a loopback to the docker
daemon on the host. I am not sure if that would solve any port visibility
issues automatically, you might still have to expose them first.
> Also I have another use case where I have to run it: a production with
> kubernetes cluster with actions. Some actions are using redis, kafka and
> buckets. Unfortunately the debugger runs the action in the local docker, and
> the local action cannot reach the services inside the cluster.
That sounds like a very special Openwhisk environment?
[1] https://stackoverflow.com/a/33003273/2709
Cheers,
Alex
From: Michele Sciabarra
Sent: Thursday, February 20, 2020 09:56
To: dev@openwhisk.apache.org
Subject: Re: Wskdebug, does it work in a docker image?
I reply to myself to say that I solved this problem (it is actually mentioned
in the documentation) with a chown of /usr/lib/node_modules and /usr/bin. So I
was able to install wskdebug.
However wskdebug in current shape does not work in my two use cases.
One use case is the one I mentioned: I am running an editor with theia in a
docker image, so I installed it inside a docker image.
Unfortunately wskdebug assumes I can contact the debugging server in
localhost:9229. This is the case if I am running wskdebug OUTSIDE docker but
not if I am running INSIDE.
Also I have another use case where I have to run it: a production with
kubernetes cluster with actions. Some actions are using redis, kafka and
buckets. Unfortunately the debugger runs the action in the local docker, and
the local action cannot reach the services inside the cluster.
--
Michele Sciabarra
mich...@sciabarra.com
- Original message -
From: Michele Sciabarra
To: dev@openwhisk.apache.org
Subject: Wskdebug, does it work in a docker image?
Date: Wednesday, February 19, 2020 7:25 PM
Hello,
I am trying to build an openwhisk IDE, using eclipse theia as a starting point.
I already packages standalone openwhisk as a docker image, and I contributed
the effort.
Theia runs from another docker image.
I am now trying to run wskdebug in the theia docker container.
Note I am able to run "wsk" from theia and I have also docker in the image
and the docker socket mounted, so I can also do docker ps, docker create etc.
But if I try to install wskdebug in the image it fails.
You can easily replicate the issue with `docker run -ti node:10 bash` and then
run `npm install -g @adobe/wskdebug`
I see errors like:
ngrok - error storing binary to local file { [Error: EACCES: permission denied,
open
'/usr/local/lib/node_modules/@adobe/wskdebug/node_modules/ngrok/bin/aHR0cHM6Ly9iaW4uZXF1aW5veC5pby9jLzRWbUR6QTdpYUhiL25ncm9rLXN0YWJsZS1saW51eC1hbWQ2NC56aXA=.zip']
errno: -13,
code: 'EACCES',
--
Michele Sciabarra
mich...@sciabarra.com
Re: [VOTE] Accept wskdebug contribution from Adobe
+1, thx Alex! Regards, Cosmin On 2/20/20, 6:37 AM, "David P Grove" wrote: This is a call to vote to accept the donation of the wskdebug code base from Adobe as discussed in [1]. This majority vote will remain open for at least 72 hours. The IP clearance form [2] has been filed and I will initiate an IPMC IP clearance vote shortly (in parallel with this vote). (Note that there appears to be a lag in rebuilding the html version of the clearance at [2]; consult the .xml file in svn [3] if you want to see the latest) If the vote is successful, we will create a new git repo, openwhisk-wskdebug, to contain the donated code to allow the OpenWhisk community to continue its development. --dave [1] https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread.html%2F3cb01abdf0a6a0f2d577d08ed687ab0c06918b7ce958a27b0654b145%2540%253Cdev.openwhisk.apache.org%253E&data=02%7C01%7Cstanciu%40adobe.com%7Ccebbb889828748d280ab08d7b6125d6a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637178062309522291&sdata=L0P%2FxAfMh%2BuzZzH9SuHOUIT%2BF%2BrvQEF0qo%2Bwonhpwx8%3D&reserved=0 [2] https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fincubator.apache.org%2Fip-clearance%2Fopenwhisk-wskdebug.html&data=02%7C01%7Cstanciu%40adobe.com%7Ccebbb889828748d280ab08d7b6125d6a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637178062309532293&sdata=EIxDGYdOKsOekHQYhltZZATwXLvfiCk3DCWCZnDYdhk%3D&reserved=0 [3] https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsvn.apache.org%2Frepos%2Fasf%2Fincubator%2Fpublic%2Ftrunk%2Fcontent%2Fip-clearance%2Fopenwhisk-wskdebug.xml&data=02%7C01%7Cstanciu%40adobe.com%7Ccebbb889828748d280ab08d7b6125d6a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637178062309532293&sdata=yXZ4G1LFd7IHNj8geJwPxTAcT5J8%2BzKUWBoLmBcyTcQ%3D&reserved=0
Re: [VOTE] Accept wskdebug contribution from Adobe
+1 to accept wskdebug contribution. On Fri, Feb 21, 2020 at 3:58 PM Dave Grove wrote: > +1 to accept wskdebug contribution. > > --dave > > On 2020/02/20 14:36:49, "David P Grove" wrote: > > > > > > This is a call to vote to accept the donation of the wskdebug code base > > from Adobe as discussed in [1]. This majority vote will remain open for > at > > least 72 hours. > > > > The IP clearance form [2] has been filed and I will initiate an IPMC IP > > clearance vote shortly (in parallel with this vote). (Note that there > > appears to be a lag in rebuilding the html version of the clearance at > [2]; > > consult the .xml file in svn [3] if you want to see the latest) > > > > If the vote is successful, we will create a new git repo, > > openwhisk-wskdebug, to contain the donated code to allow the OpenWhisk > > community to continue its development. > > > > --dave > > > > [1] > > > https://lists.apache.org/thread.html/3cb01abdf0a6a0f2d577d08ed687ab0c06918b7ce958a27b0654b145%40%3Cdev.openwhisk.apache.org%3E > > [2] https://incubator.apache.org/ip-clearance/openwhisk-wskdebug.html > > [3] > > > https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/openwhisk-wskdebug.xml > > >
Re: [VOTE] Accept wskdebug contribution from Adobe
+1 to accept wskdebug contribution. --dave On 2020/02/20 14:36:49, "David P Grove" wrote: > > > This is a call to vote to accept the donation of the wskdebug code base > from Adobe as discussed in [1]. This majority vote will remain open for at > least 72 hours. > > The IP clearance form [2] has been filed and I will initiate an IPMC IP > clearance vote shortly (in parallel with this vote). (Note that there > appears to be a lag in rebuilding the html version of the clearance at [2]; > consult the .xml file in svn [3] if you want to see the latest) > > If the vote is successful, we will create a new git repo, > openwhisk-wskdebug, to contain the donated code to allow the OpenWhisk > community to continue its development. > > --dave > > [1] > https://lists.apache.org/thread.html/3cb01abdf0a6a0f2d577d08ed687ab0c06918b7ce958a27b0654b145%40%3Cdev.openwhisk.apache.org%3E > [2] https://incubator.apache.org/ip-clearance/openwhisk-wskdebug.html > [3] > https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/openwhisk-wskdebug.xml >
Re: [VOTE] Accept wskdebug contribution from Adobe
Big +1 too ! On Fri, Feb 21, 2020 at 8:28 AM Rob Allen wrote: > +1 > > Thanks Adobe team. > > Regards, > > Rob > > > On 20 Feb 2020, at 17:35, David P Grove wrote: > > > > > > > > This is a call to vote to accept the donation of the wskdebug code base > > from Adobe as discussed in [1]. This majority vote will remain open for > at > > least 72 hours. > > > > The IP clearance form [2] has been filed and I will initiate an IPMC IP > > clearance vote shortly (in parallel with this vote). (Note that there > > appears to be a lag in rebuilding the html version of the clearance at > [2]; > > consult the .xml file in svn [3] if you want to see the latest) > > > > If the vote is successful, we will create a new git repo, > > openwhisk-wskdebug, to contain the donated code to allow the OpenWhisk > > community to continue its development. > > > > --dave > > > > [1] > > > https://lists.apache.org/thread.html/3cb01abdf0a6a0f2d577d08ed687ab0c06918b7ce958a27b0654b145%40%3Cdev.openwhisk.apache.org%3E > > [2] https://incubator.apache.org/ip-clearance/openwhisk-wskdebug.html > > [3] > > > https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/openwhisk-wskdebug.xml > >
Re: [VOTE] Accept wskdebug contribution from Adobe
+1 Thanks Adobe team. Regards, Rob > On 20 Feb 2020, at 17:35, David P Grove wrote: > > > > This is a call to vote to accept the donation of the wskdebug code base > from Adobe as discussed in [1]. This majority vote will remain open for at > least 72 hours. > > The IP clearance form [2] has been filed and I will initiate an IPMC IP > clearance vote shortly (in parallel with this vote). (Note that there > appears to be a lag in rebuilding the html version of the clearance at [2]; > consult the .xml file in svn [3] if you want to see the latest) > > If the vote is successful, we will create a new git repo, > openwhisk-wskdebug, to contain the donated code to allow the OpenWhisk > community to continue its development. > > --dave > > [1] > https://lists.apache.org/thread.html/3cb01abdf0a6a0f2d577d08ed687ab0c06918b7ce958a27b0654b145%40%3Cdev.openwhisk.apache.org%3E > [2] https://incubator.apache.org/ip-clearance/openwhisk-wskdebug.html > [3] > https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/openwhisk-wskdebug.xml
[slack-digest] [2020-02-20] #general
2020-02-20 00:06:34 UTC - Rodric Rabbah: per invoker, there is a config setting
for max memory
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1582157194098800?thread_ts=1582155347.097500&cid=C3TPCAQG1
2020-02-20 00:06:49 UTC - Rodric Rabbah: ```val poolConfig: ContainerPoolConfig
= loadConfigOrThrow[ContainerPoolConfig](ConfigKeys.containerPool)```
it’s loaded at invoker startup time ^
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1582157209099000?thread_ts=1582155347.097500&cid=C3TPCAQG1
2020-02-20 00:07:09 UTC - Rodric Rabbah: ```case class
ContainerPoolConfig(userMemory: ByteSize, concurrentPeekFactor: Double,
akkaClient: Boolean) {```
the param is `user-memory`
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1582157229099200?thread_ts=1582155347.097500&cid=C3TPCAQG1
2020-02-20 00:07:45 UTC - Rodric Rabbah: this is a max, so to have an exact
value requires changing this configuration, possibly to accept a list of
allowed sizes in lieu of a max
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1582157265099400?thread_ts=1582155347.097500&cid=C3TPCAQG1
2020-02-20 00:09:37 UTC - Kostis Kaffes: Thanks a lot!
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1582157377099600?thread_ts=1582155347.097500&cid=C3TPCAQG1
2020-02-20 02:02:00 UTC - Dominic Kim: Anyone, please upload the record of the
community call yesterday :pray:
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1582164120100500?thread_ts=1582164120.100500&cid=C3TPCAQG1
2020-02-20 05:28:32 UTC - Anuradha Natarajan: Thanks! after overriding the
action timeout using wsk update, it worked
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1582176512100900?thread_ts=1582105981.086300&cid=C3TPCAQG1
2020-02-20 05:42:46 UTC - Pranay: Thanks
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1582177366101100?thread_ts=1582007444.062700&cid=C3TPCAQG1
2020-02-20 05:47:58 UTC - Anuradha Natarajan: Is there a way to review the
output of an action getting executed by the invoker at runtime? will 'docker
logs --follow' help? in understanding what is happening
at runtime
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1582177678103000?thread_ts=1582177678.103000&cid=C3TPCAQG1
2020-02-20 07:07:30 UTC - Nikhil Achaya: you can try `wsk activation poll`
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1582182450103100?thread_ts=1582177678.103000&cid=C3TPCAQG1
2020-02-20 09:46:07 UTC - Rodric Rabbah: you want to see the logs while the
action is running? You can try docker logs if you have access to the node where
the action is running.
wsk activation poll will show you the logs when the action has finished.
The logs aren’t currently streamed.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1582191967105100?thread_ts=1582177678.103000&cid=C3TPCAQG1
2020-02-20 14:18:20 UTC - Justin Halsall: We couldn't record it unfortunately
@Dominic Kim, we will share the slides sometime soon I believe. Sorry about
that!
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1582208300105300?thread_ts=1582164120.100500&cid=C3TPCAQG1
