You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "Avinash Sridharan (JIRA)" <ji...@apache.org> on 2015/12/12 22:59:46 UTC

[jira] [Comment Edited] (MESOS-4114) Add field VIP to message Port

    [ https://issues.apache.org/jira/browse/MESOS-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15054661#comment-15054661 ] 

Avinash Sridharan edited comment on MESOS-4114 at 12/12/15 9:59 PM:
--------------------------------------------------------------------

[~sargun] , [~tknaup] so what is the final consensus on this ? Should we have a "vip" field in DiscoveryInfo and Port will have a localPort/instancePort field associated with it ? Can we close the requirements on this?


was (Author: avinash@mesosphere.io):
[~sargun] , [~tknaup] so what is the final consensus on this ? Should have a "vip" field in DiscoveryInfo and Port will have a localPort/instancePort field associated with it ? Can we close the requirements on this?

> Add field VIP to message Port
> -----------------------------
>
>                 Key: MESOS-4114
>                 URL: https://issues.apache.org/jira/browse/MESOS-4114
>             Project: Mesos
>          Issue Type: Wish
>            Reporter: Sargun Dhillon
>            Assignee: Avinash Sridharan
>            Priority: Trivial
>              Labels: mesosphere
>
> We would like to extend the Mesos protocol buffer 'Port' to include an optional repeated string named "VIP" - to map it to a well known virtual IP, or virtual hostname for discovery purposes.
> We also want this field exposed in DiscoveryInfo in state.json.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)