On Thu, Mar 13, 2014 at 3:34 PM, Sergio Mafra <sergiohmafra_at_gmail.com> wrote:
> Since weŽd like to assign to each master, a specific private ip, IŽd like to
> know if this can be done in StarCluster or by CLI commands. so my users can
> always connect in their machines using the same procedure.
Short answer: currently there is no support for that in StarCluster.
Longer answer: While the boto (AWS Python) run_instances() API does
offer support for assigning specific private IP address (by using
parameter "private_ip_address") in a VPC subnet, there is a limitation
of starting only 1 instance when private_ip_address is specified.
Thus, if you want to do it that way, the StarCluster code will need to
pass in the "private_ip_address" parameter when starting the master
node. Then the slave nodes will need to be started in another
run_instances() call. It should be doable (with some code changes) as
just running a 1-node cluster, then adding new nodes is my recommended
way of starting large clusters in EC2.
Rayson
==================================================
Open Grid Scheduler - The Official Open Source Grid Engine
http://gridscheduler.sourceforge.net/
http://gridscheduler.sourceforge.net/GridEngine/GridEngineCloud.html
>
> All best,
>
> Sergio
>
>
> _______________________________________________
> StarCluster mailing list
> StarCluster_at_mit.edu
> http://mailman.mit.edu/mailman/listinfo/starcluster
>
Received on Thu Mar 13 2014 - 16:09:59 EDT