Platform Requirements
Following are the requirements for the dedicated Platform server node managing the Swarm implementation:
System | 2+ CPU cores 8+ GB RAM | Virtual machine The OVA file is configured to use 2 cores. |
---|---|---|
Storage | 80+ GB available disk storage | Swarm nodes need to direct syslog logging messages at a dedicated partition on the Platform server. Clusters that are large or have increased logging loads will require more storage for logging. |
OS | Ubuntu Server 16.04 (Xenial) | http://releases.ubuntu.com/xenial/ or Platform Server OVA Image |
Network | Static IP address | Configure a network interface with a static IP address on the managed network before installing Swarm Platform. Note: If your firewall settings prevent Internet access, you will need to install Platform using Offline Mode. |
IPMI | Enabled IPMI 2.0 or newer | To control the power state of managed chassis, Platform uses IPMI (Intelligent Platform Management Interface), a standard for out-of-band (LOM, Lights-Out Management) device management and monitoring using a dedicated management channel. iDRAC-equipped nodes to be used for Swarm Storage must have the setting Enable IPMI Over LAN enabled, which allows Platform Server to power the machine and commission the node. NoteIf iDRAC cannot be set to Enable IPMI Over LAN, the chassis needs needs to be manually powered on twice so it can progress through the lifecycle. See Manual Power Control under Deploying Storage, below. |
Network Planning
The Platform Server manages the allocation of IP addresses. There are three types of IP addresses (depending on the NIC configuration):
Dynamic Range — IP addresses used for enlistment and commissioning
Requirements
During bootstrap, Platform will reject a dynamic range that takes up more than 25% of the address space; if this is intended and necessary, you may add a
--force
flag to the bootstrap command.Platform will also reject any dynamic range that overlaps with IP addresses that are currently used.
Reserved Range — Special IP addresses for routers, network devices, etc.
Swarm nodes — IP addresses used for storage processes
Following are two scenarios for managed IP addresses:
Storage subnet |
| (255.255.255.0) |
Set of all IP addresses |
| (254 addresses) |
Platform Server's IP |
| (1 address) |
Dynamic Range (via |
| (55 addresses) |
Reserved Range (via |
| (9 addresses) |
IP addresses available for Storage nodes |
| (189 addresses) |
Implications:
There can be 189 Storage nodes on the network
55 chassis can go through enlistment/commissioning at a time
Storage subnet |
| (255.255.0.0) |
Set of all IP addresses |
| (65,534 addresses) |
Platform Server's IP |
| (1 address) |
Dynamic Range (via |
| (100 addresses) |
Reserved Range (via |
| (9 addresses) |
IP addresses available for Storage nodes |
| (65,424 addresses) |
Implications:
There can be 65,424 Storage nodes on the network
100 chassis can go through enlistment/commissioning at a time