Converted HA networking info to RST
Only the active/active material was converted because active/passive is being depricated. This CR includes planning notes. We anticipate that this will be a very small section that links to the Networking Guide for details. Change-Id: I0bdd7f1596dbcad863be698f230facf86f5f08e2
This commit is contained in:
Meg McRoberts
parent
a2a3bb76db
commit
9df81efc90
|
|
@ -0,0 +1,17 @@
|
|||
|
||||
.. _dhcp-agent:
|
||||
|
||||
======================
|
||||
Run neutron DHCP agent
|
||||
======================
|
||||
|
||||
The OpenStack Networking service has a scheduler
|
||||
that lets you run multiple agents across nodes;
|
||||
the DHCP agent can be natively highly available.
|
||||
To configure the number of DHCP agents per network,
|
||||
modify the `dhcp_agents_per_network` parameter
|
||||
in the :file:`/etc/neutron/neutron.conf` file.
|
||||
By default this is set to 1.
|
||||
To achieve high availability,
|
||||
assign more than one DHCP agent per network.
|
||||
|
||||
|
|
@ -0,0 +1,37 @@
|
|||
|
||||
.. _neutron-l3:
|
||||
|
||||
====================
|
||||
Run neutron L3 agent
|
||||
====================
|
||||
|
||||
The neutron L3 agent is scalable, due to the scheduler that supports
|
||||
Virtual Router Redundancy Protocol (VRRP)
|
||||
to distribute virtual routers across multiple nodes.
|
||||
To enable high availability for configured routers,
|
||||
edit the :file:`/etc/neutron/neutron.conf` file
|
||||
to set the following values:
|
||||
|
||||
.. list-table:: /etc/neutron/neutron.conf parameters for high availability
|
||||
:widths: 15 10 30
|
||||
:header-rows: 1
|
||||
|
||||
* - Parameter
|
||||
- Value
|
||||
- Description
|
||||
* - l3_ha
|
||||
- True
|
||||
- All routers are highly available by default.
|
||||
* - allow_automatic_l3agent_failover
|
||||
- True
|
||||
- Set automatic L3 agent failover for routers
|
||||
* - max_l3_agents_per_router
|
||||
- 2 or more
|
||||
- Maximum number of network nodes to use for the HA router.
|
||||
* - min_l3_agents_per_router
|
||||
- 2 or more
|
||||
- Minimum number of network nodes to use for the HA router.
|
||||
A new router can be created only if this number
|
||||
of network nodes are available.
|
||||
|
||||
|
||||
|
|
@ -0,0 +1,17 @@
|
|||
|
||||
.. _neutron-lbaas:
|
||||
|
||||
=======================
|
||||
Run neutron LBaaS agent
|
||||
=======================
|
||||
|
||||
Currently, no native feature is provided
|
||||
to make the LBaaS agent highly available
|
||||
using the default plug-in HAProxy.
|
||||
A common way to make HAProxy highly available
|
||||
is to use the VRRP (Virtual Router Redundancy Protocol).
|
||||
Unfortunately, this is not yet implemented
|
||||
in the LBaaS HAProxy plug-in.
|
||||
|
||||
[TODO: update this section.]
|
||||
|
||||
|
|
@ -0,0 +1,18 @@
|
|||
|
||||
.. _neutron-metadata:
|
||||
|
||||
==========================
|
||||
Run neutron metadata agent
|
||||
==========================
|
||||
|
||||
No native feature is available
|
||||
to make this service highly available.
|
||||
At this time, the Active/Passive solution exists
|
||||
to run the neutron metadata agent
|
||||
in failover mode with Pacemaker.
|
||||
|
||||
[TODO: Update this information.
|
||||
Can this service now be made HA in active/active mode
|
||||
or do we need to pull in the instructions
|
||||
to run this service in active/passive mode?]
|
||||
|
||||
|
|
@ -1,4 +1,53 @@
|
|||
|
||||
=============================================
|
||||
Hardware considerations for high availability
|
||||
=============================================
|
||||
=======================
|
||||
OpenStack network nodes
|
||||
=======================
|
||||
|
||||
Configure networking on each node.
|
||||
The `Networking <http://docs.openstack.org/juno/install-guide/install/apt/content/ch_basic_environment.html#basics-prerequisites>`_
|
||||
section of the *Install Guide* includes basic information
|
||||
about configuring networking.
|
||||
|
||||
Notes from planning outline:
|
||||
|
||||
- Rather than configuring neutron here,
|
||||
we should simply mention physical network HA methods
|
||||
such as bonding and additional node/network requirements
|
||||
for L3HA and DVR for planning purposes.
|
||||
- Neutron agents shuld be described for active/active;
|
||||
deprecate single agent's instances case.
|
||||
- For Kilo and beyond, focus on L3HA and DVR.
|
||||
- Link to `Networking Guide <http://docs.openstack.org/networking-guide/>`_
|
||||
for configuration details.
|
||||
|
||||
[TODO: Verify that the active/passive
|
||||
network configuration information from
|
||||
`<http://docs.openstack.org/high-availability-guide/content/s-neutron-server.html>`_
|
||||
should not be included here.
|
||||
|
||||
`LP1328922 <https://bugs.launchpad.net/openstack-manuals/+bug/1328922>`
|
||||
and
|
||||
`LP1349398 <https://bugs.launchpad.net/openstack-manuals/+bug/1349398>`
|
||||
are related.]
|
||||
|
||||
OpenStack network nodes contain:
|
||||
|
||||
- :ref:`Neutron DHCP agent<dhcp-agent>`
|
||||
- Neutron L2 agent.
|
||||
Note that the L2 agent cannot be distributed and highly available.
|
||||
Instead, it must be installed on each data forwarding node
|
||||
to control the virtual network drivers
|
||||
such as Open vSwitch or Linux Bridge.
|
||||
One L2 agent runs per node and controls its virtual interfaces.
|
||||
- :ref:`Neutron L3 agent<neutron-l3>`
|
||||
- :ref:`Neutron metadata agent<neutron-metadata>`
|
||||
- :ref:`Neutron LBaaS<neutron-lbaas>` (Load Balancing as a Service) agent
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
|
||||
networking-ha-dhcp.rst
|
||||
networking-ha-l3.rst
|
||||
networking-ha-metadata.rst
|
||||
networking-ha-lbaas.rst
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue