To clarify some offline questions: DRM = Distributed Resource Manager. It describes a class of products that are job schedulers, like SGE (gridengine.sunsource.net), LSF, OpenPBS, Maui Scheduler, etc. Think of it like RDBMS describes databases like Oracle, Sybase, SQL Server, etc.
----- Original Message ----- From: "Tim Harsch" <[EMAIL PROTECTED]> To: "IvorW" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Wednesday, March 24, 2004 10:10 AM Subject: Re: DRMAA namespace (DRMAA - Distributed Resource Manager Application API) > comments below. > > ----- Original Message ----- > From: "IvorW" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Tuesday, March 23, 2004 11:27 PM > Subject: Re: DRMAA namespace (DRMAA - Distributed Resource Manager > Application API) > > > > ----- Original Message ----- > > From: "Tim Harsch" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: 24 March 2004 03:08 > > Subject: DRMAA namespace (DRMAA - Distributed Resource Manager Application > API) > > > > > > > Hi all, > > > I have created a module that is a Perl binding to the drmaa spec, > > > http://www.drmaa.org. The drmaa spec is to abstract an API for > submitting > > > jobs to different supporting job schedulers (so a method to distribute > jobs > > > over a network). The DRMAA provides a framework for job schedulers much > > > like ODBC provides one for databases. Using DRMAA, the user is > protected > > > from the details of the job schedulers, also referred to as DRM's > > > (Distributed Resource Managers). I'm looking to post this module to > CPAN in > > > the next few weeks and am wondering about the namespace. I'm currently > > > leaning towards DRMAA (in all caps), and possibly a follow up module > later > > > called DRMAA::Simple, which would provide a set of functions that wrap > > > together many of the DRMAA calls into do-it-all-at-once type calls. > > > > A pity the acronym isn't DRAMA - this would have had much more > > buzzword potential ;). > > > > > It could be argued though that someone may want to create other DRM type > > > modules, say one that gives all the functionality of DRMAA plus specific > > > functions available to a particular DRM, like SGE > > > (http://gridengine.sunsource.net ). Or perhaps a DRM module that > provided > > > an API to configure the resources of the DRM, like adding nodes, > changing > > > run time calendars, etc. (currently DRMAA is just intended for launching > and > > > monitoring jobs ) > > > > > > So, perhaps a better namespace might be: > > > > > > DRM::DRMAA > > > DRM::DRMAA::Simple > > > and then later there could be > > > DRM::SGE > > > DRM::LSF > > > DRM::OpenPBS > > > etc. > > > > > > Comments, suggestions?? > > > > > > > Why look to a new top level namespace? Who else has heard of, > > or would think of DRM or DRMAA if they want scheduling. > > > > Well, in the clustering world, DRM is a standard term. So i'd say the folks > in that realm know what it means... but ... > > > Consider Schedule::. This is where I think your module belongs. > > > > e.g. Schedule::DRMAA, Schedule::DRMAA::Simple, Schedule::DRM::SGE > > etc. > > I think your right. Schedule is perhaps where it belongs. > > > > > This is an existing namespace that holds the likes of Schedule::Cron and > Schedule::Depend. > > > > My $0.02 > > > > Ivor. >
