openstack
/
fuel-docs
Code Issues Proposed changes

Edited Fuel Pre-Installation Guide

This commit is contained in:
Svetlana Sychova 2013-10-31 18:35:14 -07:00 committed by Matthew Mosesohn
parent 0600459864
commit a986b81e4c
18 changed files with 230 additions and 461 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

0
_images/image11.jpg → _images/preinstall_d_flat_dhcp.jpg
View File

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 86 KiB

After

Width:  |  Height:  |  Size: 86 KiB

0
_images/image09.png → _images/preinstall_d_gre_2nics.png
View File

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 9.8 KiB

After

Width:  |  Height:  |  Size: 9.8 KiB

0
_images/image13.png → _images/preinstall_d_gre_3nics.png
View File

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 9.7 KiB

After

Width:  |  Height:  |  Size: 9.7 KiB

0
_images/image21.png → _images/preinstall_d_gre_4nics.png
View File

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 8.9 KiB

After

Width:  |  Height:  |  Size: 8.9 KiB

0
_images/image01.jpg → _images/preinstall_d_gre_segm.jpg
View File

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 113 KiB

After

Width:  |  Height:  |  Size: 113 KiB

0
_images/image12.jpg → _images/preinstall_d_logic_network.jpg
View File

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 87 KiB

After

Width:  |  Height:  |  Size: 87 KiB

0
_images/image04.jpg → _images/preinstall_d_switch_connect.jpg
View File

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 120 KiB

After

Width:  |  Height:  |  Size: 120 KiB

0
_images/image20.jpg → _images/preinstall_d_vlan.jpg
View File

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 96 KiB

After

Width:  |  Height:  |  Size: 96 KiB

0
_images/image16.png → _images/preinstall_d_vlan_3nics.png
View File

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 10 KiB

After

Width:  |  Height:  |  Size: 10 KiB

0
_images/image05.png → _images/preinstall_d_vlan_4nics.png
View File

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 12 KiB

After

Width:  |  Height:  |  Size: 12 KiB

0
_images/image15.jpg → _images/preinstall_d_vlan_segm.jpg
View File

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 101 KiB

After

Width:  |  Height:  |  Size: 101 KiB

3
conf.py
View File

@ -284,7 +284,8 @@ pdf_documents = [
('pdf_user', u'Fuel-for-OpenStack-3.2-UserGuide', u'User Guide',
u'2013, Mirantis Inc.'),
('pdf_install', u'Fuel-for-Openstack-3.2-InstallGuide', u'Installation Guide', u'2013, Mirantis Inc.'),
('pdf_reference', u'Fuel-for-OpenStack-3.2-ReferenceArchitecture', u'Reference Architecture', u'2013, Mirantis Inc.')
('pdf_reference', u'Fuel-for-OpenStack-3.2-ReferenceArchitecture', u'Reference Architecture', u'2013, Mirantis Inc.'),
('pdf_preinstall', u'Fuel-for-OpenStack-3.2-Pre-InstallationGuide', u'Pre-Installation Guide', u'2013, Mirantis Inc.')
# (master_doc, project, project, copyright),
]
pdf_stylesheets = ['letter', 'mirantis']

4
contents.rst
View File

@ -9,11 +9,11 @@ Documentation
.. toctree:: Documentation
:maxdepth: 2
pre-install-guide
install-guide
user-guide
reference-architecture
pre-install-guide
release-notes
frequently-asked-questions
eula

3
contents/contents-pre-install-guide.rst
View File

@ -3,7 +3,8 @@
.. toctree:: Table of Contents
:maxdepth: 2
.. include:: /pages/preface/preface.rst
.. include:: /pages/pre-install-guide/0010-intro.rst
.. include:: /pages/pre-install-guide/0020-system-requirements.rst
.. include:: /pages/pre-install-guide/0031-fuel-configuration.rst

2
pages/pre-install-guide/0030-pre-installation-checklist.rst
View File

@ -11,8 +11,6 @@ To help plan your OpenStack deployment, you can use the following
checklist to quickly identify and confirm the basic steps necessary for
a successful deployment.
.. table:: Pre-installation Checklist
+--------------------------------------------------------+--------------+
| Item to confirm | Status [tick |
| | if done] |

155
pages/pre-install-guide/0050-network-overview.rst
View File

