[
https://issues.apache.org/jira/browse/MESOS-3943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yong Qiao Wang updated MESOS-3943:
----------------------------------
Shepherd: Adam B
Description: Currently, RoleInfo protobuf never be used for serialization,
so I think we can remove it from allocator.proto, and define a struct to
communicate between the allocator and master. But for role information display,
then current serialization way(call modle(role*) in http.cpp) is not better,
and we should define another RoleInfo protobuf for serialization. Refer to
other components(such as quota), I propose to define role protobuf in a
separated package rather than define it in mesos.proto. (was: Mesos allocator
should aware the role change, this includes adding, updating and delete a role.
so in this ticket, we will extend the allocator interface based on the design
https://docs.google.com/document/d/1OIgceqpsjV3-_LGF83IMAFnrh1Ea3Zc16w9kWWPpUj4/edit#)
Summary: Support dynamic weight in allocator (was: Dynamic
roles/weights support in allocator)
> Support dynamic weight in allocator
> -----------------------------------
>
> Key: MESOS-3943
> URL: https://issues.apache.org/jira/browse/MESOS-3943
> Project: Mesos
> Issue Type: Task
> Reporter: Yong Qiao Wang
> Assignee: Yong Qiao Wang
>
> Currently, RoleInfo protobuf never be used for serialization, so I think we
> can remove it from allocator.proto, and define a struct to communicate
> between the allocator and master. But for role information display, then
> current serialization way(call modle(role*) in http.cpp) is not better, and
> we should define another RoleInfo protobuf for serialization. Refer to other
> components(such as quota), I propose to define role protobuf in a separated
> package rather than define it in mesos.proto.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
