THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
| Gliffy Diagram | ||||
|---|---|---|---|---|
|
Originally OpenWhisk was built with the assumption that each Invoker is responsible for a single VM in the cluster. With a Cluster Manager, this premise changes, as a single Invoker could be in charge of the entire cluster. The Cluster Manager is responsible for each VM. From the Invoker's perspective, the entire cluster looks like a single pool of resources.
...
| Gliffy Diagram | ||||
|---|---|---|---|---|
|
Management Plane
The management layer exposes an API that is primarily serving developers that manage actions, triggers, rules, and APIs. The wsk CLI interacts with this layer.
...
This layer should have support for sequences, and for ensuring the default FaaS execution model which sends only 1 request at a time to an action. concurrency of 1 for action invocation.
The Data Plane should perform the Authentication and Authorization that OpenWhisk Controller does currently, and it should decorate the request with the context set by OpenWhisk (i.e. __OW_NAMESPACE, __OW_ACTION_NAME, __OW_ACTIVATION_ID, etc)
CNCF Projects to integrate with
...