[
https://issues.apache.org/jira/browse/MESOS-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15211658#comment-15211658
]
Deshi Xiao edited comment on MESOS-1739 at 3/25/16 10:48 AM:
-------------------------------------------------------------
[~vinodkone] i would like to working on it. firstly we need get the design docs
done. i notice the http api propose is accepted, does it mean we support api
trigger to change the configuration?
i have read your ideas on above comments, you like to propose:
1. Lets do the reconfiguration of a slave via a restart (at least for now)
instead of via API endpoint.
in our requirement, we prefer API to update the attributes. another properties
such as roles, i agree with your idea. so i suggest i can identify which config
can use restart agent way, and else another config can use API to update.
was (Author: xds2000):
[~vi...@twitter.com] i would like to working on it. firstly we need get the
design docs done. i notice the http api propose is accepted, does it mean we
support api trigger to change the configuration?
i have read your ideas on above comments, you like to propose:
1. Lets do the reconfiguration of a slave via a restart (at least for now)
instead of via API endpoint.
in our requirement, we prefer API to update the attributes. another properties
such as roles, i agree with your idea. so i suggest i can identify which config
can use restart agent way, and else another config can use API to update.
> Allow slave reconfiguration on restart
> --------------------------------------
>
> Key: MESOS-1739
> URL: https://issues.apache.org/jira/browse/MESOS-1739
> Project: Mesos
> Issue Type: Epic
> Reporter: Patrick Reilly
> Labels: external-volumes, mesosphere, myriad
>
> Make it so that either via a slave restart or a out of process "reconfigure"
> ping, the attributes and resources of a slave can be updated to be a superset
> of what they used to be.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
