...
It is only a matter of listing computers and associating them with a name. Lets make an example of defining the following 5 collectives in a hypothetical production facility:
Rackmount-1 → The servers located in rack number 1.
Rackmount-2 → 2 → The servers located in rack number 2.
Lighter-A A → A group of servers you want to dedicate to lighter A.
Lighter-B B → A group of servers you want to dedicate fo lighter B.
All-servers servers → All the servers.
Assuming the facility has 10 servers, named server01 to server10, here is how to build the JSON file for the above 5 collectives:
...
% sudo mv /Applications/3Delight/com.3delight.collective.plist /Library/LaunchDaemons/ ← to launch the license server when the system is started.
On Linux:
3Delight includes script that will start the collective service automatically on your render servers. After installing 3Delight on the render server:
% sudo cp $DELIGHT/bin/collective /etc/rc.d/init.d/
The service will then automatically run at boot time. . (to be completed) Note that some linux systems do not have the "rc.d" directory and the proper command is:
% sudo cp $DELIGHT/bin/collective /etc/init.d/
Additional Notes
- A server/computer can be part of one or more collectives. As is the case in the example above ("server01" is part of 3 out of the 5 collectives).
- With each server/computer name, you can specify a number of cores, eg. "server01,16". This limits the number of cores that will be used when rendering using this computer by invoking the collective it is part of. If the number is not specified, eg. "server01", then all the cores will be used.