Hi Dmitry.<div><br></div><div>This plugin has been found on the internet and should be other option: <a href="https://gist.github.com/adgaudio/9200030">https://gist.github.com/adgaudio/9200030</a></div><div><br></div><div>
all best,</div><div><br></div><div>Sérgio<br><br>Em quinta-feira, 13 de março de 2014, Sergio Mafra <<a href="mailto:sergiohmafra@gmail.com">sergiohmafra@gmail.com</a>> escreveu:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Dmitry and Rayson,<div><br></div><div>Thanks for the explanation and tips for this situation that should be a common place when StarCluster moves to private subnets.</div>Other option could be assigning a secondary IP to master using EC2 cli, where this IP is fixed.<div>
<br></div><div>All best,</div><div><br></div><div>Sérgio</div><div><div><br>Em quinta-feira, 13 de março de 2014, Dmitry Serenbrennikov <<a href="javascript:_e(%7B%7D,'cvml','dmitry@adchemy.com');" target="_blank">dmitry@adchemy.com</a>> escreveu:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Sergio,<br>
<br>
To add to Rayson's answer, perhaps you can consider using DNS entries instead of fixed IP addresses?<br>
In our case, that's what we are doing. (Honestly, I didn't even know you could request specific IPs...)<br>
<br>
I wrote a small plugin to have starcluster automatically maintain Route53 entries for each master and the nodes.<br>
Feel free to use it as is or modify: <a href="https://gist.github.com/nitecoder/9536584#file-starcluster-route53-plugin" target="_blank">https://gist.github.com/nitecoder/9536584#file-starcluster-route53-plugin</a><br>
<br>
By the way, this is only my second plugin ever, so I would very much appreciate any critique / improvements from the list!<br>
<br>
Cheers!<br>
-Dmitry<br>
<br>
<br>
________________________________________<br>
From: <a>starcluster-bounces@mit.edu</a> <<a>starcluster-bounces@mit.edu</a>> on behalf of Rayson Ho <<a>raysonlogin@gmail.com</a>><br>
Sent: Thursday, March 13, 2014 1:09 PM<br>
To: Sergio Mafra<br>
Cc: <a>starcluster@mit.edu</a><br>
Subject: Re: [StarCluster] Using MIT StarCluster on VPC<br>
<br>
On Thu, Mar 13, 2014 at 3:34 PM, Sergio Mafra <<a>sergiohmafra@gmail.com</a>> wrote:<br>
> Since we´d like to assign to each master, a specific private ip, I´d like to<br>
> know if this can be done in StarCluster or by CLI commands. so my users can<br>
> always connect in their machines using the same procedure.<br>
<br>
Short answer: currently there is no support for that in StarCluster.<br>
<br>
Longer answer: While the boto (AWS Python) run_instances() API does<br>
offer support for assigning specific private IP address (by using<br>
parameter "private_ip_address") in a VPC subnet, there is a limitation<br>
of starting only 1 instance when private_ip_address is specified.<br>
<br>
Thus, if you want to do it that way, the StarCluster code will need to<br>
pass in the "private_ip_address" parameter when starting the master<br>
node. Then the slave nodes will need to be started in another<br>
run_instances() call. It should be doable (with some code changes) as<br>
just running a 1-node cluster, then adding new nodes is my recommended<br>
way of starting large clusters in EC2.<br>
<br>
Rayson<br>
<br>
==================================================<br>
Open Grid Scheduler - The Official Open Source Grid Engine<br>
<a href="http://gridscheduler.sourceforge.net/" target="_blank">http://gridscheduler.sourceforge.net/</a><br>
<a href="http://gridscheduler.sourceforge.net/GridEngine/GridEngineCloud.html" target="_blank">http://gridscheduler.sourceforge.net/GridEngine/GridEngineCloud.html</a><br>
<br>
<br>
><br>
> All best,<br>
><br>
> Sergio<br>
><br>
><br>
> _______________________________________________<br>
> StarCluster mailing list<br>
> <a>StarCluster@mit.edu</a><br>
> <a href="http://mailman.mit.edu/mailman/listinfo/starcluster" target="_blank">http://mailman.mit.edu/mailman/listinfo/starcluster</a><br>
><br>
<br>
_______________________________________________<br>
StarCluster mailing list<br>
<a>StarCluster@mit.edu</a><br>
<a href="http://mailman.mit.edu/mailman/listinfo/starcluster" target="_blank">http://mailman.mit.edu/mailman/listinfo/starcluster</a></blockquote></div></div>
</blockquote></div>