261584eb60
Changed sentence structure "there exists" is not correct moved exists to the end of the sentence in 2 places across is spelled with 1 c (fixed typo) Change-Id: I8ed0794375e7c5126459a2921934473b54b72984
41 lines
1.6 KiB
Plaintext
41 lines
1.6 KiB
Plaintext
[[ha-aa-network]]
|
|
=== OpenStack Network Nodes
|
|
|
|
OpenStack Network Nodes contains:
|
|
|
|
* Neutron DHCP Agent
|
|
* Neutron L2 Agent
|
|
* Neutron L3 Agent
|
|
* Neutron Metadata Agent
|
|
* Neutron LBaaS Agent
|
|
|
|
NOTE: The Neutron L2 Agent does not need to be highly available. It has to be
|
|
installed on each Data Forwarding Node and controls the virtual networking
|
|
drivers as Open-vSwitch or Linux Bridge. One L2 agent runs per node
|
|
and controls its virtual interfaces. That's why it cannot be distributed and
|
|
highly available.
|
|
|
|
|
|
==== Running Neutron DHCP Agent
|
|
|
|
Since the Grizzly release, OpenStack Networking service has a scheduler which
|
|
allows to run multiple agents accross nodes. Also, the DHCP agent can be natively
|
|
highly available. Please follow the http://docs.openstack.org/trunk/config-reference/content/app_demo_multi_dhcp_agents.html[OpenStack Configuration Reference] for
|
|
further details.
|
|
|
|
==== Running Neutron L3 Agent
|
|
|
|
Since the Grizzly release, the Neutron L3 Agent is scalable thanks to the scheduler
|
|
which allows distribution of virtual routers across multiple nodes.
|
|
But there is no native feature to make these routers highly available.
|
|
At this time, the Active / Passive solution exists to run the Neutron L3
|
|
agent in failover mode with Pacemaker. Please refer to the Active / Passive
|
|
section of this guide.
|
|
|
|
==== Running Neutron Metadata Agent
|
|
|
|
There is no native feature 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. Please refer to the Active /
|
|
Passive section of this guide.
|