We have been using option #2 for a while now, We started with a cron pushing a updated Day or Night host file, but now we do it though puppet. We generally run the change from day to night around an hour or so before the normal end of the day, so lighters can submit jobs before the end of the day and they will get the changes. Then the change from night to day about an hour before people come in so any jobs that are running have some time to finnish. Its not fullproof, but in most cases its worked for us.
At some point I need to investigate how to add the machines that are dedicated during the day to the greater pool at night. I just haven't had the time to look into it.
BTW, congrats Greg on the Academy award!
-Brent
On Jan 23, 2011, at 5:49 PM, Dylan Penhale wrote:
> [posted to rush.general]
>
> We currently split our render groups and criteria according to machine spec=
> s, software and department. We would like to be able to reserve a pool sele=
> ction from 9-00 till 22-00 and then open that pool to the rest of the farm =
> out of those hours.=20
>
> e.g. Comp renders are fast, we don't want 3D renders on those machines duri=
> ng the day. However at night comp isn't (always) there so those machines co=
> uld be used by 3D. Currently the only way I can think to do this is to:
>
> 1) Play about with priorities - this has proved to be unsatisfactory becaus=
> e 3D renders can take so long.
> 2) Push out the hosts files as part of a cron - I've not tried this but ima=
> gine it wouldn't be robust.
> 3) Employ a render wrangler.=20
>
> Any suggestions?
>
> Dylan Penhale
> CTO
> Fuel VFX
> Sydney
>
>
>
>
>
>
|