You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "Niklas Quarfot Nielsen (JIRA)" <ji...@apache.org> on 2015/01/15 22:15:37 UTC

[jira] [Updated] (MESOS-1486) Introduce an optional master whitelist for slaves

     [ https://issues.apache.org/jira/browse/MESOS-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Niklas Quarfot Nielsen updated MESOS-1486:
------------------------------------------
    Sprint: Mesosphere Q4 Sprint 3 - 12/7, Mesosphere Sprint 4 - 1/23/15  (was: Mesosphere Q4 Sprint 3 - 12/7)

> Introduce an optional master whitelist for slaves
> -------------------------------------------------
>
>                 Key: MESOS-1486
>                 URL: https://issues.apache.org/jira/browse/MESOS-1486
>             Project: Mesos
>          Issue Type: Improvement
>          Components: slave
>            Reporter: Niklas Quarfot Nielsen
>            Assignee: Alexander Rukletsov
>
> Like masters can whitelist slaves (and only announce available resources from slaves whitelisted), slaves should be able to whitelist masters they are willing/allowed to connect to. I have a proof-of-concept ready which ties into the slave::detected() method and prevents non-whitelisted masters to register.
> If "*" is provided - whitelisting is not enforced (which would be the usual case).



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