Mailing-List: contact dev-help@whirr.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@whirr.apache.org
Received-SPF: pass (nike.apache.org: domain of paul.baclace@gmail.com
 designates 209.85.220.47 as permitted sender)
Message-ID: <51831A65.10407@gmail.com>
Date: Thu, 02 May 2013 19:01:09 -0700
From: Paul Baclace <paul.baclace@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6;
 rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: dev@whirr.apache.org
Subject: Re: public addresses
References: <38A34C57-C2F0-4F94-B6A1-4C1065E116B9@gmail.com>
In-Reply-To: <38A34C57-C2F0-4F94-B6A1-4C1065E116B9@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 20130425 23:53 , David Alves wrote:
> Hi All
> 		
> 	The answer to this question is probably obvious for most, but I forget:
> 	- Why are we using the node public addresses when opening ports in firewalls and reporting master nodes and what not?
>
> 	I some providers like GCE and Amazon this not only forces the traffic to be routed through the much slower NAT outer routers but actually charges for the traffic that goes through these interfaces.
> 	Moreover internal firewalls are usually off which should make our lifes easier in most cases.
Using the public network unintentionally used to be a common problem on 
AWS, but then they started having public dns addresses resolve to local 
ip addresses when they are resolved inside aws-ec2.

I don't know what GCE does.

Paul