Requirements

Clients:

Clients don't need any HD or graphical card (*) -diskless/headless-.
A x86 system with a minimum of 32MB(**) RAM and motherboard with builtin PXE capable network interface, is all that's needed. 
Most modern boards support PXE boot, check your BIOS boot parameters settings

*   Some current and future systems can use your graphical card's GPU as co-processor
** Allthough the OS only needs 32MB, the real memory requirements will propably be significantly larger. Unlike M$ based machines the memory limit is only restricted by the motherboard / renderer specifications.

 

Host(s):

As this system is very flexible and scalable there isn't really a computer that goes below specs.

Min. requirements > headless x86 system with 256MB RAM and network interface 2GB free diskspace for system
recommended > 512MB 2 x 1Gbs NIC's + 1 10/100Mbs -for heartbeat / watchdog- 2GB system disk  -as raid1- + sufficient disks for raid 0/1/10/5/6 project storage

LRP headless controller can be managed thru http-https / ssh / xdmcp interfaces

It is preferable to use 2 network interfaces on larger setups - 3 using heartbeat / watchdog -, 1 outbound to your local network, 1 inbound to your rendernodes -the builtin dhcp server used to asign IP adresses to your nodes might interfere with an existing DHCP server, most likely the router/modem  for your internet access-. In other words rendernodes should solely be connected to the node controller, node controller connected to internal network.

Small setups ( 1-30) can easily run from a workstation as a Vmware virtual machine since the memory footprint (32MB) and network load is very small.

Larger setups definately requires dedicated machines and plenty of RAM for project caching as network load will become considerable

Very large setups will require additional hosts to load balance and proxy your render network subnets. Please contact me for guidance & setup

  

  • Host:           A host is considered the machine that acts as a LDAP/DHCP/TFTP/SMB/Proxy server and bootstraps clients / distributes the render project / rendercontroller / load balancer / domaincontroller,  see installation instructions.
  • Client:         A client is the machine that gets his boot-data from the server host thru PXE & NFS. Project data is delivered thru the windows compatible SMB protocol -ordinary filesharing- allowing users to access, create and update project data over the network.
  • PXE boot :  Sometimes also wrongfully referred as Netboot -Apple proprietary system- uses DHCP & TFTP  to bootstrap diskless headless machines.