[
https://issues.apache.org/jira/browse/MESOS-3962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15047883#comment-15047883
]
Avinash Sridharan commented on MESOS-3962:
------------------------------------------
Had a discussion with Adam and Sargun. From mesos perspective a labels field
needs to be introduced as an optional field in the message "Port" in
include/mesos/mesos.proto . We will also need to update the JSON model object
for TaskInfo to reflect these fields in state.json.
However, making these changes in itself is not enough since currently Marathon
is not populating the DiscoveryInfo field in TaskInfo. This implies that for
service discovery to consume this field there are changes that need to be made
in Marathon as well.
> Add labels to the message Port
> ------------------------------
>
> Key: MESOS-3962
> URL: https://issues.apache.org/jira/browse/MESOS-3962
> Project: Mesos
> Issue Type: Wish
> Reporter: Sargun Dhillon
> Assignee: Avinash Sridharan
> Priority: Minor
> Labels: mesosphere
>
> I want to add arbitrary labels to the message "Port". I have a few use cases
> for this:
> 1) I want to use it to drive isolators to install firewall rules associated
> with the port
> 2) I want to use it to drive third party components to be able to specify
> advertising information
> 3) I want to be able to able to use this to associate a deterministic virtual
> hostname with a given port
> Ideally, once the task is launched, these labels would be immutable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
