Am 29.12.2011 um 15:25 schrieb Stephen Willey: > Is 'hostonce' an in-development feature on any of the newer gridengine > versions at the moment?
None of both. It was only an RFE which came up in earlier discussions already. But I also think, that a plain implementation could block the proper use of the license. I mean: imagine two jobs of this licensed software on a machine just overlapping a few seconds but besides this other 6 cores run other software (suppose 8 cores in total). As soon as one such job is started on a machine, you also might want to accummulate this type of job there to get the most out of the license. Something like "fillup", but not based on slots but the used license. And only if it cannot be scheduled, use another license on a separate machine. Idea 1: in a queue prolog attach a boolean complex to this queue instance. All jobs of this kind could request a soft resource of this complex, SGE will try to put the jobs on a machine where already such type of job is running. In a queue prolog, check whether it's the last job of this kind there, then remove the complex from the queue instance. Idea 2: are these serial or parallel jobs? For serial ones one can setup two queues with sort oder in opposite direction, filling the cluster with different types of jobs from both ends. -- Reuti > I agree with the above sentiment that upgrading isn't advisable if the > version you're running is working properly, but for me, this is a > killer feature. I've been a bit lazy about it but we may well start > using host licensed software a lot more heavily this year and I'd > really rather not segregate my farm to do it. That'd be like going > back to Alfred... > > If it's in development anywhere, I'd be happy to test. I'd contribute > but I don't think anyone would want to kind of code I write. > > Stephen > > > On Thu, Dec 29, 2011 at 9:52 AM, Reuti <[email protected]> wrote: >> Hi, >> >> Am 29.12.2011 um 06:15 schrieb Ciaran Wills: >> >>> 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? >> >> unfortunatelly there is no direct support for this kind of licensing. It was >> discussed already on the list, to support for a consumable besides YES/NO >> and JOB the behavior of HOST and HOSTONCE: >> >> http://arc.liv.ac.uk/pipermail/gridengine-users/2010-November.txt (please >> search for HOSTONCE) >> >> Can you set aside some nodes for this kind of jobs, making the floating >> license of course host-locked this way? Or submit an Advance Reservation and >> submit the jobs into this AR? >> >> -- Reuti >> >> >>> 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? >>> >>> 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 > > > > -- > Stephen > > http://lensframephoto.com > _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
