[MESOS-2587] libprocess should allow configuration of ip/port separate from the ones it binds to

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Component/s: libprocess
• Target Version/s: 0.23.0
• Assignee: Unassigned
• Reporter: Cosmin Lehene
• Created: 01/Apr/15 23:03
• Updated: 10/Nov/15 17:13
• Resolved: 14/May/15 02:50

Description

Currently libprocess will advertise LIBPROCESS_IPLIBPROCESS_PORT, but if a framework runs in a container without an an interface that has a publicly accessible IP (e.g. a container in bridge mode) it will advertise an IP that will not be reachable by master.

With this, we could advertise the external IP (reachable from master) of the bridge from within a container.

This should allow frameworks running in containers to work in the safer bridged mode.

Issue Links

• duplicates: MESOS-809 External control of the ip that Mesos components publish to zookeeper