[
https://issues.apache.org/jira/browse/MESOS-6902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15840371#comment-15840371
]
Benjamin Mahler commented on MESOS-6902:
----------------------------------------
For now, we put the capabilities within the (re-)registration messages,
similarly to how version is handled. This is because we didn't want to solve
the issue of determining which changes to AgentInfo are compatible, and
updating the master to re-persist the new AgentInfo:
{noformat}
commit 2ff8f0129996e79ba07e19fbbc7b8472a2bde448
Author: Jay Guo guojiannan1...@gmail.com
Date: Thu Jan 26 11:55:34 2017 -0800
Moved agent capabilities from SlaveInfo to (re-)registerSlaveMessage.
We want agents to be able to upgrade to support new capabilities after
reregistration, however we don't support udpating SlaveInfo yet. This
patch moves agent capabilities protobuf message from SlaveInfo to the
(re-)registerSlaveMessage so that capabilities are communicated through
the agent registration and re-registration.
Review: https://reviews.apache.org/r/55943/
{noformat}
I'll leave this open to capture the work needed to move this into AgentInfo and
expose it to frameworks. We should also do this for version.
> Add support for agent capabilities
> ----------------------------------
>
> Key: MESOS-6902
> URL: https://issues.apache.org/jira/browse/MESOS-6902
> Project: Mesos
> Issue Type: Improvement
> Components: agent
> Reporter: Neil Conway
> Assignee: Jay Guo
> Labels: mesosphere
>
> Similarly to how we might add support for master capabilities (MESOS-5675),
> agent capabilities would also make sense: in a mixed cluster, the master
> might have support for features that are not present on certain agents, and
> vice versa.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
