I'm not sure that exposing a domain will help: do you know the IP of your task upfront, i.e., at the moment when you construct TaskInfo? Isn't your task listening on all interfaces?
On Wed, Jan 18, 2017 at 9:54 AM, CmingXu <[email protected]> wrote: > the network I am currently used is USER, and each task was assigned > with a unique vLAN IP with the underlaying docker driver is Macvlan. I > want my framework user have the ability to define there own > HealthChecks with the IP assigned to a specific task. > > I walked through the Mesos source code and obviously the TCP & HTTP > doesn't meet my requirements as DEFAULT_DOMAIN is hard coded, now the > only option to be might be health check with COMMAND, but if TCP does > support passing IP would be great help. > > Thanks > > On Wed, Jan 18, 2017 at 4:40 PM, Jie Yu <[email protected]> wrote: > > Hi, can you elaborate a bit more on why you need to use an customized IP, > > rather than using localhost for health check? > > > > - Jie > > > > On Wed, Jan 18, 2017 at 9:19 AM, CmingXu <[email protected]> wrote: > >> > >> Is there any plan we support customized IP when define a health check? > >> If true, what's the ETA? > >> > >> thanks > > > > >
