[
https://issues.apache.org/jira/browse/MESOS-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15085845#comment-15085845
]
Sargun Dhillon edited comment on MESOS-4114 at 1/6/16 5:10 PM:
---------------------------------------------------------------
I think we should just do a label on ports. In order to expose a VIP, a port
can have a label named vip with a value of a standard ip:port notation. So,
like 1.2.3.4:4000, or [::1]:80. Let's get rid of the field VIPInfo, I think
it's inflexible, an complicated.
Of course this info should be exposed via state.json as well.
was (Author: sargun):
I think we should just do a label on ports. In order to expose a VIP, a port
can have a label named vip with a value of a standard ip:port notation. So,
like 1.2.3.4:4000, or [::1]:80. Let's get rid of the field VIPInfo, I think
it's inflexible, an complicated.
> 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
> Fix For: 0.27.0
>
>
> 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)
