69 lines
3.3 KiB
Plaintext
69 lines
3.3 KiB
Plaintext
|
|
Before You Start
|
|
----------------
|
|
|
|
Before you begin your installation, you will need to make a number of
|
|
important decisions:
|
|
|
|
**OpenStack features**
|
|
Your first decision is to decide which of the
|
|
optional OpenStack features you will need. For example, you must decide
|
|
whether you want to install Swift, whether you want Glance to use Swift for
|
|
image storage, whether you want Cinder for block storage, and whether you
|
|
want nova-network or Neutron (formerly Quantum) to handle your network
|
|
connectivity. In our example installation we will be installing Glance with
|
|
Swift support and Cinder for block storage. Also, due to the fact that it
|
|
can be easily installed using orchestration, we will be using Neutron.
|
|
|
|
**Deployment configuration**
|
|
Next, you need to decide whether your
|
|
deployment requires high availability (HA). If you need HA for your
|
|
deployment, you have a choice regarding the number of controllers you want
|
|
to include. Following the recommendations in the previous section for a
|
|
typical HA deployment configuration, we will use three OpenStack controllers.
|
|
|
|
**Cobbler server and Puppet Master.**
|
|
The heart of any Fuel install is the
|
|
combination of Puppet Master and Cobbler used to create your resources.
|
|
Although Cobbler and Puppet Master can be installed on separate machines, it
|
|
is common practice to install both on a single machine for small to medium
|
|
size clouds, and that's what we'll be doing in this example. By default, the
|
|
Fuel ISO creates a single server with both services.
|
|
|
|
**Domain name.**
|
|
Puppet clients generate a Certificate Signing Request
|
|
(CSR), which is then signed by the Puppet Master. The signed certificate can
|
|
then be used to authenticate clients during provisioning. Certificate
|
|
generation requires a fully qualified hostname, so you must choose a domain
|
|
name to be used in your installation. Future versions of Fuel will enable
|
|
you to choose this domain name on your own; by default, Fuel 3.1 uses
|
|
``localdomain``.
|
|
|
|
**Network addresses.**
|
|
OpenStack requires a minimum of three networks. If
|
|
you are deploying on physical hardware, two of them -- the public network
|
|
and the internal, or management network -- must be routable in your
|
|
networking infrastructure. The third network is used by the nodes for
|
|
inter-node communications. Also, if you intend for your environment to be
|
|
accessible from the Internet, you'll want the public network to be on the
|
|
proper network segment. For simplicity in this case, this example assumes
|
|
an Internet router at 192.168.0.1. Additionally, a set of private network
|
|
addresses should be selected for automatic assignment to guest VMs. (These
|
|
are fixed IPs for the private network). In our case, we are allocating
|
|
network addresses as follows:
|
|
|
|
* Public network: 192.168.0.0/24
|
|
* Internal network: 10.0.0.0/24
|
|
* Private network: 10.0.1.0/24
|
|
|
|
**Network interfaces.**
|
|
All of those networks need to be assigned to the
|
|
available NIC cards on the allocated machines. Additionally, if a fourth NIC
|
|
is available, Cinder or block storage traffic can be separated and delegated
|
|
to the fourth NIC. In our case, we're assigning networks as follows:
|
|
|
|
* Public network: eth1
|
|
* Internal network: eth0
|
|
* Private network: eth2
|
|
|