[ 
https://issues.apache.org/jira/browse/MESOS-2830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14586969#comment-14586969
 ] 

Marco Massenzio commented on MESOS-2830:
----------------------------------------

I'll start looking into this and probably draft a design doc.
At first blush, I'm guessing a HTTP endpoint on the Master would be a better 
option, rather than expose the (possibly unreachable) Slaves?

Or is there a particular reason why we'd want to go straight to the slave 
machines?

Also, you mentioned the magic word {{container}} - however, that means that any 
changes (eg, adding a user and/or modifying the filesystem) would be 
"ephemeral" once the container goes away.

As you mentioned the alternative approach (a tedious and repetitive SSH'ing 
into the Slaves to execute the same operation) as a (very valid!) use case, may 
I assume that as the baseline use case?

(interestingly enough, I did implement exactly the same API endpoint and 
feature for our Migration Engine at RiverMeadow :) )

> Add an endpoint to slaves to allow launching system administration tasks
> ------------------------------------------------------------------------
>
>                 Key: MESOS-2830
>                 URL: https://issues.apache.org/jira/browse/MESOS-2830
>             Project: Mesos
>          Issue Type: Wish
>          Components: slave
>            Reporter: Cody Maloney
>            Assignee: Marco Massenzio
>            Priority: Minor
>              Labels: mesosphere
>
> As a System Administrator often times I need to run a organization-mandated 
> task on every machine in the cluster. Ideally I could do this within the 
> framework of mesos resources if it is a "cleanup" or auditing task, but 
> sometimes I just have to run something, and run it now, regardless if a 
> machine has un-accounted resources  (Ex: Adding/removing a user).
> Currently to do this I have to completely bypass Mesos and SSH to the box. 
> Ideally I could tell a mesos slave (With proper authentication) to run a 
> container with the limited special permissions needed to get the task done.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to