Hardware considerations for different node types

End Point node

• The main load on the endpoint node is generated by a network subsystem. This type of node requires much of the CPU performance and network throughput. It is also useful to bind network interfaces for redundancy and increased bandwidth, if possible.

Controller node• The cloud controller can be fat or thin.• The minimum configuration it can hosts includes those pieces of

OpenStack that maintain the system state: database and AMQP server• Redundant configuration of the cloud controller requires at least two

hosts• we recommend use of network interface binding for network

redundancy• RAID1 or RAID10 for storage redundancy• The following configuration can be considered the minimum for a

controller node:– Single 6-core CPU– 8GB RAM– 2x 1TB HDD in software RAID1

Compute nodes

• Compute nodes require as much memory and CPU power as possible

• Requirements for the disk system are not very restrictive• It is possible to use a single disk in a non-redundant

configuration • in case of failure replace the disk and return the server

back to the cluster as a new compute node.• for compute node hardware depend on customer

evaluation of average virtual instance parameters and desired density of instances per physical host.

Cinder node

• provide a persistent block storage feature to instances. Since block storage typically contains vital data

• it is very important to ensure its availability and consistence. The volume node must contain at least six disks

• We recommend installing the operating system on a redundant disk array (RAID1)

• The remaining four disks are assembled in a RAID5 array or RAID10 array, depending on the configuration of the RAID controller.