You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Michael Park (JIRA)" <ji...@apache.org> on 2015/04/08 20:53:12 UTC
[jira] [Closed] (MESOS-2267) Master Reservation
[ https://issues.apache.org/jira/browse/MESOS-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Park closed MESOS-2267.
-------------------------------
Resolution: Won't Fix
The {{/reserve}} and {{/unreserve}} HTTP endpoints provide the ability for operators to manage reservations dynamically, which was the intended goal for master reservations.
> Master Reservation
> ------------------
>
> Key: MESOS-2267
> URL: https://issues.apache.org/jira/browse/MESOS-2267
> Project: Mesos
> Issue Type: Epic
> Components: allocation, master, slave
> Reporter: Michael Park
> Assignee: Michael Park
> Labels: mesosphere
>
> This is a feature to allow configuration of reservations on individual slaves from the master. Currently the slave is started with a {{--resources}} flag which specifies the resources configuration of the slave (including reservations). The goal of this feature 2 folds:
> 1. Start the migration of the reservation information from the slave to the master, and
> 2. Add an API endpoint to the master to allow making configuration changes via the master rather than slave restarts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)