@ -34,13 +34,12 @@ administrative purposes and network-based installation of Node servers.
OVS is an abbreviation for Open vSwitch, a production quality, multilayer
virtual switch licensed under the open source `Apache
2.0 <http://www.apache.org/licenses/LICENSE-2.0.html>`__  license.
2.0 <http://www.apache.org/licenses/LICENSE-2.0.html>`_  license.
For more information on each of these networks, check out the
`:ref:ReferenceArchitecture`_.
For more information about networks, see
:ref:`Reference Architecture<ref-arch>`.
Network deployment models
Network Deployment Models
=========================
This section describes the following network deployement models:
@ -53,28 +52,53 @@ This section describes the following network deployement models:
Nova-network
------------
Nova-network offers two variants for deploying the private network for tenants:
FlatDHCP Manager and VLAN Manager.
Nova-network offers two options for deploying private network for tenants:
FlatDHCP Manager
~~~~~~~~~~~~~~~~
* FlatDHCP Manager
* VLAN Manager
|image0|
FlatDHCP Manager Network Diagram
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
For an overview of FlatDHCP Manager, refer to the `ReferenceArchitecture_`.
The following diagram describes network configuration when you use
Nova-network with FlatDHCP Manager:
This guide illustrates the recommended way to connect the physical interfaces
of your servers to the OpenStack network.
.. image:: /_images/preinstall_d_flat_dhcp.jpg
:align: center
To associate each of the OpenStack networks to server NICs, this can be done
in Fuel UI.
* First, go to *Add Nodes*.
* Next, select the role for this host and *Apply Changes*
* Select the role you want to modify, and click *Configure Interfaces*.
* Drag and drop the appropriate networks onto the physical interfaces.  
For more information about FlatDHCP Manager, see :ref:`Reference Architecture<ref-arch>`.
Depending how many NICs you have in your node servers, you can use the
following examples to plan your NIC assignment.
VLAN Manager Network Diagram
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The following diagram describes network configuration when you use
Nova-network with VLAN Manager:
.. image:: /_images/preinstall_d_vlan.jpg
:align: center
Assigning OpenStack Networks to Network Interfaces
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
You must associate each OpenStack network with a server NIC.
To assigna OpenStack networks to server NICs, using Fuel UI:
1. Click **Add Nodes**.
2. Select the role for this host.
3. Click **Apply Changes**.
4. Select the role you want to modify, and click **Configure Interfaces**.
5. Drag and drop the appropriate networks onto the physical interfaces.
Network Planning Examples
~~~~~~~~~~~~~~~~~~~~~~~~~
FlatDHCP
^^^^^^^^
Depending on the number of NICs you have in your node servers, you can use the
following examples to plan your NIC assignment:
1 NIC deployment
@ -116,18 +140,10 @@ Routing recommendations
VLAN Manager
~~~~~~~~~~~~
^^^^^^^^^^^^
|image1|
This guide illustrates the recommended way to connect the physical interfaces
of your servers to the Openstack network.
To connect OpenStack networks to server Ethernet cards, in the Fuel UI
add a role to node, click on Configure Interfaces, and then drag and
drop the appropriate networks onto the physical interfaces.  Here are
the recommended network configurations depending on the number of NICs
you have in the node server:
Depending on the number of NICs you have in your node servers, you can use the
following examples to plan your NIC assignment:
1 NIC deployment
@ -175,22 +191,41 @@ Routing recommendations
Neutron
-------
VLAN segmentation
This section describes recommended parameters for network configuration
using the Neutron service.
VLAN Segmentation
~~~~~~~~~~~~~~~~~
The minimum number of NICs for this configuration is 3.
The following diagram shows the network isolation using Open vSwitches and
VLANs:
|image2|
.. image:: /_images/preinstall_d_vlan_segm.jpg
:align: center
.. note:: You must have at least three network interfaces for this
configuration
GRE Segmentation
~~~~~~~~~~~~~~~~
This guide illustrates the recommended way to connect the physical interfaces
of your servers to the Openstack network.
The following diagram shows the network segmentation using Open vSwitch
and GRE tunneling.
To connect OpenStack networks to server ethernet cards, in the Fuel UI
add a role to node, click on Configure Interfaces, and then drag and
drop the appropriate networks onto the physical interfaces.  Here are
the recommended network configurations depending on the number of NICs
you have in the node server:
.. image:: /_images/preinstall_d_gre_segm.jpg
:align: center
Open vSwitch (OVS) GRE tunnels are provided through Management Network.
.. note:: This setup does not include physical Private network.
Network Planing Examples
~~~~~~~~~~~~~~~~~~~~~~~~
VLAN Segmentation
^^^^^^^^^^^^^^^^^
Depending on the number of NICs you have in your node servers, you can use the
following examples to plan your NIC assignment:
3 NIC deployment
@ -200,7 +235,8 @@ you have in the node server:
- eth2 (br-eth2) - port for Private network (where the number of VLANs
depends on the number of tenant networks with a continuous range)
|image3|
.. image:: /_images/preinstall_d_vlan_3nics.png
:align: center
4 NIC deployment
@ -210,7 +246,8 @@ you have in the node server:
IDs
- eth3 (br-eth1) - port for Storage network
|image4|
.. image:: /_images/preinstall_d_vlan_4nics.png
:align: center
Routing recommendations
@ -222,23 +259,12 @@ Routing recommendations
- The Storage and Private network (VLANs) should be configured without
access to other networks (no L3 connectivity)
GRE Segmentation
~~~~~~~~~~~~~~~~
^^^^^^^^^^^^^^^^
|image5|
Open vSwitch (OVS) - GRE tunnels are provided via Management Network.
Please note that in this setup, there is no physical Private
network.
This guide illustrates the recommended way to connect the physical interfaces
of your servers to the Openstack network.
To connect OpenStack networks to server ethernet cards, in the Fuel UI
add a role to node, click on Configure Interfaces, and then drag and
drop the appropriate networks onto the physical interfaces.  Here are
the recommended network configurations depending on the number of NICs
you have in the node server:
Depending on the number of NICs you have in your node servers, you can use the
following examples to plan your NIC assignment:
2  NIC deployment 
@ -246,7 +272,8 @@ you have in the node server:
- eth1 (br-eth1) - port for networks: Public/Floating, Management,
Storage
|image6|
.. image:: /_images/preinstall_d_gre_2nics.png
:align: center
3  NIC deployment 
@ -254,7 +281,8 @@ you have in the node server:
- eth1 (br-eth1) - port for networks: Public/Floating, Management
- eth2 (br-eth2) - port for Storage network
|image7|
.. image:: /_images/preinstall_d_gre_3nics.png
:align: center
4  NIC deployment 
@ -263,7 +291,8 @@ you have in the node server:
- eth2 (br-eth2) - port for Public/Floating network
- eth3 (br-eth3) - port for Storage network
|image8|
.. image:: /_images/preinstall_d_gre_4nics.png
:align: center
Routing recommendations
@ -278,7 +307,7 @@ Routing recommendations
Routing recommendations
^^^^^^^^^^^^^^^^^^^^^^^
Consider the following routing recommendationswhen you configure your
Consider the following routing recommendations when you configure your
network:
- Use the default routing via a router in the Public network

11
pages/pre-install-guide/0060-quick-install-fuel.rst
View File

@ -30,8 +30,7 @@ To install Fuel using the ISO image:
8. In the Fuel UI, create a new OpenStack environment.
9. Configure the network settings using the address plan `that you prepared
earlier <#id.awjhoiu5x9zi>`__.
9. Configure the network settings using the address plan.
10. Verify the network configuration by clicking **Verify Networks**.
@ -43,16 +42,12 @@ To install Fuel using the ISO image:
* Scheduler driver
* Syslog
12. Assign roles for each node server that `you decided
earlier <#id.jjvc6acq4wu1>`__.
12. Assign a role for each node server.
13. Optionally, associate NICs with the OpenStack networks:
1. Select the nodes.
2. Click **Configure Interfaces**.
|image26|
3. Drag and drop the appropriate networks onto the physical interfaces.
4. Click **Apply**.
@ -61,7 +56,7 @@ To install Fuel using the ISO image:
some time.
After you deployed Mirantis OpenStack, verify the configuration by
running the tests from the **Health Check**  tab.
running the tests from the **Health Check** tab.
.. |image20| image:: /_images/image22.png
.. |image21| image:: /_images/image10.png

513
pages/pre-install-guide/0090-appendix.rst
View File

@ -3,9 +3,9 @@ Example 1: HA + Nova-network FlatDHCP manager
As a model example, the following configuration is used:
* Deployment mode: Multi-node HA
* **Deployment mode:** Multi-node HA
* Networking model: Nova-network FlatDHCP manager
* **Networking model:** Nova-network FlatDHCP manager
**Hardware and environment:**
@ -13,7 +13,7 @@ As a model example, the following configuration is used:
* 1 Cisco Catalyst 2960G switch
* Independent out of band management network for IPMI
* Connection to the Internet or/and DC network via a router called
*Gateway* and IP 172.16.1.1
**Gateway** and IP 172.16.1.1
**Node Server roles:**
@ -44,188 +44,63 @@ As a model example, the following configuration is used:
From the server node side, ports with the following VLAN IDs for
networks are used:
* eth0 - Management VLAN 101 (tagged), Storage VLAN 102(tagged) and
Administrative VLAN 104 (untagged)
* eth1 - Public/Floating VLAN 100 (tagged), Private VLAN 103 (tagged)
* eth0 - Management VLAN 101 (tagged), Storage VLAN 102(tagged) and
Administrative VLAN 104 (untagged)
* eth1 - Public/Floating VLAN 100 (tagged), Private VLAN 103 (tagged)
Detailed ports configuration
Detailed Port Configuration
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
::
Switch port
Server name
Server NIC
tagged/
untagged
VLAN IDs
G0/1
The following table describes the detailed port configuration and VLAN
assignment.
Fuel
+--------+-------------------+--------+-----------+-------------------------+
| Switch | Server name | Server | tagged / | VLAN ID |
| Port | | NIC | untagged | |
+========+===================+========+===========+=========================+
| G0/1 | Fuel | eth0 | untagged | 104 |
+--------+-------------------+--------+-----------+-------------------------+
| G0/2 | Fuel | eth1 | untagged | 100 |
+--------+-------------------+--------+-----------+-------------------------+
| G0/3 | Compute Node 1 | eth0 | tagged | 101, 102, 104 (untagged)|
+--------+-------------------+--------+-----------+-------------------------+
| G0/4 | Compute Node 1 | eth1 | tagged | 100, 103 |
+--------+-------------------+--------+-----------+-------------------------+
| G0/5 | Compute Node n | eth0 | tagged | 101, 102, 104 (untagged)|
+--------+-------------------+--------+-----------+-------------------------+
| G0/6 | Compute Node n | eth1 | tagged | 100, 103 |
+--------+-------------------+--------+-----------+-------------------------+
| G0/7 | Controller Node 1 | eth0 | tagged | 101, 102, 104(untagged) |
+--------+-------------------+--------+-----------+-------------------------+
| G0/8 | Controller Node 1 | eth1 | tagged | 100, 103 |
+--------+-------------------+--------+-----------+-------------------------+
| G0/9 | Controller Node 2 | eth0 | tagged | 101, 102, 104 (untagged)|
+--------+-------------------+--------+-----------+-------------------------+
| G0/10 | Controller Node 2 | eth1 | tagged | 100, 103 |
+--------+-------------------+--------+-----------+-------------------------+
| G0/11 | Controller Node 3 | eth0 | tagged | 101, 102, 104 (untagged)|
+--------+-------------------+--------+-----------+-------------------------+
| G0/12 | Controller Node 3 | eth1 | tagged | 100, 103 |
+--------+-------------------+--------+-----------+-------------------------+
| G0/13 | Cinder Node | eth0 | tagged | 101, 102, 104 (untagged)|
+--------+-------------------+--------+-----------+-------------------------+
| G0/14 | Cinder Node | eth1 | tagged | 100, 103 |
+--------+-------------------+--------+-----------+-------------------------+
| G0/24 | Router (default | - | untagged | 100 |
| | gateway) | | | |
+--------+-------------------+--------+-----------+-------------------------+
eth0
untagged
104
G0/2
Fuel
eth1
untagged
100
G0/3
Compute Node 1
eth0
tagged
101, 102, 104 (untagged)
G0/4
Compute Node 1
eth1
tagged
100, 103
G0/5
Compute Node n
eth0
tagged
101, 102, 104 (untagged)
G0/6
Compute Node n
eth1
tagged
100, 103
G0/7
Controller Node 1
eth0
tagged
101, 102, 104 (untagged)
G0/8
Controller Node 1
eth1
tagged
100, 103
G0/9
Controller Node 2
eth0
tagged
101, 102, 104 (untagged)
G0/10
Controller Node 2
eth1
tagged
100, 103
G0/11
Controller Node 3
eth0
tagged
101, 102, 104 (untagged)
G0/12
Controller Node 3
eth1
tagged
100, 103
G0/13
Cinder Node
eth0
tagged
101, 102, 104 (untagged)
G0/14
Cinder Node
eth1
tagged
100, 103
G0/24
Router (default gateway)
-
untagged
100
--------------|image9|
Connect the cable servers to the switch as in the diagram below:
|image9|
.. image:: /_images/preinstall_d_switch_connect.jpg
:align: center
The following diagram describes the network for this environment.
The following diagram describes network for this environment.
|image10|
.. image:: /_images/preinstall_d_logic_network.jpg
:align: center
To deploy Mirantis OpenStack, use the following switch
configuration.
@ -654,236 +529,103 @@ Switch configuration (Juniper EX4200)
Example 2: HA + Neutron with GRE
--------------------------------
As a model example, the following configuration is used:
* **Deploying mode:** Multi-node HA
**Deploying mode:** Multi-node HA
* **Networking model:** Neutron with GRE
**Networking model:** Neutron with GRE
**Hardware and environment:**
Hardware and environment:
* 7 servers with two 1Gb/s ethernet NIC and IPMI
* 1 Cisco Catalyst 3750 switch
* Independent out of band management network for IPMI
* Connection to the Internet or/and DC network via a router called
**Gateway** and IP 172.16.1.1
- 7 servers with two 1Gb/s ethernet NIC and IPMI
- 1 Cisco Catalyst 3750 switch
- Independent out of band management network for IPMI
- Connection to the Internet or/and DC network via a router called
“Gateway” and IP 172.16.1.1
**Node servers roles:**
` <#>`__
* 1 server as Fuel Node
* 3 servers as Controller Node
* 1 server as Cinder Node
* 2 servers as Compute Node
Node servers roles:
**Network Configuration Plan:**
- 1 server as Fuel Node
- 3 servers as Controller Node
- 1 server as Cinder Node
- 2 servers as Compute Node
* Floating/Public network 172.16.0.0/24 in VLAN 100 (unttaged on
servers)
* Floating IP range 172.16.0.130 - 254
* Internal network (private) 192.168.111.0/24
* Gateway 192.168.111.1
* DNS 8.8.4.4, 8.8.8.8
* Tunnel ID range 2 - 65535
* Management network 192.168.0.0/24 in VLAN 101
* Storage network 192.168.1.0/24 in VLAN 102
* Administrative network (for Fuel) 10.20.0.0/24 in VLAN 103
` <#>`__
**Network Parameters**
Plan of network configuration:
* Fuel server: IP 10.20.0.2/24
* Default gateway: 10.20.0.1
* DNS: 10.20.0.1
- Floating/Public network 172.16.0.0/24 in VLAN 100 (unttaged on
servers)
.. note:: The Internet and rest of DC access via Public network (for Openstack
Nodes) and Administrative network (Fuel server).
- floating IP range 172.16.0.130 - 254
From server side, ports with following VLAN IDs are used:
- Internal network (private) 192.168.111.0/24
- gateway 192.168.111.1
- DNS 8.8.4.4, 8.8.8.8
- tunnel ID range 2 - 65535
- Management network 192.168.0.0/24 in VLAN 101
- Storage network 192.168.1.0/24 in VLAN 102
- Administrative network (for Fuel) 10.20.0.0/24 in VLAN 103
Fuel server IP 10.20.0.2/24, default gateway 10.20.0.1, DNS 10.20.0.1
The Internet and rest of DC access via Public network (for Openstack
Nodes) and Administrative network (Fuel server).
From server side we will use ports with following VLAN IDs for networks:
- eth0 - Administrative VLAN 103 (untagged)
- eth1 - Public/Floating VLAN 100 (untagged), Management VLAN 101
* eth0 - Administrative VLAN 103 (untagged)
* eth1 - Public/Floating VLAN 100 (untagged), Management VLAN 101
(tagged), Storage VLAN 102 (tagged)
Detailed ports configuration:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Detailed port configuration
~~~~~~~~~~~~~~~~~~~~~~~~~~~
The following table describes port configuration for this deployment.
+--------+-------------------+--------+-----------+-------------------------+
| Switch | Server name | Server | tagged / | VLAN ID |
| Port | | NIC | untagged | |
+========+===================+========+===========+=========================+
| G0/1 | Fuel | eth0 | untagged | 103 |
+--------+-------------------+--------+-----------+-------------------------+
| G0/2 | Fuel | eth1 | untagged | 100 |
+--------+-------------------+--------+-----------+-------------------------+
| G0/3 | Compute Node 1 | eth0 | untagged | 103 |
+--------+-------------------+--------+-----------+-------------------------+
| G0/4 | Compute Node 1 | eth1 | tagged | 100(untagged), 101, 102 |
+--------+-------------------+--------+-----------+-------------------------+
| G0/5 | Compute Node n | eth0 | tagged | 103 |
+--------+-------------------+--------+-----------+-------------------------+
| G0/6 | Compute Node n | eth1 | tagged | 100(untagged), 101, 102 |
+--------+-------------------+--------+-----------+-------------------------+
| G0/7 | Controller Node 1 | eth0 | tagged | 103 |
+--------+-------------------+--------+-----------+-------------------------+
| G0/8 | Controller Node 1 | eth1 | tagged | 100(untagged), 101, 102 |
+--------+-------------------+--------+-----------+-------------------------+
| G0/9 | Controller Node 2 | eth0 | tagged | 103 |
+--------+-------------------+--------+-----------+-------------------------+
| G0/10 | Controller Node 2 | eth1 | tagged | 100(untagged), 101, 102 |
+--------+-------------------+--------+-----------+-------------------------+
| G0/11 | Controller Node 3 | eth0 | tagged | 103 |
+--------+-------------------+--------+-----------+-------------------------+
| G0/12 | Controller Node 3 | eth1 | tagged | 100(untagged), 101, 102 |
+--------+-------------------+--------+-----------+-------------------------+
| G0/13 | Cinder Node | eth0 | tagged | 103 |
+--------+-------------------+--------+-----------+-------------------------+
| G0/14 | Cinder Node | eth1 | tagged | 100(untagged), 101, 102 |
+--------+-------------------+--------+-----------+-------------------------+
| G0/24 | Router (default | - | untagged | 100 |
| | gateway) | | | |
+--------+-------------------+--------+-----------+-------------------------+
Switch port
Server name
Server NIC
tagged/
untagged
VLAN IDs
G0/1
Fuel
eth0
untagged
103
G0/2
Fuel
eth1
untagged
100
G0/3
Compute Node 1
eth0
untagged
103
G0/4
Compute Node 1
eth1
tagged
100(untagged), 101, 102
G0/5
Compute Node n
eth0
tagged
103
G0/6
Compute Node n
eth1
tagged
100(untagged), 101, 102
G0/7
Controller Node 1
eth0
tagged
103
G0/8
Controller Node 1
eth1
tagged
100(untagged), 101, 102
G0/9
Controller Node 2
eth0
tagged
103
G0/10
Controller Node 2
eth1
tagged
100(untagged), 101, 102
G0/11
Controller Node 3
eth0
tagged
103
G0/12
Controller Node 3
eth1
tagged
100(untagged), 101, 102
G0/13
Cinder Node
eth0
tagged
103
G0/14
Cinder Node
eth1
tagged
100(untagged), 101, 102
G0/24
Router (default gateway)
-
untagged
100
Cable servers to the switch as in the diagram below.\ |image18|
Here is the logical network diagram for this environment.
|image19|
To deploy Mirantis OpenStack you should use the following the switch
configuration:
Switch configuration (Cisco Catalyst 2960G)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Use the following configuration to deploy Mirantis OpenStack using Cisco
Catalyst 2960G network switch.
::
service timestamps debug datetime msec localtime show-timezone
@ -1054,6 +796,9 @@ Switch configuration (Cisco Catalyst 2960G)
Switch configuration (Juniper EX4200)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Use the following configuration to deploy Mirantis OpenStack using
Juniper EX4200 network switch.
::
system {