2019-02-21 14:17:58 UTC - Michele Sciabarra: @Satwik Kolhe hmm are you using the "hostPath"? what happens if you have for example a database, it dies, kubernetes restarts it in a different node? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550758678014900?thread_ts=1550758678.014900&cid=C3TPCAQG1 ---- 2019-02-21 14:18:27 UTC - Michele Sciabarra: hostPath is considered a workaround not a storage solution +1 : Satwik Kolhe https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550758707015500 ---- 2019-02-21 14:35:09 UTC - Satwik Kolhe: Yes using hostPath - Even I am of this belief that this isn't the correct way to deploy the cluster. Better is expose the data directory from a NFS server and mount it on all nodes.
Had to try deployment using persistent storage - thus tried it that way. I have a question regarding this - While the data is stored on local storage, when I tear-down and re-deploy openwhisk cluster using the same pvc's, will the init-containers overwrite previous data or initialize containers with old data - especially couchdb? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550759709015600?thread_ts=1550758678.014900&cid=C3TPCAQG1 ---- 2019-02-21 17:24:39 UTC - Michele Sciabarra: with hostPath you get random results https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550769879016000?thread_ts=1550758678.014900&cid=C3TPCAQG1 ---- 2019-02-21 17:24:51 UTC - Michele Sciabarra: if you are lucky you get the old dir https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550769891016200?thread_ts=1550758678.014900&cid=C3TPCAQG1 ---- 2019-02-21 17:25:08 UTC - Michele Sciabarra: otherwise you can get the dir of another host it depends where the https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550769908016400?thread_ts=1550758678.014900&cid=C3TPCAQG1 ---- 2019-02-21 17:25:20 UTC - Michele Sciabarra: schedules places the pod https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550769920016600?thread_ts=1550758678.014900&cid=C3TPCAQG1 ---- 2019-02-21 17:25:37 UTC - Michele Sciabarra: hence... use rook. It works and it is easy to deploy https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550769937016800?thread_ts=1550758678.014900&cid=C3TPCAQG1 ---- 2019-02-21 17:26:53 UTC - Michele Sciabarra: check here https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550770013017100?thread_ts=1550758678.014900&cid=C3TPCAQG1 ---- 2019-02-21 17:26:53 UTC - Michele Sciabarra: <https://github.com/learning-apache-openwhisk/chapter12-deploy/blob/8ed74275c92106f72939ca8f14013deb7a7496c2/user-data.txt#L118> +1 : Satwik Kolhe https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550770013017300?thread_ts=1550758678.014900&cid=C3TPCAQG1 ---- 2019-02-21 17:27:06 UTC - Rob Allen: hmm. I'd better do a version bump if we're gonna release the runtimes! https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550770026017700 ---- 2019-02-21 17:40:08 UTC - Rodric Rabbah: Approved the Pr @Rob Allen please merge when ready if there aren’t additional changes. @Carlos Santana <https://github.com/apache/incubator-openwhisk-runtime-php/pull/53#pullrequestreview-206444899> FYI https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550770808018900 ---- 2019-02-21 17:44:53 UTC - Rob Allen: There's a reasonable argument for removing PHP 7.1 completely too. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550771093019800 ---- 2019-02-21 17:45:33 UTC - Rob Allen: Not sure whether to do that before or after this release though. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550771133020700 ---- 2019-02-21 17:59:36 UTC - Rodric Rabbah: I already dropped 7.1 and I think 7.2 from the openwhisk runtimes manifest. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550771976021300 ---- 2019-02-21 17:59:48 UTC - Rodric Rabbah: I defer to you. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550771988021500 ---- 2019-02-21 18:50:09 UTC - Sebastian: <https://github.com/asquevedos/Resize-Image-Java-OpenWhisk> I created this image resizing function for Java. Leave me your suggestions and comments to improve it. +1 : Michele Sciabarra https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550775009021800 ---- 2019-02-21 19:18:53 UTC - Roberto Diaz: @Michele Sciabarra @Carlos Santana I have been taken a look into swift actionloop, if I have understood correctly, the build is called and you get from stdin the function name, sourcedir and outputdir. With this info, you have to compile, execute the function and just print the results. Is this correct? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550776733026800 ---- 2019-02-21 19:19:38 UTC - Michele Sciabarra: Almost https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550776778027400 ---- 2019-02-21 19:20:22 UTC - Michele Sciabarra: You have to compile an executable that reads in stdin a JSON line call the function and outputs a JSON line in file descriptor 3 https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550776822028800 ---- 2019-02-21 19:20:41 UTC - Michele Sciabarra: As fd1 and fd2 are reserved for logs https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550776841029400 ---- 2019-02-21 19:21:33 UTC - Michele Sciabarra: You do not have to worry of the http thing, init and other stuff https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550776893030400 ---- 2019-02-21 19:22:41 UTC - Roberto Diaz: And where the magic happens? I mean where is all the Rust compiler configured. I supposed that underlying should be a docker container with all the Rust stuff https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550776961032200 ---- 2019-02-21 19:22:54 UTC - Michele Sciabarra: Yup https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550776974032400 ---- 2019-02-21 19:23:40 UTC - Michele Sciabarra: The magic is that the proxy gathers things for you unzip stuff and prepare things https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550777020033600 ---- 2019-02-21 19:23:56 UTC - Michele Sciabarra: You basically write a cli app like a Unix filter https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550777036034200 ---- 2019-02-21 19:24:46 UTC - Roberto Diaz: Awesome!! Very clever stuff :100: https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550777086034700 ---- 2019-02-21 19:27:55 UTC - Roberto Diaz: So that app should be also written also right? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550777275035500 ---- 2019-02-21 19:46:10 UTC - Michele Sciabarra: I need you write the so-called epilogue https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550778370036100 ---- 2019-02-21 19:47:12 UTC - Michele Sciabarra: <https://github.com/apache/incubator-openwhisk-runtime-go/blob/master/common/gobuild.py.launcher.go> https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550778432036400 ---- 2019-02-21 19:47:19 UTC - Michele Sciabarra: if you translate in rust this thing https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550778439036700 ---- 2019-02-21 19:47:31 UTC - Michele Sciabarra: 80% of the work is done https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1550778451037100 ----
