Remove SDK commands from CLI?

[James Thomas]

Does anyone have any objections to removing the "SDK" command from the wsk
cli?

I came across this "feature" again recently due to a user running into
issues trying to use docker support in the platform. I've recently been
updating the docs on the docker actions and think we should remove this
command as it doesn't represent best practice for the platform anymore.

The SDK was an old solution to utilising custom runtime images in the
beginning of the project, before the docker support improved a lot. The
"SDKs" are a series of old tar files download from the external source
repository. Looking at the Docker SDK, it does not represent a sensible
approach to using binaries on the platform now we have the dockerskeleton
image. I didn't investigate the Swift SDK and wouldn't be sure if this even
works anymore

I've never come across an external developer using these SDKs "in the wild"
and can't see a valid use-case for continuing to provide them given all the
changes in the platform since they were introduced.

Does anyone have any comments? If not, I'll open a PR in the CLI to start
removing them.
-- 
Regards,
James Thomas

Move default Node.js runtime to v10?

[James Thomas]

On Wednesday's community call I asked about moving the default Nodejs
version in the project to v10.

Node.js 6 (which is the current default version) reaches  "end of life" on
April 30th according to https://github.com/nodejs/Release. Node.js 10 is
the current LTS version and is supported until April 2021.

Rodric mentioned this was started previously but ran into issues with the
providers?
https://github.com/apache/incubator-openwhisk/issues/4265

