[
https://issues.apache.org/jira/browse/MESOS-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14033262#comment-14033262
]
Vinod Kone commented on MESOS-1486:
-----------------------------------
[~nnielsen] To provide some background, the "--whitelist" flag was added to the
master during 0.9.0 release to deal with some upgrading issues. Back then we
didn't have a good backwards compatibility story, so this was a hack. As you
alluded to, the whitelist lets the slaves to still register with the master
just not offer its resources. I meant to kill this code but never got around
it. Also, Alexandra Sava is going to add a "deactivate" endpoint to masters to
provide operators the ability to deactivate slaves (not send offers) for
maintenance purposes.
IOW, the whitelist code is going to be removed soon from the masters. So it
would be great if we don't re-introduce this concept in the slave code if we
there are alternative ways to achieve what you are after. For example, can we
use authentication and authorization to solve this issue?
> Add whitelisting of masters in slaves.
> --------------------------------------
>
> Key: MESOS-1486
> URL: https://issues.apache.org/jira/browse/MESOS-1486
> Project: Mesos
> Issue Type: Improvement
> Components: slave
> Reporter: Niklas Quarfot Nielsen
>
> 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.2#6252)
