Re: Specifying only public or private IP for RunScriptOnNode

2014-06-03 Thread Ignasi Barrera
Ah OK :) I had in mind to look at it later and just went through it without reading the thread again :) Good to see it is working! I. On 3 June 2014 00:28, Daniel Widdis wid...@gmail.com wrote: Ignasi, As I impled earlier, it looks like it does work (I tested to be sure it worked for ALL

Re: Specifying only public or private IP for RunScriptOnNode

2014-06-02 Thread Andrew Phillips
I've tried the following: overrides.setProperty(SOCKET_FINDER_ALLOWED_INTERFACES, PRIVATE); That looks correct to me, Dan. If the conversion from a string is not working (it may only work as a string if set via a -D property on the command line? I'm not sure), you may want to import

Re: Specifying only public or private IP for RunScriptOnNode

2014-06-02 Thread Andrew Phillips
If it is (which it seems to be), I'm good to go. I'm also guessing a bit here (we'll see what the experts have to say ;-)), but as far as I am aware, Guice is the one providing the string-to-enum conversion as part of it's out-of-the-box binding support [2]. [1]

Re: Specifying only public or private IP for RunScriptOnNode

2014-05-25 Thread Ignasi Barrera
Hi Daniel, This was reported recently (see JCLOUDS-528 [1]) and fixed in master. If you use the latest 1.8.0-SNAPSHOT version you should be able to set the jclouds.compute.socket-finder-allowed-interfaces property to control which IP addresses are used to connect to the node (see [2]). We are

Re: Specifying only public or private IP for RunScriptOnNode

2014-05-25 Thread Andrew Phillips
We are about to release 1.7.3, and if no one says the opposite I'll back port that fix in a while, so if that works for you, you should be able to use it in the next release. Thanks, Ignasi! ap