We have a cluster of Mac OSX G5s that are used during the daytime in
classrooms and labs, but are left idle in the evenings and weekends. We
are using PBS and Globus to submit jobs to run during these off-hours,
and we'd like to offer MPI jobs as well. We'd like to open up a
specified range of ports for use by LAM/MPI, without opening access to
all TCP ports (which the sysadmin would rightfully never allow). SSH is
used to communicate between nodes.
Additionally, we'd like each of the execute nodes to only need to hold
the public key to the head node, while the head node would hold the
public keys to each individual exeecute node. Right now we're just
testing with two nodes, so I'm not sure if this is possible as well.
Any thoughts on how to go about this?
Thanks,
- Beth
Jeff Squyres wrote:
>Unfortunately not -- the work was never completed because the goal
>there was to work between firewalls, and to do that, one essentially
>needed to create N external ghost IP addresses (one for each cluster
>node behind the firewall), and that was infeasible.
>
>What are you trying to do?
>
>
>On Jun 28, 2005, at 4:22 PM, Beth Kirschner wrote:
>
>
>
>>Hi,
>>
>> We're trying to use LAM/MPI in a (loosely bound) Mac OSX cluster.
>>The
>>LAM/MPI user's guide states that LAM/MPI "uses random TCP ports" and
>>that "firewall support must be either disabled or opened between
>>machines". Neither option is viable for us -- is there any way to
>>restrict the TCP ports that get used? I noticed a long thread on this
>>subject back in 2003
>>(http://www.lam-mpi.org/MailArchives/lam-devel/2003/10/0028.php), but
>>it
>>was left with open issues. Is there any (hopefully easy) way to
>>restrict
>>TCP ports to a specified range?
>>
>>Thanks!
>>- Beth
>>
>>_______________________________________________
>>This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>>
>>
>>
>
>
>
|
