diff --git a/doc/admin-guide-cloud/ch_networking.xml b/doc/admin-guide-cloud/ch_networking.xml index 10f5550d67..21a4730c8b 100644 --- a/doc/admin-guide-cloud/ch_networking.xml +++ b/doc/admin-guide-cloud/ch_networking.xml @@ -20,6 +20,5 @@ - diff --git a/doc/admin-guide-cloud/networking/section_networking_high_avail.xml b/doc/admin-guide-cloud/networking/section_networking_high_avail.xml deleted file mode 100644 index 71a8fb3b4f..0000000000 --- a/doc/admin-guide-cloud/networking/section_networking_high_avail.xml +++ /dev/null @@ -1,51 +0,0 @@ - -
- High availability - The use of high availability in a Networking deployment - helps mitigate the impact of individual node failures. In general, you - can run neutron-server and neutron-dhcp-agent in an - active/active - fashion. - You can run the neutron-l3-agent service - as active/passive, - which avoids IP - conflicts with respect - to gateway IP addresses. -
- Networking high availability with Pacemaker - You can run some Networking services in a cluster - configuration (active/passive or active/active for - Networking server only) with Pacemaker. - Download the latest resources agents: - - - neutron-server: https://github.com/madkiss/openstack-resource-agents - - - neutron-dhcp-agent: https://github.com/madkiss/openstack-resource-agents - - - neutron-l3-agent: https://github.com/madkiss/openstack-resource-agents - - - - For information about how to build a cluster, - see Pacemaker documentation. - -
-