This document discusses using Apache Mesos to manage the containers that are used to invoke functions in Apache OpenWhisk. It describes adding a Mesos actor to OpenWhisk, which is an Akka application, to leverage Mesos. The Mesos actor handles leader election and framework registration with Mesos. Using Mesos allows OpenWhisk to leverage a Mesos cluster to dynamically scale the invokers that handle function invocations.

3. USER EXPERIENCES - A
DRIVING FACTOR

4. COST AND OPS
OPTIMIZATIONS

5. PRODUCT EXTENSIBILITY

6. MODERN APPS HAVE A
RICHER UX, ARE SMALLER,
COMPOSABLE,
AND REAL-TIME.

9. INSIDE APACHE
OPENWHISK

10. Apache OpenWhisk is a serverless, open source cloud
platform that executes functions
IN RESPONSE TO EVENTS

11. Apache OpenWhisk is a serverless, open source cloud
platform that executes functions
IN DOCKER CONTAINERS

12. CLI + API = FUNCTION MANAGEMENT

13. OPENWHISK CONCEPTS

15. OPENWHISK SCALING

16. Add an invoker

17. Add an invoker
Invoker will advertise itself via Kafka

18. Add an invoker
Invoker will advertise itself via Kafka
Controller will register it and monitor its health

19. BUT ...
WE'RE A MESOS SHOP

20. We don’t want
competing clusters
... (or container) managers

21. Can I use Mesos
to manage the cluster ?

22. Can I use Mesos
to control my containers
that invoke actions ?

23. YES !WITH SOME MINOR CHANGES

24. HOW TO MESOS IN AKKA

25. HOW TO MESOS IN AKKA
> OpenWhisk is an Akka application (scala)
> OpenWhisk uses Docker to launch containers
> Put a Mesos actor in there !

26. BUT ...
WHAT MESOS ACTOR ?

27. MESOSIFICATION IN 2
STEPS

28. MESOSIFICATION IN 2 STEPS
1. Build a Mesos actor
2. Use the Mesos actor in OpenWhisk

29. A MESOS ACTOR IN AKKA

30. HTTPS://BIT.LY/MESOS-ACTOR

31. A SHORT DEMO

32. MESOS ACTOR FEATURES
> Leader election - based on Akka Clustering
> New leader re-subscribe after disconnection - in
master/framework failover
> Framework ID persistence
> Mesos roles

33. MESOS ACTOR TODO
> Reconcile on startup - next update received will reset
tasks
> Shared task state - based on Akka Distributed Data

34. A SERVERLESS PLATFORM ON MESOS
> Masive Scale Operators expand/contract Mesos cluster
> OpenWhisk Alterations:
> Controller - none
> Invoker - ContainerFactory

35. OPENWHISK - BEFORE

36. OPENWHISK - AFTER

37. INVOKER - BEFORE & AFTER

38. OPENWHISK DEMO

39. THANK YOU

40. AKKA CLUSTER IN OPENWHISK
Shared container state
All cluster nodes have visibility to same container pool
One leader
Single leader is responsible for streaming Mesos messages from
master

41. SHARED CONTAINER STATE
Containers remain when scheduler stream is interrupted
New Containers cannot be created until new scheduler
instance resumes
Mitigate downtime with prewarm containers

42. ONE LEADER
New leader is elected by Akka
New leader will create new subscription to Mesos master
with the same FrameworkID
Reconcile existing tasks
Resume managing containers

43. DCOS COMMONS
> (+) State Store
> (+) Task coordination
> (-) libmesos
> (-) alpha