Install: Environment updates for Mitaka
Update environment configuration for Mitaka to account for changes to network nomenclature. Implements: bp installguide-mitaka Change-Id: I9a20e18f66425e5968fefebb8901eac82fb212af
|
@ -16,8 +16,8 @@ Configure network interfaces
|
|||
|
||||
Additional compute nodes should use 10.0.0.32, 10.0.0.33, and so on.
|
||||
|
||||
#. The public interface uses a special configuration without an IP
|
||||
address assigned to it. Configure the second interface as the public
|
||||
#. The provider interface uses a special configuration without an IP
|
||||
address assigned to it. Configure the second interface as the provider
|
||||
interface:
|
||||
|
||||
Replace ``INTERFACE_NAME`` with the actual interface name. For example,
|
||||
|
@ -29,7 +29,7 @@ Configure network interfaces
|
|||
|
||||
.. code-block:: ini
|
||||
|
||||
# The public network interface
|
||||
# The provider network interface
|
||||
auto INTERFACE_NAME
|
||||
iface INTERFACE_NAME inet manual
|
||||
up ip link set dev $IFACE up
|
||||
|
|
|
@ -12,8 +12,8 @@ Configure network interfaces
|
|||
|
||||
Default gateway: 10.0.0.1
|
||||
|
||||
#. The public interface uses a special configuration without an IP
|
||||
address assigned to it. Configure the second interface as the public
|
||||
#. The provider interface uses a special configuration without an IP
|
||||
address assigned to it. Configure the second interface as the provider
|
||||
interface:
|
||||
|
||||
Replace ``INTERFACE_NAME`` with the actual interface name. For example,
|
||||
|
@ -25,9 +25,9 @@ Configure network interfaces
|
|||
|
||||
.. code-block:: ini
|
||||
|
||||
# The public network interface
|
||||
# The provider network interface
|
||||
auto INTERFACE_NAME
|
||||
iface INTERFACE_NAME inet manual
|
||||
iface INTERFACE_NAME inet manual
|
||||
up ip link set dev $IFACE up
|
||||
down ip link set dev $IFACE down
|
||||
|
||||
|
|
|
@ -44,13 +44,15 @@ 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`.
|
||||
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` through the provider network.
|
||||
|
||||
.. _figure-networklayout:
|
||||
|
||||
|
@ -65,7 +67,7 @@ The example architectures assume use of the following networks:
|
|||
nodes for administrative purposes such as package installation,
|
||||
security updates, :term:`DNS`, and :term:`NTP`.
|
||||
|
||||
* Public on 203.0.113.0/24 with gateway 203.0.113.1
|
||||
* 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.
|
||||
|
|
|
@ -64,7 +64,7 @@ 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
|
||||
a way to disable MAC address filtering on the provider network
|
||||
interface.
|
||||
|
||||
For more information about system requirements, see the `OpenStack
|
||||
|
|
Before Width: | Height: | Size: 105 KiB After Width: | Height: | Size: 41 KiB |
Before Width: | Height: | Size: 41 KiB After Width: | Height: | Size: 39 KiB |
Before Width: | Height: | Size: 148 KiB After Width: | Height: | Size: 76 KiB |
Before Width: | Height: | Size: 44 KiB After Width: | Height: | Size: 47 KiB |
Before Width: | Height: | Size: 156 KiB After Width: | Height: | Size: 77 KiB |
Before Width: | Height: | Size: 46 KiB After Width: | Height: | Size: 48 KiB |
Before Width: | Height: | Size: 101 KiB After Width: | Height: | Size: 52 KiB |
Before Width: | Height: | Size: 24 KiB After Width: | Height: | Size: 22 KiB |
|
@ -118,7 +118,7 @@ follows:
|
|||
* Networking agents reside on the controller node instead of one or more
|
||||
dedicated network nodes.
|
||||
|
||||
* Overlay (tunnel) traffic for private networks traverses the management
|
||||
* Overlay (tunnel) traffic for self-service networks traverses the management
|
||||
network instead of a dedicated network.
|
||||
|
||||
For more information on production architectures, see the
|
||||
|
@ -205,7 +205,7 @@ IP address information to instances.
|
|||
|
||||
.. note::
|
||||
|
||||
This option lacks support for self-service private networks, layer-3
|
||||
This option lacks support for self-service (private) networks, layer-3
|
||||
(routing) services, and advanced services such as :term:`LBaaS` and
|
||||
:term:`FWaaS`. Consider the self-service networks option if you
|
||||
desire these features.
|
||||
|
|