On Thu, Dec 29, 2011 at 12:15 AM, Ciaran Wills <[email protected]> wrote:
> I'm pretty new to grid engine, but have been getting along ok setting up a 
> small rendering farm with the version packaged with Fedora 16.  Here's a 
> question though:
>
> I have software that is licensed per host - I can run as many instances as I 
> like on a host and they will consume a single license.  But I can't figure 
> out how to set this limitation up in grid engine; I assume it can be done 
> with complexes but can't get my head around how to do it.  Any ideas?

You can manage it as a global consumable resource:
http://gridscheduler.sourceforge.net/howto/consumable.html

And you can consider setting up a load sensor if the licenses are used
by interactive users:
http://gridscheduler.sourceforge.net/howto/loadsensor.html

Finally, if the simpler methods are not enough for your environment,
see the flex-grid integration:
http://olesenm.github.com/flex-grid/


> Oh, and a side question - I'm confused about the proliferation of versions.  
> Which grid engine is actually in the Fedora 16 distribution?  Is it the last 
> Sun open source one or one of the offshoots?

Since the Sun Grid Engine days, Fedora takes the official Sun version,
and integrates some of the patches, and adds a number of its own
patches. Just like MySQL & PostgreSQL in Fedora, some of the patches
are Fedora specific and are not upstreamed.

While I am interested in getting more Open Grid Scheduler users, I
have to give you the advice first: In general, if the version you have
installed works for you, then do not upgrade to a newer version just
because it is newer. I have worked with clients that have clusters
that are still using early versions of SGE 6.0.

(And besides Open Grid Scheduler, Dave Love also maintains his fork of
Grid Engine.)

Rayson



>
> Thanks!
>
> The content of this e-mail (including any attachments) is strictly 
> confidential and may be commercially sensitive. If you are not, or believe 
> you may not be, the intended recipient, please advise the sender immediately 
> by return e-mail, delete this e-mail and destroy any copies.
>
> _______________________________________________
> users mailing list
> [email protected]
> https://gridengine.org/mailman/listinfo/users

_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users

Reply via email to