677d910899
Address various structure and consistency issues with environment content. This patch only addresses the critical structure and consistency problems that impact usability. A future patch should address the larger, but less obvious problems that mostly appeared during the RST conversion. Change-Id: Iae586b4cc8943abedca3c09820d0fb5370b5a858 Implements: blueprint installguide-liberty
3.0 KiB
Environment
Note
The draft version of this guide focuses on the future Liberty release and will not work for the current Kilo release. If you want to install Kilo, you must use the Kilo version of this guide instead.
This section explains how to configure the controller and one compute node using the example architecture.
Although most environments include Identity, Image service, Compute,
at least one networking service, and the dashboard, the Object Storage
service can operate independently. If your use case only involves Object
Storage, you can skip to swift after configuring the appropriate nodes for it.
However, the dashboard requires at least the Image service, Compute, and
Networking.
You must use an account with administrative privileges to configure
each node. Either run the commands as the root user or
configure the sudo utility.
obs
The systemctl enable call on openSUSE outputs a
warning message when the service uses SysV Init scripts instead of
native systemd files. This warning can be ignored.
For best performance, we recommend that your environment meets or
exceeds the hardware requirements in figure-hwreqs. However, OpenStack does not require a
significant amount of resources and the following minimum requirements
should support a proof-of-concept environment with core services and
several CirrOS
instances:
- Controller Node: 1 processor, 2 GB memory, and 5 GB storage
- Compute Node: 1 processor, 2 GB memory, and 10 GB storage
To minimize clutter and provide more resources for OpenStack, we recommend a minimal installation of your Linux distribution. Also, you must install a 64-bit version of your distribution on each node.
A single disk partition on each node works for most basic
installations. However, you should consider Logical Volume Manager (LVM)
for installations with optional services such as Block Storage.
For first-time installation and testing purposes, many users elect to
build each host as a virtual machine (VM). The primary benefits of VMs
include the following:
- One physical server can support multiple nodes, each with 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, VMs will reduce performance of your instances, particularly if your hypervisor and/or processor lacks support for hardware acceleration of nested VMs.
Note
If you choose to install on VMs, make sure your hypervisor provides a
way to disable MAC address filtering on the public network
interface.
For more information about system requirements, see the OpenStack Operations Guide.
environment-security.rst environment-networking.rst environment-ntp.rst environment-dependencies.rst