[CONF] OpenWhisk > OpenWhisk on Kubernetes

[Dragos Dascalita Haut (Confluence)]

Title: Message Title

There's 1 new edit on this page

OpenWhisk on Kubernetes Dragos Dascalita Haut edited this page Here's what changed: ... The Control Plane should provide an API used by the Data Plane to cold-start actions, and it should also emit events each time a change in the resource allocation happens; each time GC removes idle containers, or each time a new action is created, the Control Plane should notify all Data Plane instances of such changes.  Info To be detailed: Unlike the current OW, the system is "async by default". The new design is "sync by default". The open question is how to handle async cases. Data Plane The data plane layer invokes actions as fast as possible. When an action needs to be cold-started, the data plane delegates this to the Control Plane, awaiting for the action to become ready before invoking it. Once an action is warmed-up the data plane is notified, and if it was waiting for such event in order to invoke an activation, it should resume the execution.  ... Go to page history View page

Stop watching space • Manage notifications This message was sent by Atlassian Confluence 6.15.2