Is 'hostonce' an in-development feature on any of the newer gridengine versions at the moment?
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
