I have the basic version of Slack Chat Bot working which produces the following email based on the slack history of past 24 hours. Its still in early stage and some improvements are needed like adding attachments or at least link to attachments etc.
Right now I am using gmail as the SMTP server to send emails from OpenWhisk just as a starting point. Will change it as we implement further. The source code of this application is located here: https://github.com/pritidesai/slack-chat-bot Would you like to see such email everyday one per channel? Let me know your thoughts and comments, I need them for further improvements :) Thanks in advance. Cheers Priti P.S ---------- Forwarded message ---------- From: <******@gmail.com> Date: Fri, Jul 14, 2017 at 12:18 PM Subject: OpenWhisk Slack Daily Digest - Channel #general - Jul 14th 2017 To: *****@gmail.com Thu Jul 13 2017 19:45:14 GMT+0000 (UTC) rr: <@mrutkowski> recorded it - i joined a bit late but i hope someone was also taking notes to be shared on the dev list Thu Jul 13 2017 19:46:04 GMT+0000 (UTC) akrabat: The wiki notes are quite good - reads as if it was an IRC conversation Thu Jul 13 2017 19:52:01 GMT+0000 (UTC) rr: wow nice job <@mrutkowski> Thu Jul 13 2017 20:39:51 GMT+0000 (UTC) srini.aiyar: After installing using hello in openwhisk\tools\vagrant, my openwhisk vm on virtualbox works fine till after some time (may be a reboot), wsk command line is missing. I understand that the couchdb is ephemeral, but why does wsk go away. What's the easiest way to get the openwhisk vm back to being functional? This thread has 1 replies. REPLY: Thu Jul 13 2017 20:40:36 GMT+0000 (UTC) srini.aiyar: Note that this is on a Windows laptop Thu Jul 13 2017 20:42:42 GMT+0000 (UTC) akrabat: <@srini.aiyar> I think this is related to a key file being stored in `/tmp` which is cleared out on reboot. Thu Jul 13 2017 20:43:59 GMT+0000 (UTC) akrabat: The fix that I use is `cd openwhisk; wskdev fresh` but this takes a while and there's almost certainly a better way This thread has 2 replies. REPLY: Thu Jul 13 2017 20:47:54 GMT+0000 (UTC) srini.aiyar: Thanks! It's probably better than my current workaround that creates a VM all over again running hello. However, surprising that a missing key result in wsk being deleted. REPLY: Thu Jul 13 2017 20:49:16 GMT+0000 (UTC) akrabat: Other people know more about it than me :slightly_smiling_face: That's the gist though and for all I know it may be related to the vagrant build only. Thu Jul 13 2017 20:47:54 GMT+0000 (UTC) srini.aiyar: Thu Jul 13 2017 20:58:56 GMT+0000 (UTC) mrutkowski: <@rr> Thanks! Thu Jul 13 2017 21:00:46 GMT+0000 (UTC) srini.aiyar: When I install with vagrant openwhisk with ephemeral couchdb, my virtualbox VM periodically pauses resulting in the install hanging. I need to unpause to make progress. This in on Windows. Fri Jul 14 2017 00:34:26 GMT+0000 (UTC) manishv: Hey guys, I have setup OpenWhisk on Ubuntu. I am able to use wsk cli in Ubuntu by configuring apihost and auth. But when i do same thing outside the Ubuntu, It doesn't work. can i use the cli outside the Ubuntu host? Fri Jul 14 2017 01:11:15 GMT+0000 (UTC) rr: <@manishv> clarify what you mean by doesn't work? Is your "outside" host also ubuntu? If the cli binary is not compatible you can build one that is; for mac or windows or just download from the cli repository prebuilt binaries. If you mean the API host is not reachable, then make sure that you can ping the API host on your ubuntu vm. Fri Jul 14 2017 02:01:14 GMT+0000 (UTC) manishv: Hi <@rr>, my outside host is mac, I can use the wsk cli in Ubuntu VM where Openwhisk is deployed. Fri Jul 14 2017 02:02:00 GMT+0000 (UTC) manishv: I am using the correct wsk binary for mac. Fri Jul 14 2017 02:03:56 GMT+0000 (UTC) manishv: when i ping the API host from my mac, I get request time out. Fri Jul 14 2017 02:06:15 GMT+0000 (UTC) manishv: I was able to use the wsk cli in Ubuntu VM where Openwhisk is deployed* Fri Jul 14 2017 07:11:09 GMT+0000 (UTC) rr: What host value are you using from the mac host? Fri Jul 14 2017 07:11:17 GMT+0000 (UTC) akrabat: <@manishv> you're using the IP address 192.168.33.13 from the outside? Fri Jul 14 2017 07:11:46 GMT+0000 (UTC) akrabat: notes that timing is everything… Fri Jul 14 2017 07:33:41 GMT+0000 (UTC) manishv: I am not using vagrant VM. so, I tried using 172.17.0.1 and the IP address of the Ubuntu VM where Openwhisk is deployed. Fri Jul 14 2017 07:34:37 GMT+0000 (UTC) manishv: Inside Ubuntu VM I am able to use wsk CLI by setting apihost as 172.17.0.1 Fri Jul 14 2017 07:46:20 GMT+0000 (UTC) rr: From the mac host you should point at your docker host ip instead. Or set up forwarding for the 172 network. Fri Jul 14 2017 07:50:07 GMT+0000 (UTC) akrabat: Is your Vagrant just a standard VMWare Fusion VM or similar? Fri Jul 14 2017 07:51:14 GMT+0000 (UTC) akrabat: if so, maybe you need to configure some networking thing to allow routing to 172.17.0.1 from the outside? Fri Jul 14 2017 07:57:31 GMT+0000 (UTC) manishv: Thanks <@rr>. Will try to do that. Fri Jul 14 2017 07:58:08 GMT+0000 (UTC) manishv: I am using a Virtual Machine on Vsphere <@rr> Fri Jul 14 2017 07:58:35 GMT+0000 (UTC) manishv: <@akrabat> where my Ubuntu is installed Fri Jul 14 2017 07:59:15 GMT+0000 (UTC) manishv: Thanks for your suggestion as well! Fri Jul 14 2017 07:59:58 GMT+0000 (UTC) akrabat: This is veering too close to "ops" where my knowledge is distinctly lacking :slightly_smiling_face: Fri Jul 14 2017 16:17:35 GMT+0000 (UTC) akrabat: Can I update an action that has a `--kind` that's deprecated? Fri Jul 14 2017 16:25:19 GMT+0000 (UTC) rr: to a new kind Fri Jul 14 2017 16:25:39 GMT+0000 (UTC) akrabat: no - I mean can I change the code with `wsk action update` Fri Jul 14 2017 16:25:53 GMT+0000 (UTC) rr: dont think so Fri Jul 14 2017 16:26:03 GMT+0000 (UTC) akrabat: Right. Fri Jul 14 2017 16:26:26 GMT+0000 (UTC) rr: Fri Jul 14 2017 16:27:31 GMT+0000 (UTC) akrabat: Actions created against deprecated kinds continue to be invokable though? Fri Jul 14 2017 16:28:02 GMT+0000 (UTC) akrabat: is glad that there's a comment on line 400… Fri Jul 14 2017 16:29:31 GMT+0000 (UTC) rr: may not invoke - only get and delete Fri Jul 14 2017 16:30:18 GMT+0000 (UTC) akrabat: Right Fri Jul 14 2017 16:30:31 GMT+0000 (UTC) akrabat: so deprecating a kind kills all actions using it Fri Jul 14 2017 16:31:48 GMT+0000 (UTC) rr: yes… sorry? did we break actions you’re running as a result Fri Jul 14 2017 16:32:53 GMT+0000 (UTC) akrabat: Nope. I'm thinking through handling the creation of new kinds for new language minor versions Fri Jul 14 2017 16:33:38 GMT+0000 (UTC) sjfink: Fri Jul 14 2017 16:34:30 GMT+0000 (UTC) akrabat: e.g. we created `swift:3.1.1` so we don't want anyone to create new actions for `swift3`. However, I have `swift2` actions that I don't want you to turn off without warning me, but there's no easy way to tell me this in advance of my actions just stopping working. Fri Jul 14 2017 16:34:33 GMT+0000 (UTC) sjfink: ^^ we're almost there with the docker+binary+zip features from <@rr> (pluggable kinds ..) Fri Jul 14 2017 16:35:07 GMT+0000 (UTC) sjfink: sounds like we need a deprecation warning story. This thread has 3 replies. REPLY: Fri Jul 14 2017 16:57:49 GMT+0000 (UTC) mmarth: maybe a language version container could have a state/property "deprecated"? then the OW provider could proceed as fit. Along the lines of this a way to mark containers as "do not accept new actions, but run the old ones" (cf <@akrabat> 's Swift 2 example) REPLY: Fri Jul 14 2017 17:13:28 GMT+0000 (UTC) akrabat: A language version container (is the best name for this a "kind"?) does have a deprecated property already. (e.g. ) REPLY: Fri Jul 14 2017 18:41:23 GMT+0000 (UTC) mmarth: ah great - thanks for letting me know Fri Jul 14 2017 16:35:43 GMT+0000 (UTC) rr: <@akrabat> you can continue using those actions - `wsk action update mySwift2Action --docker openwhisk/swift2action` Fri Jul 14 2017 16:35:51 GMT+0000 (UTC) akrabat: I think I'd like a grace period. No new actions, but can invoke currently registered ones. Fri Jul 14 2017 16:36:44 GMT+0000 (UTC) rr: since we are storing the images on docker hub, you can even use a previous version of the runtime - relevant to the discussion you started on dev list… caveat: i did not try what i just suggested and i think there’s a small fix we’ll need to make in the core to support historical images Fri Jul 14 2017 16:36:58 GMT+0000 (UTC) akrabat: shrugs - it's sounded easy until I started thinking about it more Fri Jul 14 2017 16:37:19 GMT+0000 (UTC) akrabat: The real problems are around the actions suddenly stopping Fri Jul 14 2017 16:37:47 GMT+0000 (UTC) rr: sure - so for ibm’s openwhisk offering, it will be announced well in advance (30 days at least) Fri Jul 14 2017 16:37:59 GMT+0000 (UTC) rr: this was done in January i think for node 4 for example Fri Jul 14 2017 16:38:00 GMT+0000 (UTC) akrabat: I have some quotations out which are for actions that run really infrequently - one day a month at most Fri Jul 14 2017 16:38:51 GMT+0000 (UTC) rr: i think in the gitub repo, you have freedom since you can just change the flag in the deployment but that doesn’t help if we delete the runtime code Fri Jul 14 2017 16:38:51 GMT+0000 (UTC) akrabat: Good notifications become required like Heroku did for the NodeJS security fix. Fri Jul 14 2017 16:40:16 GMT+0000 (UTC) akrabat: I could of course roll my own action that queried the API to find out what the current list of action kinds are and then email me if the ones I care about disappeared/were deprecated Fri Jul 14 2017 16:47:19 GMT+0000 (UTC) rr: i cant imagine that service provider don’t announce these things in advance Fri Jul 14 2017 16:47:38 GMT+0000 (UTC) rr: but of course on github we might have been sloppy on this and just deleted things early Fri Jul 14 2017 16:47:43 GMT+0000 (UTC) akrabat: Does a given deployment update the container that it uses to run the action at all? Fri Jul 14 2017 16:57:49 GMT+0000 (UTC) mmarth: Fri Jul 14 2017 17:03:11 GMT+0000 (UTC) rr: we can change the meaning of “deprecated” from can only get+delete to get+delete+activate but not update or add a new flag to mean the latter what is deprecated is controlled from a deployment manifest eg Fri Jul 14 2017 17:03:20 GMT+0000 (UTC) rr: ``` runtimesManifest: defaultImagePrefix: "openwhisk" defaultImageTag: "latest" runtimes: nodejs: - kind: "nodejs" image: name: "nodejsaction" deprecated: true ``` On 2017-06-29 11:45 (-0700), "Priti Desai" <[email protected]> wrote: > > > Hi Everyone,> > > We had an idea to ease accessibility and archive slack conversations for> > OpenWhisk developers so that they can refer back to messages they might> > have missed. I am trying to make this idea go live using OpenWhisk itself> > just like Drinking Our Own Champagne. I am working on an application to> > post slack messages to OpenWhisk dev list and would like to get your input> > on my proposal. I have collected design details on cwiki and it will be> > great if you can help me improvise it.> > > > Cheers> > Priti> > > P.S.> > https://medium.com/openwhisk/openwhisk-drinking-our-own-champagne-c29a0dd04bee> > https://cwiki.apache.org/confluence/x/-ZI7B> >
