af8571d858
Found by running the python misspellings package Change-Id: I6a1b4ee5dee54a4c5adc9780718b258ba20f4d53
40 lines
1.5 KiB
Plaintext
40 lines
1.5 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 that
|
|
lets you run multiple agents across nodes. Also, the DHCP agent can be natively
|
|
highly available. For details, see http://docs.openstack.org/trunk/config-reference/content/app_demo_multi_dhcp_agents.html[OpenStack Configuration Reference].
|
|
|
|
==== Running Neutron L3 Agent
|
|
|
|
Since the Grizzly release, the Neutron L3 Agent is scalable thanks to the scheduler
|
|
that 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. See 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. See the Active /
|
|
Passive section of this guide.
|