The hardware requirements are based on the number of VMs used for each component. For example, two VMs are used for load balancing, each of which requires two vCPUs for a total requirement of four vCPUs.
Core VMware Integrated OpenStack Components
Component |
VMs |
vCPU |
vRAM (GB) |
vDisk Space (GB) |
|---|---|---|---|---|
Integrated OpenStack Manager |
1 |
4 (4 per VM) |
4 (4 per VM) |
25 |
Load balancing service |
2 |
4 (2 per VM) |
8 (4 per VM) |
40 (20 per VM) |
Database service |
3 |
12 (4 per VM) |
48 (16 per VM) |
240 (80 per VM) |
Controllers |
2 |
16 (8 per VM) |
32 (16 per VM) |
160 (80 per VM) |
Compute service (Nova CPU) |
1 |
2 (2 per VM) |
4 (4 per VM) |
20 (20 per VM) |
Ceilometer |
1 |
2 (2 per VM) |
4 (4 per VM) |
20 (20 per VM) |
Database (MongoDB or NoSQL) for Ceilometer |
3 |
6 (2 per VM) |
12 (4 per VM) |
60 (20 per VM) |
TOTAL |
13 |
46 |
112 |
565 |
The optional Object Storage (Swift) is installed separately post-installation and is not included in the above requirements. See Adding OpenStack Components and Features.
NSX Components
Additional CPU, RAM, and disk space is required for NSX components if they are deployed with VMware Integrated OpenStack. It is a best practice to deploy the NSX Manager and NSX Controller nodes in the Management cluster.
Component |
VMs |
vCPU |
vRAM (GB) |
vDisk Space (GB) |
|---|---|---|---|---|
NSX Controller |
3 |
12 (4 per VM) |
12 (4 per VM) |
60 (20 per VM) |
NSX Manager |
1 |
4 (4 per VM) |
12 (12 per VM) |
60 (60 per VM) |
NSX Edge (see note below) |
Varies: created on demand. |
1 per Edge DHCP VM, 2 per Edge router VM |
0.5 per Edge DHCP VM, 1 per Edge router VM |
0.5 per Edge DHCP VM, 1 per Edge router VM |
TOTAL |
4 plus Edge requirements |
16 plus Edge requirements |
24 plus Edge requirements |
120 plus Edge requirements |
When you create a logical subnet or logical router, a new Edge VM is dynamically created to serve this request if an existing Edge node cannot.
