Hi Stuart, Thanks for the response.
Overall the documents are very good at explaining how to install and set up the components, but there's no Overview document that covers the structure of the Globus Toolkit and how the components interact with each other, or how to plan your Grid (or as in my case, how to put Globus on your Cluster). The closest I've seen is the big stack of boxes diagram from the various power point presentations, but there's no explanation on why the boxes are stacked or coloured that way. It's also difficult at times to see if some components e.g. GridFTP and LRS are complimentary or replace each other. There's also no mention of which components have to be co-located on the same machine, and it's not until you get to the Admin guide that you might find that it's possible because a completely separate module has a URL or hostname as a configuration option. I think the problem I've been having is that I start with the Quickstart, then the Install doc, and don't find the details I'm looking for until I reach the Admin guide, by which time I've often forgotten exactly what I was looking for in the first place. The admin guide is good and all, but each section is quite specific and it seems that the relationship between two components relies on the _other_ component to document it. Overall it means I'm getting a very good description on each component and how to configure it, but very little information on how the components interact, and leaves me feeling like the whole toolkit is disconnected. The SGE adapters are a good example, if I start at the recommended start point, the Quickstart document, I have to go through to the Install, and then the Admin document before I find that it's even possible. Finding where it fits in and how to install and configure the adapter is nice, but what I need to know first is "Can I hook Globus to SGE?" Unqualified statements like "GT5 supports SGE" on a top level overview don't need more detail than "Read the Admin guide for configuring Local Resource Manager (LRM) adapters". > -----Original Message----- > From: Stuart Martin [mailto:[email protected]] > Sent: Wednesday, 10 February 2010 5:24 a.m. > To: Aaron Hicks > Cc: gt-userlist > Subject: Re: [gt-user] Breaking up the Globus modules > > Hi Aaron, > > Thanks for the feedback and sorry about the troubles. Looks like we > need to make some improvements in the GT doc. > > I assume you looked at the quickstart guide for setting up the GT > components. Maybe that is too basic and does not discuss well the > options/recommendations for setting up a grid? Seems like we need a > new higher-level doc for that. > http://www.globus.org/toolkit/docs/5.0/5.0.0/admin/quickstart/#qu > ickstart > > For the GRAM LRMs supported by Globus, there is a list here in the > admin guide. SGE is listed there. That seems ok to me. > http://www.globus.org/toolkit/docs/5.0/5.0.0/execution/gram5/admi > n/#gram5-admin-lrmAdapters > > Cheers, > -Stu > > On Feb 8, 2010, at Feb 8, 9:58 PM, Aaron Hicks 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: [email protected] [mailto:gt-user- > >> [email protected]] On Behalf Of Aaron Hicks > >> Sent: Tuesday, 2 February 2010 4:10 p.m. > >> To: [email protected] > >> 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: [email protected] [mailto:announce- > >> [email protected]] On Behalf Of Aaron Hicks > >> Sent: Tuesday, 2 February 2010 1:29 p.m. > >> To: [email protected] > >> 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
