[
https://issues.apache.org/jira/browse/MESOS-7317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15973771#comment-15973771
]
Adam B commented on MESOS-7317:
-------------------------------
Obviously we'll need authentication and authorization on these new
endpoints/calls.
Are you planning to make these v1-only, or v1 and v0?
ACLs can probably be coarse-grained, like the suggestion for MESOS-2222 , e.g.
Dan can DeactivateAgents for ANY agent, without trying to do attributed based
access control to specify which agents a user can activate/deactivate. Object
is just ANY/NONe.
> Add master endpoint to deactivate / activate agent
> --------------------------------------------------
>
> Key: MESOS-7317
> URL: https://issues.apache.org/jira/browse/MESOS-7317
> Project: Mesos
> Issue Type: Improvement
> Components: agent, master
> Reporter: Neil Conway
> Labels: mesosphere
>
> This would allow the operator to deactivate and then subsequently activate an
> agent. The allocator does not make offers for deactivated agents; this
> functionality would be useful to help operators "manually (incrementally)
> drain" the tasks running on an agent, e.g., before taking the agent down.
> At present, if the operator causes a framework to kill a task running on the
> agent, the framework will often receive an offer for the unused resources on
> the agent, which will often result in respawning the killed task on the same
> agent.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
