2019-07-02 06:59:21 UTC - Rob Allen: Dunno if anyone is able to point Allan at
some useful docs?
<https://twitter.com/allanmacgregor/status/1145837326276464642> at
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562050761118300?thread_ts=1562050761.118300&cid=C3TPCAQG1
----
2019-07-02 07:01:56 UTC - chetanm: May be standalone mode would be useful here.
Commented on the thread
+1 : Rob Allen, Dominic Kim
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562050916118500?thread_ts=1562050761.118300&cid=C3TPCAQG1
----
2019-07-02 07:26:12 UTC - Dominic Kim: Are you guys aware that we can trace all
OW invocation with
Pinpoint(<https://github.com/naver/pinpoint/tree/master/plugins/openwhisk>)?
My team recently contributed the OpenWhisk plugin and Akka-http plugin to the
project.
+1 : keonhee Kim, Jiang PengCheng, chetanm, Rodric Rabbah
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562052372120500
----
2019-07-02 07:26:27 UTC - Dominic Kim: You guys can get something similar to
this:
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562052387120900
----
2019-07-02 07:26:45 UTC - Dominic Kim:
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562052405121000
----
2019-07-02 07:28:26 UTC - Dominic Kim: I took screenshots from my in-house
version and please bear with some blurred parts and differences in the server
map.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562052506122900
----
2019-07-02 07:28:58 UTC - Dominic Kim: But you can setup the same thing with
the current upstream master and Pinpoint.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562052538123500
----
2019-07-02 08:00:02 UTC - James Thomas: wow neat!
grinning : Dominic Kim
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562054402124100
----
2019-07-02 08:00:11 UTC - James Thomas: you should blog about that @Dominic Kim
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562054411124400
----
2019-07-02 08:00:12 UTC - James Thomas: :slightly_smiling_face:
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562054412124600
----
2019-07-02 09:13:03 UTC - Dominic Kim: @James Thomas Thanks
:slightly_smiling_face: Do you mean blogging to OpenWhisk blog? or a personal
blog?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562058783125800
----
2019-07-02 09:14:33 UTC - Dominic Kim: I think I can ask the one who mainly did
it to blog it. : )
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562058873126500
----
2019-07-02 09:19:50 UTC - James Thomas: if you publish on medium - we can put
it on the OW blog?
white_check_mark : Dominic Kim
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562059190126800
----
2019-07-02 09:20:05 UTC - Dominic Kim: got it.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562059205127100
----
2019-07-02 13:36:19 UTC - Michael Schmidt: Hi I am attempting to use the
serverless libraries with OpenWhisk. I have successfully tried out the nodejs
I have a bug to report with the python2 (let me know where the best place for
this is):
```
serverless create --template openwhisk-python --path pyhton-test
#creates project successfully, but then when you try to deploy you get the
following error
```
```
serverless deploy -v
Serverless: Packaging service...
Serverless: Excluding development dependencies...
Serverless: Compiling Functions...
Serverless: Compiled Function (tryme):
{"actionName":"pyhton-test-dev-tryme","overwrite":true,"action":{"exec":{"main":"tryme","kind":"python","code":"<hidden>"},"limits":{"timeout":60000,"memory":256,"concurrency":1},"parameters":[],"annotations":[]}}
Serverless: Compiling Packages...
Serverless: Compiling API Gateway definitions...
Serverless: Compiling Rules...
Serverless: Compiling Triggers & Feeds...
Serverless: Compiling Service Bindings...
Serverless: Deploying Functions...
Serverless: Deploying Function: pyhton-test-dev-tryme
Serverless Error ---------------------------------------
Failed to deploy function (pyhton-test-dev-tryme) due to error: PUT
<https://10.113.78.22:31001/api/v1/namespaces/_/actions/pyhton-test-dev-tryme?overwrite=true>
Returned HTTP 400 (Bad Request) --> "The request content was malformed:
kind 'python' not in Set(dotnet:2.2, go:1.11, nodejs:10, ballerina:0.990,
ruby:2.5, nodejs:8, blackbox, java, swift:4.2, sequence, nodejs:6, nodejs:12,
python:3, python:2, php:7.3)"
Get Support --------------------------------------------
Docs: <http://docs.serverless.com|docs.serverless.com>
Bugs:
<http://github.com/serverless/serverless/issues|github.com/serverless/serverless/issues>
Issues: <http://forum.serverless.com|forum.serverless.com>
Your Environment Information ---------------------------
OS: linux
Node Version: 6.17.1
Serverless Version: 1.46.1
```
After editing the serverless yaml to python:2 things worked just fine
I am now having trouble with setting up python3 via the same method, but then
obviously changing the python 2 code over to python 3. So I am looking to
verify that python 3 is actually supported.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562074579130100
----
2019-07-02 13:41:31 UTC - Rodric Rabbah: You can use kind “python:2” or
python:3 or python:default
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562074891131000
----
2019-07-02 13:42:36 UTC - Rodric Rabbah: The naked python is not a recognized
kind. It’s not a bug. We could make unqualified types use :default I suppose.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562074956132000
----
2019-07-02 13:44:32 UTC - Rodric Rabbah: Python 3 is available and the primary
change for your code is making sure it works with python 3 vs 2. The rest in
terms of the runtime is the same in OpenWhisk.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562075072134100
----
2019-07-02 13:44:56 UTC - Michael Schmidt: I mean, it doesn't really matter to
me, but if you user the serverless create template it may just be less
confusing if the templates were python:2 python:3 or python:default
+1 : Rodric Rabbah, James Thomas
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562075096134600
----
2019-07-02 13:45:37 UTC - Michael Schmidt: okay got it, yeah there could be an
issue with my python 3 code... I will look at it a little more
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562075137135100
----
2019-07-02 13:45:46 UTC - Michael Schmidt: I just wanted to verify that I
wasn't chasing ghosts
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562075146135400
----
2019-07-02 13:46:40 UTC - Rodric Rabbah: @James Thomas ^^
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562075200136000
----
2019-07-02 13:48:24 UTC - Dave Grove: looking at that list of kinds, should we
be changing `java` to `java:8` for consistency with every other language?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562075304137300?thread_ts=1562075304.137300&cid=C3TPCAQG1
----
2019-07-02 13:48:52 UTC - Rodric Rabbah: Yes. There is a Pr for that open I
think
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562075332137800
----
2019-07-02 13:52:18 UTC - Rodric Rabbah:
<https://github.com/apache/incubator-openwhisk/pull/4390>
Ill finish it off
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562075538138900
----
2019-07-02 14:17:26 UTC - Michael Schmidt: Another question as I am looking at
openwhisk. So this seems very cool and very robust, but I am curious how it
works.
So my only other limited experience is with kubeless, in that framework when
you deploy a function it deploys as a container. Does it work the same way with
openwhisk? How do I track my various deployed serverless functions/how many
there are, how does openwhisk handle scaling?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562077046141100
----
2019-07-02 14:18:34 UTC - Michael Schmidt: If deploying an openwhisk platform
on my own hardware, should I be pre planning space to be allocated for my
serverless workloads?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562077114141900
----
2019-07-02 14:18:55 UTC - Michael Schmidt: via kubernetes/helm variables
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562077135142300
----
2019-07-02 14:19:20 UTC - Rodric Rabbah:
<https://github.com/apache/incubator-openwhisk/blob/master/docs/about.md>
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562077160142500
----
2019-07-02 14:19:54 UTC - Rodric Rabbah: provides an overview of how actions
run on the platforms (this is derived from a couple of medium blogs from
@Markus Thömmes that are also a good reference)
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562077194143200
----
2019-07-02 14:20:35 UTC - Rodric Rabbah: tl;dr actions run in containers,
openwhisk doesn’t expose the underlying platform at all, you get logs,
activation data, etc through the wsk cli or openwhisk api
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562077235144100
----
2019-07-02 14:25:22 UTC - Michael Schmidt: So first off, yay I got the python 3
stuff to run, I was just being silly about renaming the python function, but
then forgetting to set configuration correctly in serverless.yml
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562077522145400
----
2019-07-02 14:25:44 UTC - Michael Schmidt: But okay if the actions run in
containers, where do those containers live in my K8s cluster?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562077544145900
----
2019-07-02 14:26:11 UTC - Michael Schmidt: openwhisk in this case is installed
in the default namespace
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562077571146200
----
2019-07-02 16:06:34 UTC - James Thomas: @Michael Schmidt Opened an issue for
that bug you found:
<https://github.com/serverless/serverless-openwhisk/issues/178>
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562083594146700
----
2019-07-02 16:07:38 UTC - Michael Schmidt: @James Thomas Thanks! In the future
is it helpful for me to put in issues there? Or just let you all know here and
then you all can decide whether to pull it in or not?
+1 : James Thomas
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562083658147500
----
2019-07-02 16:07:52 UTC - James Thomas: yeah - please file issues in that repo
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562083672147800
----
2019-07-02 16:08:06 UTC - James Thomas: no guarantees when I’ll fix them but
need to track everything for the next release
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562083686148200
----
2019-07-02 16:09:56 UTC - Michael Schmidt: So now that I know what the work
around is (i can put it in the issue) I wouldn't call this a major bug
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562083796148700
----
2019-07-02 16:11:45 UTC - Michael Schmidt: There now the googlers of the world
can find their answers :slightly_smiling_face:
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562083905149100
----
2019-07-02 16:12:12 UTC - Michael Schmidt: Don't worry I am helping because I
have lots of questions, but I am happy to update docs as I go along.
+1 : James Thomas, Rodric Rabbah
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562083932149700
----
2019-07-02 16:58:11 UTC - Michael Schmidt: So for helm, there is a comment in
the values file that says to look at the docs folder for details about ingress.
I can't find anything about it but maybe someone can tell me why this isn't
exposing openwhisk over http and is only working over https:
```
ingress:
apiHostName: "ip-thing"
apiHostPort: 31001
apiHostProto: "http"
type: NodePort
annotations:
domain: "ip-thing"
tls:
enabled: false
secretenabled: true
createsecret: true
secretname: "ow-ingress-tls-secret"
secrettype: "tls"
```
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562086691151600
----
2019-07-02 17:00:06 UTC - Michael Schmidt: Maybe this section?
```
# Nginx configurations
nginx:
imageName: "nginx"
imageTag: "1.15"
imagePullPolicy: "IfNotPresent"
replicaCount: 1
restartPolicy: "Always"
httpPort: 80
httpsPort: 443
httpsNodePort: 31001
```
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562086806152000
----
2019-07-02 17:16:53 UTC - Dave Grove: @Michael Schmidt For your earlier
question about where containers live in a k8s cluster, it depends on which impl
of the ContainerFactory SPI you chose to use. The defaults are setup to bypass
Kubernetes for the user action containers and schedule directly via Docker on
worker nodes with the label `openwhisk-role=invoker`
(`DockerContainerFactory`). There is a an option to not bypass Kubernetes
using the `KubdernetesContainerFactory`, in this case the pods for the action
containers will be created in the same namespace as the rest of the OpenWhisk
pods. More details at
<https://github.com/apache/incubator-openwhisk-deploy-kube/blob/master/docs/configurationChoices.md#invoker-container-factory>
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562087813156600
----
2019-07-02 17:18:24 UTC - Dave Grove: For ingress, the documentation was
reorganized to group by Kubernetes platform each of the `docs/k8s-*.md` files
will have sometihng about ingress.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562087904158200
----
2019-07-02 17:18:31 UTC - Michael Schmidt: @Dave Grove That is awesome! Perfect
answer and exactly what I was looking for!
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562087911158500
----
2019-07-02 17:18:43 UTC - Rodric Rabbah: any of this worth replicating on the
dev list?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562087923158900
----
2019-07-02 17:19:39 UTC - Michael Schmidt: Yeah @Dave Grove for our tracking
and compliance we are suppose to run everything atop the k8s cluster. Else we
have the use wsk to show what functions are running at any given time
:slightly_smiling_face:
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562087979160700
----
2019-07-02 17:20:25 UTC - Rodric Rabbah: @Michael Schmidt contributions are
welcome and appreciated especially with docs
please check out the contributions guide in the project repo
<https://github.com/apache/incubator-openwhisk/blob/master/CONTRIBUTING.md>
and lets us what you’re up to via the apache dev list
`<mailto:[email protected]|[email protected]>`
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562088025161100
----
2019-07-02 17:22:13 UTC - Michael Schmidt: If I am using a hardware k8s cluster
which md is recommended?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562088133161700
----
2019-07-02 17:24:37 UTC - Dave Grove: Good question. Maybe k8s-google.md is
closest to generic bring-your-own-hardware cluster. but we probably should
have a document just for that.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562088277163600
----
2019-07-02 17:26:24 UTC - Michael Schmidt: I think the main reason for my
confusion is that the "ingress" section isn't really meant for ingress
controllers? Openwhisk helm seems to be laid out like this with two main
sections:
```
# Nginx configurations
nginx:
imageName: "nginx"
imageTag: "1.15"
imagePullPolicy: "IfNotPresent"
replicaCount: 1
restartPolicy: "Always"
httpPort: 80
httpsPort: 443
httpsNodePort: 31001
```
```
# Ingress defines how to access OpenWhisk from outside the Kubernetes cluster.
# See docs/ingress.md for a discussion of how to provide these values.
ingress:
apiHostName: "<http://ip-blah.com|ip-blah.com>"
apiHostPort: 31001
apiHostProto: "http"
type: NodePort
annotations:
domain: "<http://ip-blah.com|ip-blah.com>"
tls:
enabled: false
secretenabled: true
createsecret: true
secretname: "ow-ingress-tls-secret"
secrettype: "tls"
```
Most helm charts with ingress controllers in them look more like this (this is
from google's minio just as an example, but they are pretty standard):
```
ingress:
tls:
- secretName: "minio-secret"
hosts:
- <http://ip-blah.com|ip-blah.com>
enabled: true
annotations:
<http://kubernetes.io/tls-acme|kubernetes.io/tls-acme>: "true"
<http://kubernetes.io/ingress.class|kubernetes.io/ingress.class>: nginx
<http://nginx.ingress.kubernetes.io/whitelist-source-range|nginx.ingress.kubernetes.io/whitelist-source-range>:
0.0.0.0/0
path: /minio
hosts:
- <http://ip-blah.com|ip-blah.com>
```
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562088384165900
----
2019-07-02 17:28:52 UTC - Michael Schmidt: so I am unsure with the
configuration at the moment, but I am continuing to play with it
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562088532167500
----
2019-07-02 17:29:31 UTC - Michael Schmidt: I will say, all things considered I
just picked openwhisk up for the first time today. and the helm stuff has come
a really long way from just two months ago
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562088571168400
----
2019-07-02 17:29:39 UTC - Michael Schmidt: its been pretty easy
:slightly_smiling_face:
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562088579168600
----
2019-07-02 17:30:25 UTC - Dave Grove: yeah. Ingress in values.yaml is an
attempt to merge together the various bits we need to know any of the
kubernetes clusters we run on, some of which don’t have real ingress
controllers in them.
I’d probably try to get NodePort working first. Something like this should
work:
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562088625169400
----
2019-07-02 17:30:54 UTC - Dave Grove:
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562088654169600
----
2019-07-02 17:32:10 UTC - Dave Grove: glad it hasn’t been too bad. Ingress is
the thing we don’t have a great handle on because every vendor does their own
extension
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562088730171000
----
2019-07-02 17:33:16 UTC - Michael Schmidt: So I had the node port working, the
problem is because the test machines I am on don't have any certificates
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562088796171800
----
2019-07-02 17:33:36 UTC - Michael Schmidt: which isn't an issue if the service
is http for testing, but I can't force it away from https
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562088816172300
----
2019-07-02 17:35:30 UTC - Michael Schmidt: which means I can't test out
deployments of web servers because I get errors like this:
```Failed to deploy API Gateway route due to error: POST
https://<ip>:31001/api/v1/web/whisk.system/apimgmt/createApi.http
Returned HTTP 502 (Bad Gateway) --> "API creation failure: Unable to
configure the API Gateway: "Invalid URI \"undefined/tenants\"""```
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562088930173600
----
2019-07-02 17:36:06 UTC - Michael Schmidt: its not THE worst, it just means I
have to wait for someone to import openwhisk software to a closed env before I
can keep testing
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562088966174500
----
2019-07-02 17:36:43 UTC - Michael Schmidt: Which is why I was just trying to
test out all the examples and then start building on them with insecure http
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562089003175200
----
2019-07-02 17:38:33 UTC - Dave Grove: @Rodric Rabbah - any thoughts about
apigateway ^
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562089113175700
----
2019-07-02 17:38:49 UTC - Rodric Rabbah: yes
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562089129176000
----
2019-07-02 17:39:18 UTC - Rodric Rabbah: add this to your `.wskprops` file
`APIGW_ACCESS_TOKEN=APIGW_ACCESS_TOKEN`
i found this on an issue for `sls`
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562089158176500
----
2019-07-02 17:39:50 UTC - Rodric Rabbah: checking if it’s the same error
message actually hang on
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562089190176900
----
2019-07-02 17:40:14 UTC - Rodric Rabbah:
<https://github.com/serverless/serverless-openwhisk/issues/103#issuecomment-503732524>
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562089214177100
----
2019-07-02 17:40:21 UTC - Rodric Rabbah: yup looks the same
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562089221177300
----
2019-07-02 17:42:07 UTC - Michael Schmidt: literally copy paste
"APIGW_ACCESS_TOKEN=APIGW_ACCESS_TOKEN" in there?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562089327177600
----
2019-07-02 17:43:12 UTC - Michael Schmidt: did not work for me, but now its a
different error:
```
Failed to deploy API Gateway route due to error: POST
<https://blah:31001/api/v1/web/whisk.system/apimgmt/createApi.http?accesstoken=APIGW_ACCESS_TOKEN&spaceguid=2yadayada8c502>
Returned HTTP 502 (Bad Gateway) --> "API creation failure: Unable to
configure the API Gateway (status code 400): {"status":400,"message":"Error:
Resource path must begin with '/'."}"
```
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562089392178400
----
2019-07-02 17:43:33 UTC - Michael Schmidt: the access token and ip are omitted
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562089413178600
----
2019-07-02 17:44:18 UTC - Michael Schmidt: and its attempting to run as
python:2 code (had to update the serverless.yml) and ignore_certs is true
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562089458179200
----
2019-07-02 17:45:13 UTC - Rodric Rabbah: ```
provider:
name: openwhisk
ignore_certs: true
# extend the framework using plugins listed here:
# <https://github.com/serverless/plugins>
plugins:
- serverless-openwhisk
- serverless-dotenv-plugin
functions:
hello:
handler: handler.hello
events:
- http:
method: GET
path: /api/greeting
resp: http
```
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562089513179400
----
2019-07-02 17:45:24 UTC - Rodric Rabbah: this is my sls yml for the sample
project
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562089524179700
----
2019-07-02 17:45:44 UTC - Michael Schmidt: what is your runtime?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562089544179900
----
2019-07-02 17:45:59 UTC - Rodric Rabbah: this is node
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562089559180300
----
2019-07-02 17:46:09 UTC - Michael Schmidt: I am attempting to use the python
http server
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562089569180700
----
2019-07-02 17:46:12 UTC - Rodric Rabbah: so dont have a kind specified
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562089572181000
----
2019-07-02 17:46:25 UTC - Michael Schmidt: simple-python-http-endpoint
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562089585181400
----
2019-07-02 17:46:58 UTC - Michael Schmidt: from the examples serverless repo, I
am not much of a python person but everyone always seems to love python
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562089618182200
----
2019-07-02 18:39:43 UTC - Michael Schmidt: @Dave Grove I typed kubenetes into
the factory instead of kubernetes and the error message was extreme lol but it
looks like I can verify that it worked! It even brought three of my serverless
functions that were origonally in docker into k8s when the new whisk fired up
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562092783183700
----
2019-07-02 18:40:10 UTC - Dave Grove: cool
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562092810183900
----
2019-07-02 18:41:47 UTC - Michael Schmidt: is there an easy place I can find a
container list for all the runtimes?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562092907185600
----
2019-07-02 18:42:00 UTC - Michael Schmidt: or should I just fire up one of each
and get the container iamges from kubectl describe?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562092920186200
----
2019-07-02 18:42:34 UTC - Michael Schmidt: oh... or are they all
openwhisk/action-nodejs-v10:ab224ab
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562092954187100
----
2019-07-02 18:43:01 UTC - Michael Schmidt: cancel all that
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562092981187500
----
2019-07-02 18:43:18 UTC - Michael Schmidt: nvm i see what is happening now...
the invokers were added to the k8s deploy..
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562092998188000
----
2019-07-02 18:43:18 UTC - Ran Ribenzaft: Hi guys! not even sure where to start
:slightly_smiling_face:
Last month I met @Lars Trieloff from Adobe, and we discussed about adding
support for OpenWhisk in Epsagon.
In short - Epsagon provides monitoring and troubleshooting solution for
distributed/serverless apps.
We are now at the point that it is supported in Node, so wanted to know if
someone is interested in learning more and be part of shaping the product.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562092998188100
----
2019-07-02 18:43:41 UTC - Ran Ribenzaft: Adding an example of tracing
action->action
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562093021188400
----
2019-07-02 18:47:33 UTC - Rodric Rabbah: that’s awesome @Ran Ribenzaft - Lars
posted a video on sunday.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562093253189100
----
2019-07-02 18:47:53 UTC - Rodric Rabbah:
<https://github.com/apache/incubator-openwhisk/pull/4390> is ready to merge
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562093273189200?thread_ts=1562075304.137300&cid=C3TPCAQG1
----
2019-07-02 18:49:48 UTC - Ran Ribenzaft: We are constantly adding support for
more and more stuff - so if anyone is interested in trying out - DM me
:slightly_smiling_face:
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562093388189900
----
2019-07-02 18:50:38 UTC - Ran Ribenzaft: (we recently added instrumentation for
`openwhisk` lib in Node, and soon we will release "actions" screen)
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562093438190600
----
2019-07-02 18:59:25 UTC - Michael Schmidt: Success with the none web server
ones in K8s!
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562093965191200
----
2019-07-02 19:20:03 UTC - Michael Schmidt: Okay so I tried out the cron one,
that one ends immediately for some reason and terminates from k8s right away.
Is that expected behavior?
```
Your cron function /guest/python_service-dev-cron ran at 19:18:13.361971
XXX_THE_END_OF_A_WHISK_ACTIVATION_XXX
XXX_THE_END_OF_A_WHISK_ACTIVATION_XXX
```
I guess it wakes up, prints a statement then goes away?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1562095203192400
----
