Hi Eric, Thanks for your response.
It think my point is that the current documentation doesn't give any indication on topology or grid planning at all, just that you can install Globus, these are the components. In my case I'm just setting up Globus as middleware interface to our Rocks cluster, which uses the Sun Grid Engine as a Resource Manager. The cluster has a head node and 12 compute nodes, for a total of 104 processors and 384GB of RAM. The compute nodes exist on a private internal (physical) network. I also have a virtual machine host that I can use to create servers, which means I prefer not to run services on the cluster's head node wherever possible to reduce overheads. Both the head node and VM host have access to the clusters private internal network, the external network, the internet in general (via our firewall), and access to a SAN via fibre channel. So far I've determined that GRAM5 should be installed on the head node and basically act as an interface to the SGE, but I'm still uncertain if I can set it up remotely. I think I need GridFTP and I think I can set that up on a VM and use it to bridge the external and internal networks. I think I want LRS, especially considering we plan on using iRODS, but I can't tell LRC and LRI are part of the same component or separate entities, nor can I tell if they can be separated out onto their own VM. I know I don't need MyProxy or GIS because we have a federated MyProxy already set up for us by our partners who want us to use Globus. So as you can see, my setup isn't a matter of simply installing Globus on all the nodes. Regards, Aaron Hicks > -----Original Message----- > From: b...@mcs.anl.gov [mailto:b...@mcs.anl.gov] > Sent: Wednesday, 10 February 2010 4:33 a.m. > To: Aaron Hicks > Subject: Re: [gt-user] Breaking up the Globus modules > > > You can run a GridFTP server on any node(s) that has access to the > filesystems that you want to make available to it. There are more > elaborate configurations using multiple GridFTP servers that are also > possible, but whether or not they make sense for your situation depends > on your expected usage, and on the details of your cluster/network > topology. > > In fact, there are many potential deployment scenarios/strategies for > the components comprising GT5, each dictated by the topologies and > needs of the individual resource. Without knowing more information, it > is difficult to give any kind of useful answer. > > Eric > > ----- "Aaron Hicks" <hic...@landcareresearch.co.nz> 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. > > > > Regards, > > > > Aaron Hicks > > > > > -----Original Message----- > > > From: gt-user-boun...@lists.globus.org [mailto:gt-user- > > > boun...@lists.globus.org] On Behalf Of Aaron Hicks > > > Sent: Tuesday, 2 February 2010 4:10 p.m. > > > To: gt-user@lists.globus.org > > > Subject: [gt-user] FW: Breaking up the Globus modules > > > > > > Sorry everyone, posted this to the wrong list. > > > > > > ...perhaps the announce list shouldn't be postable by anyone. > > > > > > -----Original Message----- > > > From: announce-boun...@lists.globus.org [mailto:announce- > > > boun...@lists.globus.org] On Behalf Of Aaron Hicks > > > Sent: Tuesday, 2 February 2010 1:29 p.m. > > > To: annou...@lists.globus.org > > > Subject: [Globus] Breaking up the Globus modules > > > > > > Hi all, > > > > > > The Globus toolkit documentation states that Globus Toolkit 5.0.0 > > is > > > modular, and it gives some explanation about each component > > (MyProxy, > > > GridFTP, RLS, GRAM5, etc). What's not stated is which modules must > > be > > > installed on First Node ('elephant' in the Quickstart guide), and > > which > > > modules could be installed on other servers. > > > > > > It looks like MyProxy and GridFTP could be set up on separate > > machines, > > > but I'm unsure about the other components. > > > > > > We'd like to _not_ have a single monolithic installation on the > > head > > > node of our cluster, and instead distribute out various services > > (like > > > MyProxy) to virtual machines, or GridFTP/RLS onto a server/VM > backed > > by > > > our SAN. This would allow us to tweak these components of Globus > > > without interfering with the others. > > > > > > ...it's going to be complex enough setting up GRAM5 so that it > > pipes > > > jobs into SGE. It looks like it should just work. > > > > > > Regards, > > > > > > Aaron Hicks > > > > > > > > > Please consider the environment before printing this email > > > Warning: This electronic message together with any attachments is > > > confidential. If you receive it in error: (i) you must not read, > > use, > > > disclose, copy or retain it; (ii) please contact the sender > > immediately > > > by reply email and then delete the emails. > > > The views expressed in this email may not be those of Landcare > > Research > > > New Zealand Limited. http://www.landcareresearch.co.nz > > > > > > Please consider the environment before printing this email > > > Warning: This electronic message together with any attachments is > > > confidential. If you receive it in error: (i) you must not read, > > use, > > > disclose, copy or retain it; (ii) please contact the sender > > immediately > > > by reply email and then delete the emails. > > > The views expressed in this email may not be those of Landcare > > Research > > > New Zealand Limited. http://www.landcareresearch.co.nz > > > > Please consider the environment before printing this email > > Warning: This electronic message together with any attachments is > > confidential. If you receive it in error: (i) you must not read, use, > > disclose, copy or retain it; (ii) please contact the sender > > immediately by reply email and then delete the emails. > > The views expressed in this email may not be those of Landcare > > Research New Zealand Limited. http://www.landcareresearch.co.nz Please consider the environment before printing this email Warning: This electronic message together with any attachments is confidential. If you receive it in error: (i) you must not read, use, disclose, copy or retain it; (ii) please contact the sender immediately by reply email and then delete the emails. The views expressed in this email may not be those of Landcare Research New Zealand Limited. http://www.landcareresearch.co.nz
