| commit | 3c747df2c3c0877d2eb8030f657f169fc96104c3 | [log] [tgz] |
|---|---|---|
| author | Francesco Timperi Tiberi <francesco.timperi@gmail.com> | Tue Sep 24 20:57:12 2024 +0200 |
| committer | GitHub <noreply@github.com> | Tue Sep 24 20:57:12 2024 +0200 |
| tree | c7d1a399d0267f45102357beb26cdc188bcd468e | |
| parent | 487606f15e66bab8a9b180217814e1d733265f48 [diff] | |
| parent | c98228d31ee0b6ebef1560869370982aac928d62 [diff] |
Merge pull request #30 from francescotimperi/main chore: prepare release 1.21.0
All the Apache Openserverless OpenWhisk runtimes in a single place using the Go proxy and ActionLoop.
runtimes are docker images, and they all use a proxy in go and some scripts for execution.
Go Proxy code is in folder openwhisk and the main is proxy.go in top level.
You can compile it with go build -o proxy.
Tests are in openwhisk folder, test it with cd opewhisk ; go test
Runtime sources are under runtimes/<plang>/<version> (<plang> is programming languate)
Special case is runtime/common/<version> that contains the proxy itseself, it is used as base image for the others and must be build first.
Build and push the common runtime with task build-common. Also ensure the image is public.
Then you can build a single runtime specifingh the dir:
Build a single runtime: task build-runtime RT=nodejs VER=v18
The project contains a runtimes.json.tpl with specific placeholder for managed Apache OpenServerless runtimes. To regenerate a newer runtimes.json from the current TAG and assuming that the images have been effectively pushed to the Apache Official DockerHub repositories execute the command:
task render-runtimes
This will create a new runtimes.json that can be pushed to the official Apache OpenServerless task repo, replacing the existing file.
The proxy can be used in client or server mode, where the client acts as a forward proxy and the server will be the actual executor.
In client mode the runtime does not execute the action, but instead forwards the /init and /run requests to a server runtime. To activate this mode, set the environment variable OW_ACTIVATE_PROXY_CLIENT to 1. When creating actions, use the --main flag with this syntax: --main "<main>@<remote runtime address>". <main> can be empty.
The remote runtime is enabled by setting the environment variable OW_ACTIVATE_PROXY_SERVER to 1. In this mode the runtime is multi-action enabled, meaning that it can initialize and run more than one action. Many client runtimes can forward requests to the same server runtime.