Mesos-agent maybe not 'really' binding on ip

[Marc Roos <M....@f1-outsourcing.eu>]

I have noticed that when I configure mesos-agents to run on the aliased 
ip, there is a problem with the tls certificates host names. Some 
communication still comes from the 'main' adapter ip 192.168.10.114.
First I thought this is normal, but my rsync sessions are fine and also 
running like this. Maybe worth checking out.



[@ mesos]# ifconfig

macvtap0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.114  netmask 255.255.255.0  broadcast 
192.168.10.255
        ether 7e:e5:79:d1:2a:18  txqueuelen 500  (Ethernet)
        RX packets 3973188  bytes 6703037003 (6.2 GiB)
        RX errors 0  dropped 1247  overruns 0  frame 0
        TX packets 3594652  bytes 16450477885 (15.3 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

macvtap0:1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.57  netmask 255.255.255.0  broadcast 
192.168.10.255
        ether 7e:e5:79:d1:2a:18  txqueuelen 500  (Ethernet)




[@~]# cat /etc/default/mesos
LOGS=/var/log/mesos
ULIMIT="-n 8192"


IP=192.168.10.57