Precise hardware requirements can only be listed for the Administration Server and the OpenStack Control Node. The requirements of the OpenStack Compute and Storage Nodes depends on the number of concurrent instances and their virtual hardware equipment.
A minimum of three machines are required for a SUSE OpenStack Cloud: one Administration Server, one Control Node, and one Compute Node. You also need a gateway providing access to the public network. Deploying storage requires additional nodes: at least two nodes for Swift and a minimum of four nodes for Ceph.
IMPORTANT: Virtual/Physical Machines and Architecture
Deploying SUSE OpenStack Cloud functions to virtual machines is only supported for the Administration Server—all other nodes need to be physical hardware. Although the Control Node can be virtualized in test environments, this is not supported for production systems.
SUSE OpenStack Cloud currently only runs on x86_64 hardware.
RAM: at least 4 GB, 8 GB recommended. The demand for memory depends on the total number of nodes in SUSE OpenStack Cloud—the higher the number of nodes, the more RAM is needed. A deployment with 50 nodes requires a minimum of 24 GB RAM for each Control Node.
Hard disk: at least 50 GB. We recommend putting /srv on a separate partition with at least additional 30 GB of space. Alternatively, you can mount the update repositories from another server (see Section 2.5.2, Product and Update Repositories for details).
Number of network cards: 1 for single and dual mode, 2 or more for team mode. Additional networks such as the bastion network and/or a separate BMC network each need an additional network card. See Section 2.1, Network for details.
Can be deployed on physical hardware or a virtual machine.
The Compute Nodes need to be equipped with a sufficient amount of RAM
and CPUs, matching the numbers required by the maximum number of
instances running concurrently. An instance started in
SUSE OpenStack Cloud cannot share resources from several physical nodes. It uses
the resources of the node on which it was started. So if you
offer a flavor (see Flavor
The compute, memory, and storage capacity of nova
computing instances (in terms of virtual CPUs, RAM, etc.). Flavors can
be thought of as
templates for the amount of cloud
resources that are assigned to an instance.
for a definition)
with 8 CPUs and 12 GB RAM, at least one of your nodes should be able to
provide these resources. Add 1 GB RAM for every two nodes
(including Control Nodes and Storage Nodes) deployed in your cloud.
See Compute Nodes for storage requirements.
Usually a single CPU and a minimum of 4 GB RAM are sufficient for the Storage Nodes. Memory requirements increase depending on the total number of nodes in SUSE OpenStack Cloud—the higher the number of nodes, the more RAM you need. A deployment with 50 nodes requires a minimum of 20 GB for each Storage Node. If you use Ceph as storage, the storage nodes should be equipped with an additional 2 GB RAM per OSD (Ceph object storage daemon).
For storage requirements, see Storage Nodes (optional).
The Monasca Node is a dedicated physical machine that runs the monasca-server role. This node is used for SUSE OpenStack Cloud Crowbar Monitoring. Hardware requirements for the Monasca Node are as follows:
RAM: At least 32 GB, 64 GB or more is recommended
CPU: At least 8 cores, 16 cores or more is recommended
Hard Disk: SSD is strongly recommended
The following formula can be used to calculate the required disk space:
200 GB + ["number of nodes" * "retention period" * ("space for log data/day" + "space for metrics data/day") ]
The recommended values for the formula are as follows:
Retention period = 60 days for InfluxDB and Elasticsearch
Space for daily log data = 2GB
Space for daily metrics data = 50MB
The formula is based on the following log data assumptions:
Approximately 50 log files per node
Approximately 1 log entry per file per sec
200 bytes in size
The formula is based on the following metrics data assumptions:
400 metrics per node
Time interval of 30 seconds
20 bytes in size
The formula provides only a rough estimation of the required disk space. There are several factors that can affect disk space requirements. This includes the exact combination of services that run on your OpenStack node actual cloud usage pattern, and whether any or all services have debug logging enabled.