Update cinder configuration for Liberty. Includes moving basic host configuration of the block storage node to environment section. Also addresses some consistency issues, mostly from the RST conversion. Changes and testing specific to distribution packages primarily involve Ubuntu. Other distributions may require additional patches. Change-Id: I8915bc5fad5d278fd73899476bf6d90970d18564 Implements: bp installguide-liberty
5.5 KiB
Host networking
ubuntu
After installing the operating system on each node for the architecture that you choose to deploy, you must configure the network interfaces. We recommend that you disable any automated network management tools and manually edit the appropriate configuration files for your distribution. For more information on how to configure networking on your distribution, see the documentation .
debian
After installing the operating system on each node for the architecture that you choose to deploy, you must configure the network interfaces. We recommend that you disable any automated network management tools and manually edit the appropriate configuration files for your distribution. For more information on how to configure networking on your distribution, see the documentation .
rdo
After installing the operating system on each node for the architecture that you choose to deploy, you must configure the network interfaces. We recommend that you disable any automated network management tools and manually edit the appropriate configuration files for your distribution. For more information on how to configure networking on your distribution, see the documentation .
obs
After installing the operating system on each node for the architecture that you choose to deploy, you must configure the network interfaces. We recommend that you disable any automated network management tools and manually edit the appropriate configuration files for your distribution. For more information on how to configure networking on your distribution, see the SLES 12 or openSUSE documentation.
All nodes require Internet access for administrative purposes such as
package installation, security updates, DNS
, and NTP
. In most cases, nodes should obtain internet
access through the management network interface. To highlight the
importance of network separation, the example architectures use private address space for
the management network and assume that the physical network
infrastructure provides Internet access via NAT
or other method. The
example architectures use routable IP address space for the public
network and assume that the physical network infrastructure provides
direct Internet access. In the provider networks architecture, all
instances attach directly to the public network. In the self-service
networks architecture, instances can attach to a private or public
network. Private networks can reside entirely within OpenStack or
provide some level of public network access using NAT
.
The example architectures assume use of the following networks:
Management on 10.0.0.0/24 with gateway 10.0.0.1
Note
This network requires a gateway to provide Internet access to all nodes for administrative purposes such as package installation, security updates,
DNS
, andNTP
.Public on 203.0.113.0/24 with gateway 203.0.113.1
Note
This network requires a gateway to provide Internet access to instances in your OpenStack environment.
You can modify these ranges and gateways to work with your particular network infrastructure.
Note
Network interface names vary by distribution. Traditionally, interfaces use "eth" followed by a sequential number. To cover all variations, this guide simply refers to the first interface as the interface with the lowest number and the second interface as the interface with the highest number.
Unless you intend to use the exact configuration provided in this
example architecture, you must modify the networks in this procedure to
match your environment. Also, each node must resolve the other nodes by
name in addition to IP address. For example, the controller
name must resolve to 10.0.0.11
, the IP address of the
management interface on the controller node.
Warning
Reconfiguring network interfaces will interrupt network connectivity. We recommend using a local terminal session for these procedures.
Note
rdo or obs
Your distribution enables a restrictive firewall
by default. During
the installation process, certain steps will fail unless you alter or
disable the firewall. For more information about securing your
environment, refer to the OpenStack Security Guide.
ubuntu or debian
Your distribution does not enable a restrictive firewall
by default. For
more information about securing your environment, refer to the OpenStack Security Guide.
environment-networking-controller.rst environment-networking-compute.rst environment-networking-storage-cinder.rst environment-networking-storage-swift.rst environment-networking-verify.rst