e39304d4ae
The PDF build does not include content multiple times if the same file is included in a toctree more than once. That means we need to restructure the guide to handle the common parts differently. This approach merges some of the previously split sections back together using inline prose to indicate where minor variations apply for different operating systems but retaining separate files for cases where the differences are significant. Change-Id: I5d9ff549b05ca4ce54486719d70858589b8fcfa3 Depends-On: Ia750cb049c0f53a234ea70ce1f2bbbb7a2aa9454 Signed-off-by: Doug Hellmann <doug@doughellmann.com>
101 lines
4.2 KiB
ReStructuredText
101 lines
4.2 KiB
ReStructuredText
.. _environment-networking:
|
|
|
|
Host networking
|
|
~~~~~~~~~~~~~~~
|
|
|
|
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.
|
|
|
|
.. seealso::
|
|
|
|
* `Debian Network Configuration <https://wiki.debian.org/NetworkConfiguration>`__
|
|
* `Ubuntu Network Configuration
|
|
<https://help.ubuntu.com/lts/serverguide/network-configuration.html>`__
|
|
* `Red Hat Network Configuration
|
|
<https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Networking_Guide/sec-Using_the_Command_Line_Interface.html>`__
|
|
* `SLES 12
|
|
<https://www.suse.com/documentation/sles-12/book_sle_admin/data/sec_basicnet_manconf.html>`__
|
|
or `openSUSE
|
|
<https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.reference/cha.basicnet.html>`__ Network Configuration
|
|
|
|
All nodes require Internet access for administrative purposes such as package
|
|
installation, security updates, :term:`DNS <Domain Name System (DNS)>`, and
|
|
:term:`NTP <Network Time Protocol (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 <https://tools.ietf.org/html/rfc1918>`__ for the
|
|
management network and assume that the physical network infrastructure
|
|
provides Internet access via :term:`NAT <Network Address Translation (NAT)>`
|
|
or other methods. The example architectures use routable IP address space for
|
|
the provider (external) network and assume that the physical network
|
|
infrastructure provides direct Internet access.
|
|
|
|
In the provider networks architecture, all instances attach directly
|
|
to the provider network. In the self-service (private) networks architecture,
|
|
instances can attach to a self-service or provider network. Self-service
|
|
networks can reside entirely within OpenStack or provide some level of external
|
|
network access using :term:`NAT <Network Address Translation (NAT)>` through
|
|
the provider network.
|
|
|
|
.. _figure-networklayout:
|
|
|
|
.. figure:: figures/networklayout.png
|
|
:alt: Network layout
|
|
|
|
The example architectures assume use of the following networks:
|
|
|
|
* Management on 10.0.0.0/24 with gateway 10.0.0.1
|
|
|
|
This network requires a gateway to provide Internet access to all
|
|
nodes for administrative purposes such as package installation,
|
|
security updates, :term:`DNS <Domain Name System (DNS)>`, and
|
|
:term:`NTP <Network Time Protocol (NTP)>`.
|
|
|
|
* Provider on 203.0.113.0/24 with gateway 203.0.113.1
|
|
|
|
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.
|
|
|
|
Network interface names vary by distribution. Traditionally,
|
|
interfaces use ``eth`` followed by a sequential number. To cover all
|
|
variations, this guide 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. 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::
|
|
|
|
Red Hat and SUSE distributions enable a restrictive
|
|
:term:`firewall` by default. Ubuntu and Debian do not. For more
|
|
information about securing your environment, refer to the
|
|
`OpenStack Security Guide
|
|
<https://docs.openstack.org/security-guide/>`_.
|
|
|
|
|
|
.. toctree::
|
|
:maxdepth: 1
|
|
|
|
environment-networking-controller.rst
|
|
environment-networking-compute.rst
|
|
environment-networking-storage-cinder.rst
|
|
environment-networking-verify.rst
|