Hi folks,

I am trying to have the Chronos framework consume dynamic reservations in
Mesos. However, it appears that Chronos is unable to do this because it
does not pass the framework principal to Mesos when launching tasks (See
https://github.com/mesos/chronos/issues/843), which makes Mesos reject the
launch operation.

To get around this, I am considering changing my dynamic reservations to be
purely role-based instead of (role, principal)-based. Is this
allowed/valid? http://mesos.readthedocs.io/en/0.24.1/reservation/#
dynamic-reservation-since-0230 says "resources are reserved for a *role*." Does
this mean I can make a dynamic reservation just for (role) instead of
(role, principal)?

Thanks,
Srikanth

Reply via email to