openstack/openstack-manuals
Code Issues Proposed changes
820d50f4d4
openstack-manuals/doc/ha-guide/source/environment-hardware.rst
KATO Tomoyuki d1fe08b4a7 [ha-guide] Reorganize basic services content 
To sync with installation guides.

Change-Id: Ia4df2bdb1f058bb3d8bcf035160463134d115384
Implements: blueprint improve-ha-guide
2016-05-24 07:17:39 +09:00

2.1 KiB
Raw Blame History

Hardware considerations for high availability

[TODO: Provide a minimal architecture example for HA, expanded on that given in http://docs.openstack.org/mitaka/install-guide-ubuntu/environment.html for easy comparison]

Hardware setup

The standard hardware requirements:

However, OpenStack does not require a significant amount of resources and the following minimum requirements should support a proof-of-concept high availability environment with core services and several instances:

[TODO: Verify that these numbers are good]

Node type Processor Memory Storage NIC
controller node 1-2 8 GB 100 GB 2
compute node 2-4+ 8+ GB 100+ GB 2

For demonstrations and studying, you can set up a test environment on virtual machines (VMs). This has the following benefits:

  • One physical server can support multiple nodes, each of which supports almost any number of network interfaces.
  • Ability to take periodic "snap shots" throughout the installation process and "roll back" to a working configuration in the event of a problem.

However, running an OpenStack environment on VMs degrades the performance of your instances, particularly if your hypervisor and/or processor lacks support for hardware acceleration of nested VMs.

Note

When installing highly-available OpenStack on VMs, be sure that your hypervisor permits promiscuous mode and disables MAC address filtering on the external network.