Sorry for the radio silence on this. This is probably just me not understanding how EC2 networking works, but I have couple of questions.
> > You can't `bind()' to an address that the network interface is not > > assigned. Maybe there is another workaround? I wouldn't know where to > > look. > > > So, you are saying the public ip address the EC2 host gets is not assigned to the NIC? How does it get it then? > > Either way, I think it's preferable to use DNS because it will map to > the > > correct address regardless of whether you're in or out of the EC2 > network. > > > Where does DNS come into the picture? > > > > On Mon, Jun 17, 2013 at 3:16 PM, Charles Reiss <[email protected]> > wrote: > > >> For everything but the webui, it's better to prefer the private IP > because > >> Amazon charges for data transfer using the public IP. > >> > I thought the problem with mesos on ec2 was that masters and slaves were not able to communicate when using private ip addresses (IIRC, at least one way communication was broken). So, I'm not sure how we can get around by not using public ip addresses for communication. > >> - Charles > >> > >> > > >> > > >> > On Mon, Jun 17, 2013 at 2:47 PM, Brenden Matthews < > >> > [email protected]> wrote: > >> > > >> >> Folks, > >> >> > >> >> I'd like to be able to make the master redirection in the web UI work > >> with > >> >> EC2, which has weird internal/external IP address issues. > >> >> > >> >> I was thinking about adding a hostname to the Master info message, > and > >> >> adding that along with the libprocess PID into the ZooKeeper state in > >> >> detector.{cpp,hpp}. > >> >> > >> >> Any thoughts on this? Are there any objections or concerns? From > >> >> examining the code, I couldn't think of a better way to do this. > >> >> > >> >> Thanks! > >> >> > >> >> Brenden > >> >> > >> > > >> > >> > > >
