On Mon, Feb 8, 2010 at 7:58 PM, Aaron Hicks <[email protected]> wrote: > Hi All, > > Still working on this, having a very difficult time figuring out what > components of the Globus Toolkit I need to install, and where they ought to > be installed. > > I have figured that I can just have GRAM5 on the Head Node (aka Service Node, > first node) of our cluster and use the LRM Adaptor and LRM Module to push > jobs into our existing Sun Grid Engine. A lot of reading needed to find that > GRAM5 supports SGE out of the box. > > ...but do not want the GridFTP service managed or stored from the Head Node. > I've also found that you often have to drill very deeply into the > documentation before you discover that you do or don't need a component. Even > as far as reading the SRB site to figure out that I won't need that and the > SRB-DSI until much later. >
Hi Aaron, I'm new to GT too and found it a bit difficult to understand which components to install for my requirements. My requirement is for a high-performance file transfer system spread across two WAN sites. Here is what we've done, and its working fine so far : Site A : 3 hosts Host A1 is what we call the "master" node , it runs MyProxy , WS Container and has the RFT command line tools. Hosts A2 and A3 are the gridftp nodes. They have gridftp server and the ws-container installed and running Site B: 2 hosts Hosts B1 and B2 are the gridftp nodes. They have gridftp server and the ws-container installed and running We simplified the procedure by doing a full "make". i.e. we compiled all the packages using the method shown in the quickstart guide. Then we tarred and copied the installed directory ($GLOBUS_LOCATION) to our other nodes. Lastly, we ran "gpt-postinstall -force" on each node and only configured the components we need. So if we need gridftp and ws-container on hosts A2, A3, B1 and B2, we only configured and started those two components on those hosts. Of course it helps that the OS, software and tools setup across our hosts is mostly identical. Cheers ARN
