2019-09-05 08:54:58 UTC - Sven Lange-Last: @Ahmet Uyar does your installation use runc directly to pause / resume containers? we introduced using runc for pause / resume instead of docker pause / unpause because the operation runs faster with runc. the downside of this shortcut is that you can no more use docker unpause to resume a container that was paused with runc. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1567673698041500?thread_ts=1567516313.035200&cid=C3TPCAQG1 ---- 2019-09-05 08:56:28 UTC - Sven Lange-Last: following setting determines whether you use runc or not: <https://github.com/apache/openwhisk/blob/8d2aeabf56667a9dec49690da1cd63f64eb217ee/core/invoker/src/main/resources/application.conf#L49-L52> https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1567673788041700?thread_ts=1567516313.035200&cid=C3TPCAQG1 ---- 2019-09-05 08:57:41 UTC - Sven Lange-Last: if you deploy via ansible, following setting overrides the application.conf: <https://github.com/apache/openwhisk/blob/master/ansible/roles/invoker/tasks/deploy.yml#L252> https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1567673861041900?thread_ts=1567516313.035200&cid=C3TPCAQG1 ---- 2019-09-05 08:58:11 UTC - Sven Lange-Last: also see here: <https://github.com/apache/openwhisk/blob/master/ansible/group_vars/all#L195-L196> https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1567673891042100?thread_ts=1567516313.035200&cid=C3TPCAQG1 ---- 2019-09-05 09:00:46 UTC - Ahmet Uyar: i see in invoker logs file entries such as: [RuncClient] running /usr/bin/docker-runc resume 57d99f0d186f9af832b27ef1d06662fa39cf9ffe03ce0fffb5932d5786e23c7a (timeout: 10 seconds) [marker:invoker_runc.resume_start:10375074] https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1567674046042300?thread_ts=1567516313.035200&cid=C3TPCAQG1 ---- 2019-09-05 09:01:07 UTC - Ahmet Uyar: so I thought it is using docker-runc https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1567674067042500?thread_ts=1567516313.035200&cid=C3TPCAQG1 ---- 2019-09-05 09:04:44 UTC - Ahmet Uyar: group_vars/all has the entries: # Specify if it should use docker-runc or docker to pause/unpause containers useRunc: "{{ invoker_use_runc | default(true) }}" runcdir: "{{ invoker_runcdir | default('/run/docker/runtime-runc/moby') }}" https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1567674284042900?thread_ts=1567516313.035200&cid=C3TPCAQG1 ---- 2019-09-05 11:23:18 UTC - Ahmet Uyar: i disabled runc from group_vars/all. Then I was able to unpause with "docker unpause <id>" and then I did exec into the container. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1567682598043100?thread_ts=1567516313.035200&cid=C3TPCAQG1 ---- 2019-09-05 19:38:22 UTC - Jesse MacFadyen: Who is going to be ApacheCon next week? I am going to be presenting a couple talks on Apache Cordova, and leading a mobile track on Thursday. Would be great to meet some OpenWhisk peeps! https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1567712302044500 ---- 2019-09-05 19:44:52 UTC - Rodric Rabbah: i know there’s at least one openwhisk talk https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1567712692044800 ---- 2019-09-05 19:47:22 UTC - Matt Sicker: has anyone seen or played with <http://cloudstate.io|cloudstate.io> yet? any collaboration or integration possible? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1567712842045400 ---- 2019-09-05 19:47:58 UTC - Matt Sicker: could even take ideas from that project. it's based on fairly similar tech https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1567712878045800 ---- 2019-09-05 20:06:16 UTC - Rodric Rabbah: i’ve seen the proposal and one of the talks guessing some of the folks here in knative land have too as there was some exchange on the knative mailing list https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1567713976046800 ---- 2019-09-05 20:06:46 UTC - Rodric Rabbah: i like the actor oriented approach, matches the openwhisk programming model https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1567714006047300 ---- 2019-09-05 20:18:57 UTC - Tyson Norris: I think it matches the openwhisk programming model, but not the openwhisk action developer (or other serverless provider) programming model - like it may be more useful to implement a serverless platform, rather than expose to developers as your serverless platform? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1567714737048500 ---- 2019-09-05 20:19:42 UTC - Tyson Norris: Like many things, it will depend on your audience https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1567714782048900 ---- 2019-09-05 20:21:44 UTC - Tyson Norris: It is sort of like “state first” in comparison to “api first” approaches, where “api first” is potentially more compatible with jamstack type of applications https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1567714904050000 ---- 2019-09-05 20:27:51 UTC - Rodric Rabbah: coming from the akka folks, it makes sense for them https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1567715271050300 ----
