Merge "Documentation chagnes for Fuel 9.0/9.1 release"
16
README.rst
@ -3,7 +3,7 @@ Mirantis Fuel MidoNet plugin
|
|||||||
|
|
||||||
Compatible versions:
|
Compatible versions:
|
||||||
|
|
||||||
- Mirantis Fuel 9.0
|
- Mirantis Fuel 9.0 and Fuel 9.1
|
||||||
- MidoNet v5.2
|
- MidoNet v5.2
|
||||||
- Midokura Enterprise MidoNet 5.2
|
- Midokura Enterprise MidoNet 5.2
|
||||||
|
|
||||||
@ -24,7 +24,7 @@ How to build the plugin
|
|||||||
$ cd fuel-plugin-midonet
|
$ cd fuel-plugin-midonet
|
||||||
$ fpb --build .
|
$ fpb --build .
|
||||||
|
|
||||||
A *rpm* called `midonet-4.1-4.0.0-1.noarch.rpm` should be created in
|
A *rpm* called `midonet-4.1-4.1.0-1.noarch.rpm` should be created in
|
||||||
the same directory.
|
the same directory.
|
||||||
|
|
||||||
Follow the documentation to install and configure the plugin. You can read the
|
Follow the documentation to install and configure the plugin. You can read the
|
||||||
@ -33,8 +33,14 @@ Follow the documentation to install and configure the plugin. You can read the
|
|||||||
How to build the documentation
|
How to build the documentation
|
||||||
------------------------------
|
------------------------------
|
||||||
|
|
||||||
You need to have **Sphinx** installed in your computer. The Makefile provides
|
You need to have **Sphinx** installed in your computer. Hint; for full Latex
|
||||||
several target formats to do so. Go to the `doc` directory and run:
|
Sphinx support on Ubuntu one needs **python-sphinx**, **rst2pdf**, **texlive**
|
||||||
|
and **texlive-latex-extra** packages. The Makefile provides several target
|
||||||
|
formats to do so. Go to the `doc` directory and run:
|
||||||
|
|
||||||
|
make latexpdf
|
||||||
|
|
||||||
|
or:
|
||||||
|
|
||||||
make html
|
make html
|
||||||
|
|
||||||
@ -42,4 +48,4 @@ or:
|
|||||||
|
|
||||||
make pdf
|
make pdf
|
||||||
|
|
||||||
You will need `rst2pdf` to run the latter.
|
You will need `rst2pdf` to run the last one.
|
||||||
|
BIN
doc/TestPlanforMidoNetFuelPlugin4.1.0.pdf
Normal file
Before Width: | Height: | Size: 35 KiB After Width: | Height: | Size: 17 KiB |
Before Width: | Height: | Size: 29 KiB After Width: | Height: | Size: 34 KiB |
Before Width: | Height: | Size: 6.8 KiB After Width: | Height: | Size: 24 KiB |
Before Width: | Height: | Size: 20 KiB After Width: | Height: | Size: 16 KiB |
Before Width: | Height: | Size: 74 KiB After Width: | Height: | Size: 97 KiB |
Before Width: | Height: | Size: 63 KiB After Width: | Height: | Size: 92 KiB |
Before Width: | Height: | Size: 45 KiB |
Before Width: | Height: | Size: 60 KiB |
BIN
doc/images/static_gw_params.png
Normal file
After Width: | Height: | Size: 34 KiB |
Before Width: | Height: | Size: 6.6 KiB After Width: | Height: | Size: 7.9 KiB |
Before Width: | Height: | Size: 50 KiB After Width: | Height: | Size: 61 KiB |
@ -8,8 +8,9 @@ Appendix B - references
|
|||||||
=======================
|
=======================
|
||||||
|
|
||||||
- `MidoNet Web Site <http://midonet.org/>`_
|
- `MidoNet Web Site <http://midonet.org/>`_
|
||||||
- `MidoNet v2015.06 Documentation <http://docs.midonet.org/>`_
|
- `MidoNet v5.2 Documentation <http://docs.midonet.org/>`_
|
||||||
- `MidoNet v2015.06 Code <https://github.com/midonet/midonet/tree/stable/v2015.06.3>`_
|
- `MidoNet v5.2 Code <https://github.com/midonet/midonet/tree/stable/v5.2.1>`_
|
||||||
- `Midokura Enterprise MidoNet (MEM) v1.9 Documentation <http://docs.midokura.com/docs/latest/manager-guide/content/index.html>`_
|
- `Midokura Enterprise MidoNet (MEM) v5.2 Documentation <http://docs.midokura.com/docs/latest/manager-guide/content/index.html>`_
|
||||||
- `Midokura Enterprise MidoNet (MEM) 30 Day Trial <http://www.midokura.com/mem-eval/>`_
|
- `Midokura Enterprise MidoNet (MEM) 30 Day Trial <http://www.midokura.com/mem-eval/>`_
|
||||||
- `Fuel Plugins Catalog <https://www.mirantis.com/products/openstack-drivers-and-plugins/fuel-plugins/>`_
|
- `Partner Community Catalog, Midokura <https://www.mirantis.com/partners/midokura/>`_
|
||||||
|
|
||||||
|
@ -2,6 +2,8 @@
|
|||||||
|
|
||||||
PageBreak oneColumn
|
PageBreak oneColumn
|
||||||
|
|
||||||
|
.. _bgp_peer:
|
||||||
|
|
||||||
Appendix C - Setting up test BGP peer
|
Appendix C - Setting up test BGP peer
|
||||||
=====================================
|
=====================================
|
||||||
|
|
||||||
|
@ -39,7 +39,7 @@ master_doc = 'index'
|
|||||||
# General information about the project.
|
# General information about the project.
|
||||||
project = u'fuel-midonet-plugin'
|
project = u'fuel-midonet-plugin'
|
||||||
copyright = u'2016, Midokura SARL'
|
copyright = u'2016, Midokura SARL'
|
||||||
version = '4.0.0'
|
version = '4.1.0'
|
||||||
release = version[:3] + '-' + version + '-1'
|
release = version[:3] + '-' + version + '-1'
|
||||||
|
|
||||||
# If true, '()' will be appended to :func: etc. cross-reference text.
|
# If true, '()' will be appended to :func: etc. cross-reference text.
|
||||||
@ -75,7 +75,7 @@ latex_documents = [
|
|||||||
|
|
||||||
latex_elements = { 'classoptions': ',openany,oneside', 'babel' : '\\usepackage[english]{babel}' }
|
latex_elements = { 'classoptions': ',openany,oneside', 'babel' : '\\usepackage[english]{babel}' }
|
||||||
|
|
||||||
pdf_documents = [(master_doc, project, u'MidoNet plugin for Fuel 8', copyright),]
|
pdf_documents = [(master_doc, project, u'MidoNet plugin for Fuel 9', copyright),]
|
||||||
pdf_inline_footnotes = True
|
pdf_inline_footnotes = True
|
||||||
|
|
||||||
# Example configuration for intersphinx: refer to the Python standard library.
|
# Example configuration for intersphinx: refer to the Python standard library.
|
||||||
|
@ -1,6 +1,6 @@
|
|||||||
.. |FuelVer| replace:: 8.0
|
.. |FuelVer| replace:: 9.0/9.1
|
||||||
.. |PrevPluginVer| replace:: 3.0.1
|
.. |PrevPluginVer| replace:: 4.0.0
|
||||||
.. |PluginVer| replace:: 4.0.0
|
.. |PluginVer| replace:: 4.1.0
|
||||||
|
|
||||||
.. raw:: pdf
|
.. raw:: pdf
|
||||||
|
|
||||||
@ -15,13 +15,13 @@ for Infrastructure-as-a-Service (IaaS) clouds. Plugin for Fuel |FuelVer| provide
|
|||||||
puppet manifests to install all the components to deploy easily MidoNet with
|
puppet manifests to install all the components to deploy easily MidoNet with
|
||||||
Fuel in both lab or production environments.
|
Fuel in both lab or production environments.
|
||||||
|
|
||||||
Fuel MidoNet plugin is capable of deploying MidoNet v2015.06_ on top of Mirantis
|
Fuel MidoNet plugin is capable of deploying MidoNet v5.2_ on top of Mirantis
|
||||||
OpenStack Fuel version |FuelVer|. There are no prerequisites to use the MidoNet
|
OpenStack Fuel version |FuelVer|. There are no prerequisites to use the MidoNet
|
||||||
plugin: MidoNet is Open Source, and the plugin sets the repositories from where
|
plugin: MidoNet is Open Source, and the plugin sets the repositories from where
|
||||||
download and install MidoNet packages.
|
download and install MidoNet packages.
|
||||||
|
|
||||||
This plugin also supports Midokura Enterprise MidoNet (MEM_) installation by
|
This plugin also supports installation of same version of Midokura Enterprise
|
||||||
allowing the user to choose the option from the Fuel Web UI.
|
MidoNet (MEM_) by allowing the user to choose the option from the Fuel Web UI.
|
||||||
The packages are available to download from a password protected-repository.
|
The packages are available to download from a password protected-repository.
|
||||||
The needed credentials will be provided_ by Midokura.
|
The needed credentials will be provided_ by Midokura.
|
||||||
|
|
||||||
@ -40,17 +40,11 @@ MidoNet plugin for Fuel |PluginVer|
|
|||||||
Known Limitations
|
Known Limitations
|
||||||
-----------------
|
-----------------
|
||||||
|
|
||||||
* The plugin has some limitations regarding node count scalability for NSDB
|
* The plugin has some limitations regarding node count regarding
|
||||||
(Network State Database) nodes. Once number of nodes with such role have been
|
Analytics/Insight MEM-only feature. Currently, only one such node can be
|
||||||
determined on initial deployment, it can not be changed. Controller and
|
deployed.
|
||||||
Compute role nodes are not affected by this limitation, current plugin
|
|
||||||
version supports Controller and Compute scalability.
|
|
||||||
|
|
||||||
* Current version of plugin can only deploy single MidoNet Gareway role node.
|
.. _v5.2: https://github.com/midonet/midonet/tree/v5.2.1
|
||||||
MidoNet itself supports any number of gateway nodes, it is only a plugin
|
|
||||||
limitation, additional gateways needs to be set up manually.
|
|
||||||
|
|
||||||
.. _v2015.06: https://github.com/midonet/midonet/releases/tag/v2015.06.3
|
|
||||||
.. _MEM: http://docs.midokura.com/docs/latest/manager-guide/content/index.html
|
.. _MEM: http://docs.midokura.com/docs/latest/manager-guide/content/index.html
|
||||||
.. _provided: http://www.midokura.com/mem-eval
|
.. _provided: http://www.midokura.com/mem-eval
|
||||||
|
|
||||||
@ -58,12 +52,17 @@ Known Limitations
|
|||||||
Changes in MidoNet plugin |PluginVer|
|
Changes in MidoNet plugin |PluginVer|
|
||||||
-------------------------------------
|
-------------------------------------
|
||||||
|
|
||||||
* New features:
|
New features:
|
||||||
|
|
||||||
|
* Support for MidoNet 5.2 including all MEM features
|
||||||
* Support for Fuel |FuelVer|
|
* Support for Fuel |FuelVer|
|
||||||
* Tasks are included in the ``deployment`` stage of Fuel instead of in the
|
* support for deploying MidoNet manager web-app on controller nodes
|
||||||
``post_deployment``, so the time of deployment has decreased around 20-30
|
* Support for arbitrary number of BGP gateway nodes
|
||||||
minutes, as well as it makes the deployment more reliable.
|
* Support for static, non-BGP gateway
|
||||||
* **MidoNet** option available in the *Networking Setup* during the environment
|
|
||||||
creation, making the configuration of an environment with MidoNet much
|
|
||||||
easier.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
@ -1,26 +1,17 @@
|
|||||||
|
|
||||||
.. raw:: pdf
|
.. raw:: pdf
|
||||||
|
|
||||||
PageBreak oneColumn
|
|
||||||
|
|
||||||
|
|
||||||
MidoNet Fuel Plugin User Guide
|
MidoNet Fuel Plugin User Guide
|
||||||
==============================
|
==============================
|
||||||
|
|
||||||
Once the Fuel MidoNet plugin has been installed (following
|
Short Introduction to MidoNet
|
||||||
:ref:`Installation Guide <installation_guide>`), you can create *OpenStack* environments that use
|
-----------------------------
|
||||||
MidoNet SDN controller as a Neutron back-end.
|
|
||||||
|
|
||||||
MidoNet Networks
|
|
||||||
----------------
|
|
||||||
|
|
||||||
MidoNet changes the behaviour of default Neutron deployments, understanding
|
MidoNet changes the behaviour of default Neutron deployments, understanding
|
||||||
what MidoNet plugin does, especially in regard to external networks, is
|
what MidoNet plugin does, especially in regard to external networks, is
|
||||||
essential to configure and use MidoNet Fuel plugin properly.
|
essential to configure and use MidoNet Fuel plugin properly. MidoNet plugin is
|
||||||
|
compatible with both **Neutron + GRE** and **Neutron + VxLAN** network
|
||||||
MidoNet plugin is compatible with both **Neutron + GRE** and
|
tunnelling overlays, so let's focus on showing the differences between the
|
||||||
**Neutron + VxLAN** network tunnelling overlays, so let's focus on showing
|
Neutron default ML2 deployments first.
|
||||||
the differences between the Neutron default ML2 deployments first.
|
|
||||||
|
|
||||||
Neutron without MidoNet plugin
|
Neutron without MidoNet plugin
|
||||||
``````````````````````````````
|
``````````````````````````````
|
||||||
@ -30,7 +21,8 @@ Fuel 7.0 reference architecture contains some useful information in
|
|||||||
Neutron-default ML2 topolgy:
|
Neutron-default ML2 topolgy:
|
||||||
|
|
||||||
.. image:: ../images/fuelml2gre.png
|
.. image:: ../images/fuelml2gre.png
|
||||||
:width: 100%
|
:width: 70%
|
||||||
|
:align: center
|
||||||
|
|
||||||
In this topology, red, or "North" network represents the Public Internet,
|
In this topology, red, or "North" network represents the Public Internet,
|
||||||
including Floating IP subnet assigned to OpenStack cloud. That means API access
|
including Floating IP subnet assigned to OpenStack cloud. That means API access
|
||||||
@ -57,13 +49,14 @@ Even the Floating IPs live in the network overlay. Floating IP subnet is
|
|||||||
separated from the services API network range (called Public Network on Fuel
|
separated from the services API network range (called Public Network on Fuel
|
||||||
and represented by the red network below) and MidoNet gateway advertises the
|
and represented by the red network below) and MidoNet gateway advertises the
|
||||||
routes that belong to Floating Ranges to BGP peers. So MidoNet plugin forces
|
routes that belong to Floating Ranges to BGP peers. So MidoNet plugin forces
|
||||||
you to define a new Network on its settings, and allocation-range from
|
user to define a new Network on its settings, and allocation-range from
|
||||||
environment settings get overridden.
|
environment settings get overridden.
|
||||||
|
|
||||||
MidoNet deployment topology:
|
MidoNet deployment topology:
|
||||||
|
|
||||||
.. image:: ../images/midonet_fuel.png
|
.. image:: ../images/midonet_fuel.png
|
||||||
:width: 100%
|
:width: 75%
|
||||||
|
:align: center
|
||||||
|
|
||||||
On this topology diagram:
|
On this topology diagram:
|
||||||
|
|
||||||
@ -88,24 +81,46 @@ On this topology diagram:
|
|||||||
this guide (and Neutron & MidoNet itself).
|
this guide (and Neutron & MidoNet itself).
|
||||||
|
|
||||||
|
|
||||||
MidoNet gateway is native distributed system, one can place as many gateways
|
MidoNet gateway in its BGP mode of operation is a native distributed system,
|
||||||
necessary, so North-South traffic can be distributed and balanced (Although due
|
one can place as many BGP gateways as necessary, so North-South traffic can be
|
||||||
plugin limitation you can only deploy one). Once BGP sessions are established
|
distributed and balanced. Once BGP sessions are established and routes are
|
||||||
and routes are exchanged between BGP "peers", each North-to-South network packet
|
exchanged between BGP peers, each North-to-South network packet gets routed
|
||||||
gets routed from the External Public API network to one of the MidoNet gateways.
|
from the External Public API network to one of the MidoNet gateways.
|
||||||
It does not matter which of them gets the packet, they work as if they are a
|
It does not matter which of them gets the packet, they work as if they are a
|
||||||
single entity. MidoNet gateway sends the inbound packet directly to the Compute
|
single entity. MidoNet gateway sends the inbound packet directly to the Compute
|
||||||
that hosts the target virtual machine.
|
that hosts the target virtual machine.
|
||||||
|
|
||||||
In this way controller nodes gets significantly less overloaded, since they
|
In this way controller nodes gets significantly less overloaded, since they
|
||||||
only need to answer user requests and they don't handle VM traffic at all
|
only need to answer user requests and they don't handle VM traffic at all.
|
||||||
(the only exception is the metadata traffic at VM provisioning time).
|
|
||||||
|
Another MidoNet gateway mode of operation is to set up a single static routing
|
||||||
|
gateway, conceptually similar to the simple hardware gareway routers. Although
|
||||||
|
the plugin supports such setup, it would only establish one such gateway,
|
||||||
|
and consequently no redundancy or traffic balancing will be supported. This
|
||||||
|
kind of gateway setup is not recommanded in production and mission-critical
|
||||||
|
deployments, but may be suitable for lab or proof-of-concept deployments.
|
||||||
|
|
||||||
Following the learned concepts, we are ready to create a Fuel environment
|
Following the learned concepts, we are ready to create a Fuel environment
|
||||||
that uses MidoNet.
|
that uses MidoNet.
|
||||||
|
|
||||||
|
|
||||||
Select Environment
|
MidoNet MEM Insights
|
||||||
|
````````````````````
|
||||||
|
The Midokura Enterprise MidoNet (MEM) add-ons offer additional functionalities
|
||||||
|
on top of the core MidoNet features, including Flow Tracing and Big Data
|
||||||
|
Analytics support. These tools provide means to collect system information that
|
||||||
|
can be used by the operator to visualize the network behavior.
|
||||||
|
|
||||||
|
These, as well as many other features are accessible via MidoNet manager,
|
||||||
|
a WEB front-end application that can manage many aspects of MidoNet network
|
||||||
|
topology that are usually not available in OpenStack or Neutron, provide
|
||||||
|
detailed visualization of network usage as well as provide important
|
||||||
|
troubleshooting tool. For more details see
|
||||||
|
`Midokura Enterprise MidoNet (MEM) MidoNet Manager Guide`_ and
|
||||||
|
`Midokura Enterprise MidoNet (MEM) Insights Guide`_
|
||||||
|
|
||||||
|
|
||||||
|
Create Environment
|
||||||
------------------
|
------------------
|
||||||
|
|
||||||
#. When creating the environment in the Fuel UI wizard, choose **Neutron with
|
#. When creating the environment in the Fuel UI wizard, choose **Neutron with
|
||||||
@ -113,15 +128,16 @@ Select Environment
|
|||||||
|
|
||||||
.. image:: ../images/tunneling.png
|
.. image:: ../images/tunneling.png
|
||||||
:width: 75%
|
:width: 75%
|
||||||
|
:align: center
|
||||||
|
|
||||||
After that, one will be able to choose between *GRE* or *VXLAN* encapsulation
|
After that, one will be able to choose between *GRE* or *VXLAN* encapsulation
|
||||||
(WEB interface; Settings, Other section). MidoNet works with both of the
|
(Fuel WEB interface; Settings, Other section). MidoNet works with both of the
|
||||||
encapsulation technologies, but VXLAN may offer better performance,
|
encapsulation technologies, but VXLAN may offer better performance,
|
||||||
especially for the deployments of a larger scale.
|
especially for the deployments of a larger scale.
|
||||||
|
|
||||||
#. MidoNet plugin does not interact with the rest of the options, so choose
|
#. MidoNet plugin does not interact with the rest of the options, so choose
|
||||||
whatever your deployment demands on them. Follow instructions from the
|
whatever your deployment demands on them. Follow instructions from the
|
||||||
`official Mirantis OpenStack documentation`_ to finish the configuration.
|
`official OpenStack Fuel documentation`_ to finish the configuration.
|
||||||
|
|
||||||
|
|
||||||
Configure MidoNet Plugin
|
Configure MidoNet Plugin
|
||||||
@ -132,6 +148,7 @@ go to the *Other* section:
|
|||||||
|
|
||||||
.. image:: ../images/other.png
|
.. image:: ../images/other.png
|
||||||
:width: 75%
|
:width: 75%
|
||||||
|
:align: center
|
||||||
|
|
||||||
Install Midokura Enterprise MidoNet (Optional)
|
Install Midokura Enterprise MidoNet (Optional)
|
||||||
``````````````````````````````````````````````
|
``````````````````````````````````````````````
|
||||||
@ -139,14 +156,15 @@ Install Midokura Enterprise MidoNet (Optional)
|
|||||||
#. Installing Midokura Enterprise MidoNet, you will be able to use some specific
|
#. Installing Midokura Enterprise MidoNet, you will be able to use some specific
|
||||||
features from MidoNet only available on the Enterprise version.
|
features from MidoNet only available on the Enterprise version.
|
||||||
|
|
||||||
#. Activate the option **Install Midokura Enterprise MidoNet**.
|
#. Activate the option **Install Midokura Enterprise MidoNet**. Optionally,
|
||||||
|
activate Insights features if desired. Select the Midokura Enterprise
|
||||||
|
MidoNet (MEM) version (currently this plugin supports only MEM 5.2).
|
||||||
|
|
||||||
.. image:: ../images/mem.png
|
.. image:: ../images/mem.png
|
||||||
:width: 75%
|
:width: 75%
|
||||||
|
|
||||||
#. Select the Midokura Enterprise MidoNet (MEM) version (only 1.9 available now)
|
#. Fill the MEM repository **Username** and **Password** fields required for
|
||||||
and fill the **Username** and **Password** fields for downloading the
|
downloading the MEM packages from the repository.
|
||||||
packages from the repository.
|
|
||||||
|
|
||||||
.. image:: ../images/mem_credentials.png
|
.. image:: ../images/mem_credentials.png
|
||||||
:width: 75%
|
:width: 75%
|
||||||
@ -174,44 +192,62 @@ filled by default, but you will need to change them for sure):
|
|||||||
:width: 75%
|
:width: 75%
|
||||||
|
|
||||||
|
|
||||||
Configuring the floating fields in *MidoNet plugin*, you will override most of the
|
Configuring the floating fields in *MidoNet plugin*, you will override most of
|
||||||
options of the *Neutron L3/Floating Network Parameters* section of the
|
the options of the *Neutron L3/Floating Network Parameters* section of the
|
||||||
*Networks* tab of the environment:
|
*Networks* tab of the environment.
|
||||||
|
|
||||||
.. image:: ../images/overridden_options.png
|
|
||||||
:width: 75%
|
|
||||||
|
|
||||||
So this *Floating IP range* (first row) will be completely ignored. This
|
So this *Floating IP range* (first row) will be completely ignored. This
|
||||||
range has to match with the *CIDR* of the *Public Network*:
|
range has to match with the *CIDR* of the *Public Network*, Which only will be
|
||||||
|
used for API-accessible IPs to the OpenStack services but not for Virtual
|
||||||
.. image:: ../images/public_network.png
|
Machine's floating IPs. Please refer to `Neutron with Midonet
|
||||||
:width: 75%
|
|
||||||
|
|
||||||
Which only will be used for API-accessible IPs to the OpenStack services but not
|
|
||||||
for Virtual Machine's floating IPs. Please refer to `Neutron with Midonet
|
|
||||||
plugin`_ section of this document if it is not clear enough to you.
|
plugin`_ section of this document if it is not clear enough to you.
|
||||||
|
|
||||||
Configure BGP
|
Configure the Gateway
|
||||||
`````````````
|
`````````````````````
|
||||||
|
|
||||||
Fill the BGP attributes:
|
|
||||||
|
|
||||||
|
#. Here we have three options, first of which is to configure the arbitrary number
|
||||||
|
of BGP gateways. For this one needs to fill the BGP attributes properly:
|
||||||
|
|
||||||
.. image:: ../images/bgp_params.png
|
.. image:: ../images/bgp_params.png
|
||||||
:width: 75%
|
:width: 75%
|
||||||
|
|
||||||
There is a nice tutorial in this document: **Setting up test BGP peer** to run a
|
Special attention needs to be given to a formatting of a **BGP Peers** field.
|
||||||
BGP peer for testing environments.
|
This field can supply a comma-separated list of a BGP pairs, where each pair
|
||||||
|
is defined as:
|
||||||
|
|
||||||
|
::
|
||||||
|
|
||||||
|
<local-peer-IP>/<bit-length-of-the-net-prefix>-<external-peer-IP>-<remote-AS>
|
||||||
|
|
||||||
|
Note that under normal conditions, local BGP peer means "local to MidoNet
|
||||||
|
deployment" and remote BGP peer means external, BGP router peer located at
|
||||||
|
the physical network underlay. In case one needs to set up external BGP peer
|
||||||
|
to test the MidoNet BGP gateway functionality, we provide the simple tutorial
|
||||||
|
at :ref:`Appendix C - Setting up test BGP peer <bgp_peer>`.
|
||||||
|
|
||||||
|
#. Second option is to tell MidoNet Fuel plugin to setup a single static routing
|
||||||
|
gateway, conceptually similar to the simple hardware gareway routers. For this
|
||||||
|
to work one needs to supply routing IP addresses, one for a routing interface
|
||||||
|
on an "external" side (LinuxBridge address on a server that is running MidoNet
|
||||||
|
gateway agent software) and one at "internal" virtual Edge Router. For example:
|
||||||
|
|
||||||
|
.. image:: ../images/static_gw_params.png
|
||||||
|
:width: 85%
|
||||||
|
|
||||||
|
#. Finnaly, last option is to leave gateway configurationto be done completely
|
||||||
|
manually. Such use case may be neccessary for complex deployments with
|
||||||
|
multiple gateways of various types.
|
||||||
|
|
||||||
|
|
||||||
Assign Roles to Nodes
|
Assign Roles to Nodes
|
||||||
---------------------
|
---------------------
|
||||||
|
|
||||||
#. Go to the *Nodes* tab and you will see the **Network State DataBase** and
|
#. Go to the *Nodes* tab and you will see the **Network State Database** and
|
||||||
**MidoNet HA Gateway** roles available to be assigned to roles.
|
**MidoNet HA Gateway** roles available to be assigned to roles. Optionally,
|
||||||
|
**MidoNet Analytics Node** as well.
|
||||||
|
|
||||||
.. image:: ../images/nodes_to_roles.png
|
.. image:: ../images/nodes_to_roles.png
|
||||||
:width: 75%
|
:width: 85%
|
||||||
|
|
||||||
#. Some general advice to be followed:
|
#. Some general advice to be followed:
|
||||||
|
|
||||||
@ -245,9 +281,9 @@ For advanced networking features supported by MidoNet please
|
|||||||
see `MidoNet Operations Guide`_. For general MidoNet troubleshooting, assuming
|
see `MidoNet Operations Guide`_. For general MidoNet troubleshooting, assuming
|
||||||
the deployment went fine, please see `MidoNet Troubleshooting Guide`_.
|
the deployment went fine, please see `MidoNet Troubleshooting Guide`_.
|
||||||
|
|
||||||
.. _MidoNet Operations Guide: https://docs.midonet.org/docs/v2015.06/en/operations-guide/content/index.html
|
.. _MidoNet Operations Guide: https://docs.midonet.org/docs/v5.2/en/operations-guide/content/index.html
|
||||||
.. _MidoNet Troubleshooting Guide: https://docs.midonet.org/docs/v2015.06/en/troubleshooting-guide/content/index.html
|
.. _MidoNet Troubleshooting Guide: https://docs.midonet.org/docs/v5.2/en/troubleshooting-guide/content/index.html
|
||||||
.. _`Connectivity Check`: https://docs.mirantis.com/openstack/fuel/fuel-8.0/operations.html#network-issues
|
.. _`Connectivity Check`: http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-user-guide/configure-environment/verify-networks.html
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -278,4 +314,8 @@ from happening on re-deployment.
|
|||||||
|
|
||||||
|
|
||||||
.. _`Neutron Network Topologies`: https://docs.mirantis.com/openstack/fuel/fuel-7.0/reference-architecture.html#neutron-with-gre-segmentation-and-ovs
|
.. _`Neutron Network Topologies`: https://docs.mirantis.com/openstack/fuel/fuel-7.0/reference-architecture.html#neutron-with-gre-segmentation-and-ovs
|
||||||
.. _`official Mirantis OpenStack documentation`: https://docs.mirantis.com/openstack/fuel/fuel-7.0/user-guide.html#create-a-new-openstack-environment
|
.. _`official OpenStack Fuel documentation`: http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-user-guide/create-environment/start-create-env.html
|
||||||
|
.. _`Midokura Enterprise MidoNet (MEM) MidoNet Manager Guide`: http://docs.midokura.com/docs/latest-en/manager-guide/content/index.html
|
||||||
|
.. _`Midokura Enterprise MidoNet (MEM) Insights Guide`: http://docs.midokura.com/docs/latest-en/insights-guide/content/index.html
|
||||||
|
|
||||||
|
|
||||||
|
@ -13,7 +13,7 @@ Install the Plugin
|
|||||||
|
|
||||||
To install the MidoNet Fuel plugin:
|
To install the MidoNet Fuel plugin:
|
||||||
|
|
||||||
#. Download the plugin from the `Fuel Plugin Catalog`_
|
#. Download the plugin from the `Partner Community Catalog`_
|
||||||
|
|
||||||
#. Log into Fuel Master node and install the plugin using the `Fuel CLI`_:
|
#. Log into Fuel Master node and install the plugin using the `Fuel CLI`_:
|
||||||
|
|
||||||
@ -25,9 +25,10 @@ To install the MidoNet Fuel plugin:
|
|||||||
::
|
::
|
||||||
|
|
||||||
# fuel plugins
|
# fuel plugins
|
||||||
id | name | version | package_version
|
id | name | version | package_version | releases
|
||||||
---|---------|---------|----------------
|
---+---------+---------+-----------------+--------------------
|
||||||
9 | midonet | 4.1.0 | 4.0.0
|
1 | midonet | 4.1.0 | 4.0.0 | ubuntu (mitaka-9.0)
|
||||||
|
|
||||||
.. _`Fuel Plugin Catalog`: https://www.mirantis.com/products/openstack-drivers-and-plugins/fuel-plugins/
|
|
||||||
|
.. _`Partner Community Catalog`: https://www.mirantis.com/partners/midokura/
|
||||||
.. _`Fuel CLI`: http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-user-guide/cli.html
|
.. _`Fuel CLI`: http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-user-guide/cli.html
|
||||||
|
@ -1,6 +1,6 @@
|
|||||||
.. |FuelVer| replace:: 8.0
|
.. |FuelVer| replace:: 9.0/9.1
|
||||||
.. |PrevPluginVer| replace:: 3.0.1
|
.. |PrevPluginVer| replace:: 4.0.0
|
||||||
.. |PluginVer| replace:: 4.0.0
|
.. |PluginVer| replace:: 4.1.0
|
||||||
|
|
||||||
Document purpose
|
Document purpose
|
||||||
================
|
================
|
||||||
@ -29,5 +29,8 @@ Revision history
|
|||||||
(jaume@midokura.com)
|
(jaume@midokura.com)
|
||||||
4.1 09.05.2016 Samir Ibradzic Formatting changes
|
4.1 09.05.2016 Samir Ibradzic Formatting changes
|
||||||
|
|
||||||
|
(samir@midokura.com)
|
||||||
|
4.2 11.11.2016 Samir Ibradzic Adapt to Fuel 9
|
||||||
|
|
||||||
(samir@midokura.com)
|
(samir@midokura.com)
|
||||||
========= =============== ========================== =========================
|
========= =============== ========================== =========================
|
||||||
|