From 7e8d629108605930d6fdacebba07c03024012ce3 Mon Sep 17 00:00:00 2001 From: Jean-Philippe Evrard Date: Wed, 4 May 2016 11:03:13 +0100 Subject: [PATCH] Doc: Configuring the network refactor For better understanding and avoiding inconsistencies, this commit removes focuses on a consistent network configuration explanation, with 2 paths for the deployer: - The reference "path" - The single host "path" Each path is explained the same way, this way the deployers know how to follow the path. Closes-bug: #1547598 Change-Id: I6e187ab5d88f1387876012d4f40f96205cc7a6ee Signed-off-by: Jean-Philippe Evrard --- .../install-guide/targethosts-network.rst | 8 +-- .../targethosts-networkconfig.rst | 21 ++++++ .../targethosts-networkexample.rst | 6 +- .../targethosts-networkrefarch.rst | 64 +++++++++++++++++++ doc/source/install-guide/targethosts.rst | 4 +- 5 files changed, 93 insertions(+), 10 deletions(-) create mode 100644 doc/source/install-guide/targethosts-networkconfig.rst diff --git a/doc/source/install-guide/targethosts-network.rst b/doc/source/install-guide/targethosts-network.rst index c4ffb98732..96306ba7dc 100644 --- a/doc/source/install-guide/targethosts-network.rst +++ b/doc/source/install-guide/targethosts-network.rst @@ -1,8 +1,8 @@ `Home `_ OpenStack-Ansible Installation Guide -======================= -Configuring the network -======================= +===================== +Designing the network +===================== This section describes the recommended network architecture. Some components are mandatory, such as the bridges described below. We @@ -10,7 +10,7 @@ recommend other components such as a bonded network interface but this is not a requirement. .. important:: - + Follow the reference design as closely as possible for production deployments. Although Ansible automates most deployment operations, networking on diff --git a/doc/source/install-guide/targethosts-networkconfig.rst b/doc/source/install-guide/targethosts-networkconfig.rst new file mode 100644 index 0000000000..9440e66e92 --- /dev/null +++ b/doc/source/install-guide/targethosts-networkconfig.rst @@ -0,0 +1,21 @@ +`Home `_ OpenStack-Ansible Installation Guide + +================= +Configuring hosts +================= + + +With the information available on the design guide page, you are now +able to make the decisions to build your own OpenStack. There +are two examples given here: reference architecture (recommended) and +single host architecture (simple). + +.. toctree:: + + targethosts-networkrefarch.rst + targethosts-networkexample.rst + + +-------------- + +.. include:: navigation.txt diff --git a/doc/source/install-guide/targethosts-networkexample.rst b/doc/source/install-guide/targethosts-networkexample.rst index 408e13aebf..58980ba069 100644 --- a/doc/source/install-guide/targethosts-networkexample.rst +++ b/doc/source/install-guide/targethosts-networkexample.rst @@ -1,8 +1,8 @@ `Home `_ OpenStack-Ansible Installation Guide -=================================================================================== -Configuring the network on a target host: Simple architecture: A single target host -=================================================================================== +========================================= +Simple architecture: A single target host +========================================= Overview ~~~~~~~~ diff --git a/doc/source/install-guide/targethosts-networkrefarch.rst b/doc/source/install-guide/targethosts-networkrefarch.rst index 151966cbeb..88ae84197d 100644 --- a/doc/source/install-guide/targethosts-networkrefarch.rst +++ b/doc/source/install-guide/targethosts-networkrefarch.rst @@ -4,6 +4,35 @@ Reference architecture ====================== +Overview +~~~~~~~~ + +This example allows you to use your own parameters for the deployment. + +The following is a table of the bridges that are be configured on hosts, if you followed the +previously proposed design. + ++-------------+-----------------------+-------------------------------------+ +| Bridge name | Best configured on | With a static IP | ++=============+=======================+=====================================+ +| br-mgmt | On every node | Always | ++-------------+-----------------------+-------------------------------------+ +| | On every storage node | When component is deployed on metal | ++ br-storage +-----------------------+-------------------------------------+ +| | On every compute node | Always | ++-------------+-----------------------+-------------------------------------+ +| | On every network node | When component is deployed on metal | ++ br-vxlan +-----------------------+-------------------------------------+ +| | On every compute node | Always | ++-------------+-----------------------+-------------------------------------+ +| | On every network node | Never | ++ br-vlan +-----------------------+-------------------------------------+ +| | On every compute node | Never | ++-------------+-----------------------+-------------------------------------+ + +Modifying the network interfaces file +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + After establishing initial host management network connectivity using the ``bond0`` interface, modify the ``/etc/network/interfaces`` file as described in the following procedure. @@ -136,6 +165,41 @@ described in the following procedure. ``*_BRIDGE_NETMASK``, ``*_BRIDGE_DNS_SERVERS`` with the appropriate configuration for the environment. +Example for 3 controller nodes and 2 compute nodes +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +- VLANs: + + - Host management: Untagged/Native + - Container management: 10 + - Tunnels: 30 + - Storage: 20 + +- Networks: + + - Host management: 10.240.0.0/22 + - Container management: 172.29.236.0/22 + - Tunnel: 172.29.240.0/22 + - Storage: 172.29.244.0/22 + +- Addresses for the controller nodes: + + - Host management: 10.240.0.11 - 10.240.0.13 + - Host management gateway: 10.240.0.1 + - DNS servers: 69.20.0.164 69.20.0.196 + - Container management: 172.29.236.11 - 172.29.236.13 + - Tunnel: no IP (because IP exist in the containers, when the components aren't deployed directly on metal) + - Storage: no IP (because IP exist in the containers, when the components aren't deployed directly on metal) + +- Addresses for the compute nodes: + + - Host management: 10.240.0.21 - 10.240.0.22 + - Host management gateway: 10.240.0.1 + - DNS servers: 69.20.0.164 69.20.0.196 + - Container management: 172.29.236.21 - 172.29.236.22 + - Tunnel: 172.29.240.21 - 172.29.240.22 + - Storage: 172.29.244.21 - 172.29.244.22 + -------------- .. include:: navigation.txt diff --git a/doc/source/install-guide/targethosts.rst b/doc/source/install-guide/targethosts.rst index ccc055cefd..075dce1b45 100644 --- a/doc/source/install-guide/targethosts.rst +++ b/doc/source/install-guide/targethosts.rst @@ -8,9 +8,7 @@ Chapter 3. Target hosts targethosts-prepare.rst targethosts-network.rst - targethosts-networkrefarch.rst - targethosts-networkexample.rst - + targethosts-networkconfig.rst **Figure 3.1. Installation workflow**