Mailing-List: contact user-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@ignite.apache.org
Date: Fri, 11 Mar 2016 14:40:44 -0800 (PST)
From: vkulichenko <valentin.kulichenko@gmail.com>
To: user@ignite.apache.org
Message-ID: <1457736044555-3464.post@n6.nabble.com>
In-Reply-To: 
 <CACtD+L=u1YV0JGdkpoPxJzD9MP9iSikk64XyuMdAtyKqStEL4Q@mail.gmail.com>
References: 
 <CACtD+L=u1YV0JGdkpoPxJzD9MP9iSikk64XyuMdAtyKqStEL4Q@mail.gmail.com>
Subject: Re: Connecting Amazon cluster with client from local
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi Alper,

That's a tricky question :)

This is possible to achieve if you implement AddressResolver that will map
private address to public address and provide it in the configuration
(IgniteConfiguration.setAddressResolver). This will add public address to
node attributes, and client node will know how to connect. On Amazon you can
use the special metadata URL [1] to get the public address. See [2] for more
details.

[1] http://169.254.169.254/latest/meta-data/public-ipv4
[2]
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-instance-addressing.html

In addition Ignite currently requires bi-directional connection even between
client and server, i.e. server has to be able to establish TCP connection
with client. This means that if your client is behind NAT (which is often
the case), you will have to provide proper address resolver there as well,
and configure port forwarding on the router.

This is something that should be seriously improved from usability
standpoint, I will create a ticket.

-Val


--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Connecting-Amazon-cluster-with-client-from-local-tp3453p3464.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.