Hi Chetan,
The greatest news can go to that OpenWhisk officially first-time released all
the 12 modules under Apache as incubator project.
We have walked through the voting processes for all the modules, and we passed
all the vote mails.
The download links are available here:
Hi OpenWhiskers,
After everybody's great effort, OpenWhisk has now successfully releases all the
12 designated modules:
OpenWhisk
CLI
Catalog
Wskdeploy
Apigateway
Client Go library
Runtime Nodejs
Runtime Java
Runtime Docker
Runtime Swift
Runtime Python
Runtime PHP
under Apache as incubator
Hi Ben,
Thanks for starting this thread.
I'll chime in with my POV.
I see the deployment largely structured around 3 layers:
1. Container Management. This layer contains logic to spin up a Kubernetes
or Mesos cluster. It could be a managed cluster ( Azure Container Service,
Amazon ECS for
Hi,
Please add to this thread any agenda items you'd like to discuss at the
Tech Interchange call tomorrow.
Call details:
Web Meeting: Tech Interchange (bi-weekly):
- Day-Time: Wednesdays, 11AM EDT (Eastern US), 5PM CEST (Central Europe),
3PM UTC, 11PM CST (Beijing)
- Zoom:
Congrats Michelle !!
TOC looks good, you have the architecture and building an app cover, and in
3 languages that's more than good IMO
One important info I would not leave out is WebActions what they and how to
deal with them.
I see many users having trouble finding good examples on building a
With concurrency of 1 like we have by default, the action container is not
free up until the log collection is finished, so the controller should not
schedule a new activation to the invoker until then, regardless if it's
blocking or not blocking.
I like the idea of the invoker be more detailed
Hi Michele,
Congratulations on the O'Reilly book proposal acceptance!
I also suggest including wskadmin in the Appendixes.
Another suggestion for the Appendixes is Lean OpenWhisk:
https://github.com/apache/incubator-openwhisk/pull/3886
I believe it will be merged by the time you write the
Hi Michele,
Congratulations for getting an O'Reilly contract. That's awesome!
Also, this list is totally the right place for this topic (IMO).
I have a little comment about the TOC: the way I read it your intended audience
are OW users (action developers), not developers of OW itself. Is that
Hi,
today, we execute the user-action in the invoker, send the active-ack
back to the controller and collect logs afterwards.
This has the following implication:
- controller receives the active ack, so it thinks the slot on the
invoker is free again.
- BUT the invoker is still collecting logs,
