-
Type:
Epic
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 1.3.0
-
Component/s: allocation, master, scheduler api
-
Labels:
-
Epic Name:multi-role frameworks (phase 1)
-
Target Version/s:
Currently, a framework can only obtain resources for a single allocation role. This design discusses allowing frameworks to obtain resources for multiple allocation roles.
Use cases:
- Allow an instance of a framework to be “multi-tenant” (e.g. Marathon, Aurora, etc). Currently, users run multiple instances of a framework under different roles to support multiple tenants.
- Allow a framework to further leverage the resource allocation primitives within Mesos to ensure it has sufficient resource guarantees in place (e.g. a framework may want to set different guarantees amongst the tasks it needs to run, without necessarily being multi-tenant).
- duplicates
-
MESOS-1142 Add a 'roles' field to FrameworkInfo.
-
- Resolved
-
- is depended upon by
-
MESOS-6627 Allow frameworks to modify the role(s) they are subscribed to.
-
- Resolved
-
- is related to
-
MESOS-7075 mesos-execute rejects all offers
-
- Resolved
-
-
MESOS-7077 Check failed: resource.has_allocation_info().
-
- Resolved
-
- relates to
-
MESOS-6375 Support hierarchical resource allocation roles.
-
- Reviewable
-