2019-12-20 04:11:30 UTC - Ajoy Agarwal: I am new to OpenWhisk. When we deploy OpenWhisk using docker composer, we have various docker instances running for zookeeper, kafka, api gateway, contoller, invoker, minio, redis on different ports. I want to use Whisk CLI for pushing function logics to be deployed on OpenWhisk. Which container IP and port should be exposed outside to Whisk Client to talk to? In other words, to which component the Whisk CLI connects to? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1576815090023500 ---- 2019-12-20 04:23:18 UTC - Jiang PengCheng: controller, or nginx, both are ok, I think ports should be already exposed https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1576815798024700 ---- 2019-12-20 04:35:37 UTC - Ajoy Agarwal: @Jiang PengCheng should it not be API Manager first? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1576816537025300 ---- 2019-12-20 04:37:25 UTC - Rodric Rabbah: you’ll want both exposed, nginx + apigw https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1576816645025700 ---- 2019-12-20 09:30:57 UTC - Ajoy Agarwal: @Rodric Rabbah I have used "Docker Compose" option available for deployment but after installation I find that there is no container for nginx whereas when we do native deployment using Ansible, we get nginx as well. So, how which component should we expose to outside world in such case? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1576834257028100 ---- 2019-12-20 11:54:33 UTC - Rodric Rabbah: For compose there’s just one nginx it does apigw and proxy to controller https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1576842873028700 ---- 2019-12-20 13:20:18 UTC - Rodric Rabbah: warning - some more issue triage ongoing https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1576848018029200 ---- 2019-12-20 14:00:59 UTC - Anant: Hi all. I am new to OpenWhisk. I was looking at the documentation, and the ease of deployments using Whisk manifest yamls is really appealing. Could anyone share any Python example which uses yamls for deployment? Also, how do I control cluster resources while using the manifests (like memory and CPU)? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1576850459031100 ---- 2019-12-20 14:06:04 UTC - Rodric Rabbah: hi Anant and welcome to the openwhisk community. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1576850764031500 ---- 2019-12-20 14:06:25 UTC - Rodric Rabbah: Are you referring to `wskdeploy`? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1576850785032000 ---- 2019-12-20 14:06:39 UTC - Anant: Hello @Rodric Rabbah So I figured out the second part of the question of mine from here - <https://github.com/apache/openwhisk-wskdeploy/blob/master/specification/html/spec_actions.md#valid-limit-keys>. Yes, my question was about wskdeploy. +1 : Rodric Rabbah https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1576850799032300 ---- 2019-12-20 14:06:58 UTC - Anant: Any examples for using wskdeploy with dependencies /requirements.txt would be really helpful for me. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1576850818033000 ---- 2019-12-20 14:08:14 UTC - Rodric Rabbah: @Matt Rutkowski or others might have some references ^^ (I don’t know myself, sorry.) https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1576850894034500 ---- 2019-12-20 14:10:09 UTC - Anant: sure. I must say this seems a really neat approach for serverless deployments, especially when it comes to handling large code bases for production scenarios. I'll also search in the meanwhile if I can get something. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1576851009036300 ---- 2019-12-20 16:45:48 UTC - Bilal: @Anant Hey, I'm also new to openwhisk and have been messing around with creating manifests and deploying them. A few things you might find useful. <https://github.com/apache/openwhisk-package-deploy> Basically this can deploy from gitHub repos as an action. I haven't used it myself as I'm using a different flavor of git repo and I have a slightly different use case. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1576860348038200 ---- 2019-12-20 16:47:53 UTC - Bilal: The package-deploy above takes in <https://hub.docker.com/r/openwhisk/wskdeploy> this image and is how it calls `wskdeploy` from within the action. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1576860473039500 ---- 2019-12-20 16:49:30 UTC - Bilal: For my use case I've written a _very_ simple manifest creator in python. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1576860570040500 ----
