openstack/openstack-manuals
Code Issues Proposed changes
4082ba0fea
openstack-manuals/doc/install-guide/source/environment-networking.rst

128 lines
5.5 KiB
ReStructuredText
Raw Normal View History

[install] Fix environment structure 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
2015-10-05 13:39:48 -05:00
Host networking
[install] Initial networking architecture changes Implement initial networking architecture changes for Liberty as follows: 1) Remove nova-network. 2) Develop architecture for provider networks with Linux bridge agent. 3) Develop architecture for self-service networks with Linux bridge agent. 4) Munge the neutron controller and network node configuration together. 5) Rejigger neutron to use the Linux bridge agent. 6) Restructure launch an instance content to account for two networking options. 7) Other restructuring as necessary to meet the primary goal. For simplicity, both architectures require only two nodes, each with two network interfaces, to deploy core OpenStack services. Also, to address recurring issues about the lack of support for connecting instances directly to the public/external network, the self-service architecture augments the provider networks architecture which allows connection to both private and public networks. Change-Id: Ie3ab9a15ebfe82c0ce54f709c87a66d7cc46db3f Implements: blueprint installguide-liberty
2015-09-08 13:38:37 -05:00
~~~~~~~~~~~~~~~
.. only:: 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 <https://help.ubuntu.com/lts/serverguide/network-configuration.html>`__ .
.. only:: 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 <https://wiki.debian.org/NetworkConfiguration>`__ .
.. only:: 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 <https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Networking_Guide/sec-Using_the_Command_Line_Interface.html>`__ .
.. only:: 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 <https://www.suse.com/documentation/sles-12/book_sle_admin/data/sec_basicnet_manconf.html>`__ or `openSUSE <http://activedoc.opensuse.org/book/opensuse-reference/chapter-13-basic-networking>`__ documentation.
All nodes require Internet access for administrative purposes such as package
installation, security updates, :term:`DNS`, and :term:`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` 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 :term:`NAT`.
.. _figure-networklayout:
.. figure:: figures/networklayout.png
:alt: Network layout
The example architectures assume use of the following networks:
Install guide, Basic Env, networking, ntp -Converts networking and ntp sections in Basic Environment chapter from DocBook to RST. Change-Id: Ic810327ebefff94eeaad0bc45de8cb442d4629be Implements: blueprint installguide-liberty
2015-07-21 13:40:26 -04:00
- 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,
[install] Initial networking architecture changes Implement initial networking architecture changes for Liberty as follows: 1) Remove nova-network. 2) Develop architecture for provider networks with Linux bridge agent. 3) Develop architecture for self-service networks with Linux bridge agent. 4) Munge the neutron controller and network node configuration together. 5) Rejigger neutron to use the Linux bridge agent. 6) Restructure launch an instance content to account for two networking options. 7) Other restructuring as necessary to meet the primary goal. For simplicity, both architectures require only two nodes, each with two network interfaces, to deploy core OpenStack services. Also, to address recurring issues about the lack of support for connecting instances directly to the public/external network, the self-service architecture augments the provider networks architecture which allows connection to both private and public networks. Change-Id: Ie3ab9a15ebfe82c0ce54f709c87a66d7cc46db3f Implements: blueprint installguide-liberty
2015-09-08 13:38:37 -05:00
security updates, :term:`DNS`, and :term:`NTP`.
Install guide, Basic Env, networking, ntp -Converts networking and ntp sections in Basic Environment chapter from DocBook to RST. Change-Id: Ic810327ebefff94eeaad0bc45de8cb442d4629be Implements: blueprint installguide-liberty
2015-07-21 13:40:26 -04:00
[install] Initial networking architecture changes Implement initial networking architecture changes for Liberty as follows: 1) Remove nova-network. 2) Develop architecture for provider networks with Linux bridge agent. 3) Develop architecture for self-service networks with Linux bridge agent. 4) Munge the neutron controller and network node configuration together. 5) Rejigger neutron to use the Linux bridge agent. 6) Restructure launch an instance content to account for two networking options. 7) Other restructuring as necessary to meet the primary goal. For simplicity, both architectures require only two nodes, each with two network interfaces, to deploy core OpenStack services. Also, to address recurring issues about the lack of support for connecting instances directly to the public/external network, the self-service architecture augments the provider networks architecture which allows connection to both private and public networks. Change-Id: Ie3ab9a15ebfe82c0ce54f709c87a66d7cc46db3f Implements: blueprint installguide-liberty
2015-09-08 13:38:37 -05:00
- Public on 203.0.113.0/24 with gateway 203.0.113.1
Install guide, Basic Env, networking, ntp -Converts networking and ntp sections in Basic Environment chapter from DocBook to RST. Change-Id: Ic810327ebefff94eeaad0bc45de8cb442d4629be Implements: blueprint installguide-liberty
2015-07-21 13:40:26 -04:00
.. 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.
[install] Initial networking architecture changes Implement initial networking architecture changes for Liberty as follows: 1) Remove nova-network. 2) Develop architecture for provider networks with Linux bridge agent. 3) Develop architecture for self-service networks with Linux bridge agent. 4) Munge the neutron controller and network node configuration together. 5) Rejigger neutron to use the Linux bridge agent. 6) Restructure launch an instance content to account for two networking options. 7) Other restructuring as necessary to meet the primary goal. For simplicity, both architectures require only two nodes, each with two network interfaces, to deploy core OpenStack services. Also, to address recurring issues about the lack of support for connecting instances directly to the public/external network, the self-service architecture augments the provider networks architecture which allows connection to both private and public networks. Change-Id: Ie3ab9a15ebfe82c0ce54f709c87a66d7cc46db3f Implements: blueprint installguide-liberty
2015-09-08 13:38:37 -05:00
.. note::
.. only:: rdo or obs
Your distribution enables a restrictive :term:`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 <http://docs.openstack.org/sec/>`__.
.. only:: ubuntu or debian
Your distribution does not enable a restrictive :term:`firewall`
by default. For more information about securing your environment,
refer to the
`OpenStack Security Guide <http://docs.openstack.org/sec/>`__.
[install] Fix environment structure 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
2015-10-05 13:39:48 -05:00
.. toctree::
:maxdepth: 1
environment-networking-controller.rst
environment-networking-compute.rst
[install] Liberty updates for cinder 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
2015-10-12 11:06:28 -06:00
environment-networking-storage-cinder.rst
[install] Liberty updates for swift Update swift configuration for Liberty. Includes moving basic host configuration of object storage nodes 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: I00c9f9fbc3700ebf0423a4c1ac92ff6863852df6 Implements: blueprint installguide-liberty
2015-10-06 16:35:02 -06:00
environment-networking-storage-swift.rst
[install] Fix environment structure 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
2015-10-05 13:39:48 -05:00
environment-networking-verify.rst
Copy Permalink