Does anyone have any issues with going forward with this work (once any
issues have been resolved)? I see there is some work going on to fix the
failures (https://github.com/apache/incubator-openwhisk/pull/4450)

-- 
Regards,
James Thomas

Re: 2019-04-17 OW Tech. Int. Notes + Video posted

[Rodric Rabbah]

> Could you share what should I know in advance to host the meeting or link
me to the proper guides?

Here's what I've done:
- on Monday before the call:
  1. go through the PRs that are open or recently closed and pick ones to
highlight on the call
  2. send out a call for topics via email to the dev list, and optionally
include an agenda at your discretion

- the night before the call:
  1. assemble the final agenda
  2. if warranted, put together a small number of slides that correspond to
the agenda and any other topics you as the moderator wish to cover

- moderating the call itself:
  0. Matt records the call on your cue and also takes notes which end up on
the wiki
  1. allow newcomers to say hello and introduce themselves
  2. show the agenda and moderate hand off from one speaker to the next
  3. time permitting, solicit new topics that participants want to raise
  4. call for a volunteer to run the next community call

-r

[GitHub] [incubator-openwhisk-pluggable-provider] jthomas opened a new issue #1: Provider should be installable using Helm

[GitBox]

jthomas opened a new issue #1: Provider should be installable using Helm 
URL: https://github.com/apache/incubator-openwhisk-pluggable-provider/issues/1
 
 
   Follow same approach to other project components and allow providers to be 
installed with Helm charts.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Re: Write down some documents which describe OW internals

[Bertrand Delacretaz]

Hi,

On Thu, Apr 18, 2019 at 10:44 AM Dominic Kim  wrote:
> ...Initially, I`ve naively thought of two options.
> 1. Including docs in core repo.
> 2. Including docs in cwiki or wiki in core repo. ...

To me a third option is blog posts, which have the advantage that they
don't need to be maintained: they express your current view, which
might still be valuable later even if it gets out of sync when things
evolve. OpenWhisk can get a blog at https://blogs.apache.org/ if
desired, or a blog section might be created at
http://openwhisk.apache.org/ for more informal content than what's
there now.

Apart from that, consolidating docs is great, of course - I just
wanted to mention the difference between reference docs and
informative articles which are also useful.

-Bertrand

Re: Write down some documents which describe OW internals

[Dominic Kim]

Initially, I`ve naively thought of two options.
1. Including docs in core repo.
2. Including docs in cwiki or wiki in core repo.

With the first option, new people will be able to easily find the documents
and we can guarantee the freshness of the documents as it resides in core
repo.
(It will urge contributors to update the document as the architecture
changes over time.)

With the second option, we can write down the document in cwiki or wiki and
link it in the core repo.
The document can easily become stale as contributors can overlook it when
making a change on OW internals.

But as you mentioned, it would be better to host the documents on the
website.
Aside from it, I feel like documents in OpneWhisk is somewhat scattered.
We have some documents on the websites and some documents in core repo
written in markdown, some documents in cwiki or wiki in core repo.

I didn't look into it deeply, but it seems our website is maintained in the
different project and being rendered via Jekyll. (
https://github.com/apache/incubator-openwhisk-website)
I want to raise a discussion to consolidate them into one.

In Apache Kafka, it seems they are maintaining HTML files in the core repo
and hosting documents and their website via those files.
https://github.com/apache/kafka/tree/trunk/docs

I don't want to say we need to follow their rules, but it was easy for me
to look into their documents as all information is provided in one place.

In short, I want to suggest to consolidate all docs and serve them on the
websites.
It is optional, but if we include such docs in the core repo, it would be
useful to keep them updated.


I  want to listen to any opinion or feedbacks.

Best regards
Dominic



2019년 4월 18일 (목) 오전 4:08, Matt Rutkowski 님이 작성:

> That would be a very welcome addition to our docs. indeed.  Please let me
> know if you have any ideas about how we might expose (cross-ref.) the
> resultant info better via our website or confluence wiki would be happy to
> help there.
>
>
>
> From:   Dominic Kim 
> To: dev@openwhisk.apache.org
> Date:   04/16/2019 05:29 AM
> Subject:Write down some documents which describe OW internals
>
>
>
> Dear whiskers.
>
> When I started to involve in this project, I felt the learning curve of
> OpenWhisk is relatively steep.
> It has many components, flows, edge cases and the fundamental difficulties
> coming from Scala.
>
> So how about writing down some documents about OpenWhisk internals?
> I am thinking of writing down documents which explain basic architectures
> of each component, how activations flow the system, how entities are
> managed, and so on.
> There is a possibility that the documents could be stale in the future as
> the system is quickly changing, however, it would be a good starting point
> to help more people get involved in the project.
>
>
> Best regards
> Dominic
>
>
>
>
>

Re: 2019-04-17 OW Tech. Int. Notes + Video posted

[Dominic Kim]

Thank you, Matt, for sharing this useful information.

Could you share what should I know in advance to host the meeting or link
me to the proper guides?

Best regards
Dominic

2019년 4월 18일 (목) 오전 2:03, Matt Rutkowski 님이 작성:

> Thanks Rodric for hosting and Dominic for being the next volunteer for the
> May 1st meeting.
>
> CWiki:
>
> https://cwiki.apache.org/confluence/display/OPENWHISK/2019-04-17+OW+Tech+Int.+Meeting+Notes
>
> YouTube: https://www.youtube.com/watch?v=ngWTBp9VPJY
>
> Some topics from agenda:
>
> * NodeJS for Knative (119) (NodeJS): Support
> *
> https://github.com/apache/incubator-openwhisk-runtime-nodejs/pull/119
> * Docker Upgrade (4430) (OW Core): Docker 18 upgrade: Dominic leading this
> PR
> * https://github.com/apache/incubator-openwhisk/pull/4430
> * Invoker for Lambda (4412): AWS lambda: Chetan at Adobe OW actions with
> AWS lambda
> * https://github.com/apache/incubator-openwhisk/pull/4412
> * New LB Proposal: Dominic proposal on Wiki/dev list posted, redo.
> LoadBalancer, working with Dragos
> *
>
> https://cwiki.apache.org/confluence/display/OPENWHISK/New+architecture+proposal
>
> * Node6 Runtime (deprecation): James: version 6 out of LTS should we
> deprecate officially?
> * User Doc updates: James: plans to update docs. with some commonly asked
> questions (provide answers)
> * Tech. Int. call future: Rodric: evaluate value/length of interchange
> calls
> * Kubernetes/Knative:
> * Please see WIki proposal from Dragos suggesting how we preserve OW
> models/control/data/mgmt. planes on Kube.
> *
>
> https://cwiki.apache.org/confluence/display/OPENWHISK/OpenWhisk+on+Kubernetes
>
>
> Cheers,
> Matt
>
>

[slack-digest] [2019-04-17] #wskdeploy

[OpenWhisk Team Slack]

2019-04-17 15:02:53 UTC - Matt Rutkowski: @Dominic Kim will look at asap
https://openwhisk-team.slack.com/archives/C79ALSWJJ/p113373002000

[slack-digest] [2019-04-17] #general

[OpenWhisk Team Slack]

2019-04-17 06:40:34 UTC - owen: thank you, I'll take a look
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1555483234052700?thread_ts=1555396476.027800=C3TPCAQG1

2019-04-17 14:36:54 UTC - Rob Allen: Beijing time is _CST_ …
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p111814053700

2019-04-17 14:54:23 UTC - Shazron Abdullah: (China Standard Time not to be 
confused with Central ST or Cuba ST...)
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p112863054400

2019-04-17 16:06:31 UTC - ed: are there any  predefined env variables set by 
openwhisk or ibm cloud functions? I would like my code to know that I'm running 
inside ow or ibmcf
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p117191055500

2019-04-17 16:09:29 UTC - Rodric Rabbah: you can check for the presence of 
`process.env.__OW_ACTIVATION_ID`
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p117369055900

2019-04-17 16:10:11 UTC - Rodric Rabbah: more generally, 

https://openwhisk-team.slack.com/archives/C3TPCAQG1/p117411056100

2019-04-17 16:14:51 UTC - James Thomas: does anyone know what the caching 
policy is for custom docker images in openwhisk? when I update an existing 
custom runtime image in docker hub, there seems to be a delay in that image 
being available to the action using that image.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p117691057300

2019-04-17 16:16:06 UTC - Rodric Rabbah: You have to update the action to force 
a docker refresh: wsk action update name
Is enough
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p117766058100

2019-04-17 16:16:20 UTC - Markus Thömmes: not sure that's true anymore
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p117780058500

2019-04-17 16:16:25 UTC - Rodric Rabbah: ah ok
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p117785058800

2019-04-17 16:16:36 UTC - Markus Thömmes: I think we do something "smart" based 
on whether you use latest or some tag
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p117796059100

2019-04-17 16:16:52 UTC - Markus Thömmes: using latest + @Rodric Rabbah's tip 
should do the trick, I think?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p11781206

2019-04-17 16:16:54 UTC - Rodric Rabbah: ah. Vaguely remembering that.  
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p117814060100

2019-04-17 16:17:03 UTC - James Thomas: based on my informal testing recently, 
even if I delete the action and re-create it seems to use the old image for a 
short period
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p117823060400

2019-04-17 16:17:06 UTC - James Thomas: like  30 mins
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p117826060600

2019-04-17 16:17:26 UTC - James Thomas: I will try again and see where I get 
to…..
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p117846060900?thread_ts=117846.060900=C3TPCAQG1

2019-04-17 16:17:49 UTC - James Thomas: didn’t know about the `latest` thing - 
guess this isn’t documented anywhere? :slightly_smiling_face:
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p117869061400

2019-04-17 16:18:01 UTC - Markus Thömmes: I *think* it is! :smile:
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p117881061700

2019-04-17 16:18:08 UTC - James Thomas: :shocked_face_with_exploding_head:
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p117888061900

2019-04-17 16:18:38 UTC - Markus Thömmes: maybe I'm mistaken though, lemme skim 
through the codez
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p117918062200

2019-04-17 16:20:05 UTC - Markus Thömmes: 


Yeah, I'm mistaken. "latest" vs something else only triggers error handling on 
the pull call. Basically, if you use latest we assume you always want latest 
and don't tolerate a failure to pull
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p118005062900

2019-04-17 16:22:49 UTC - Rodric Rabbah: 

https://openwhisk-team.slack.com/archives/C3TPCAQG1/p118169063100

2019-04-17 16:23:23 UTC - Rodric Rabbah: ?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p118203063300

2019-04-17 16:31:26 UTC - Carlos Santana: Use tag latest tag to always pull, or 
push with a new tag to pull. There is caching to not do the pull for none 
latest 
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p118686065200?thread_ts=117846.060900=C3TPCAQG1

2019-04-17 16:44:47 UTC - James Thomas: @Carlos Santana get back on holiday sir!
palm_tree : Carlos Santana
beach_with_umbrella : Carlos Santana