...
Collectives are defined through a simple JSON file. Assuming a facility with 10 servers, named server01 to server10, here is how to build such a file for the above 5 collectives example:
{"Rack-1" : [ "server01", "server02", "server03", "server04", "server05" ],"Rack-2" : [ "server06", "server07", "server08", "server09", "server10" ],"Lighter-A" : [ "server01,16", "server02,16", "server03,16" ],"Lighter-B" : [ "server04,16", "server05,16", "server06,16" ],"All-servers" : [ "server01", "server02", "server03", "server04", "server05", "server06", "server07", "server08", "server09", "server10" ]} |
Equipped with this file, which can be named and saved wherever you choose among your installation, all you have to do is point to it in the 3delight.config configuration file by adding this line:
...
With this information, the 3Delight Collective option will be available among the 3Delight Preferences accompanied with a menu to select which collective to use:
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 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.