Merge "Clarify no controller setup for nova-network"
This commit is contained in:
commit
43084d2e47
@ -4,11 +4,15 @@
|
|||||||
version="5.0"
|
version="5.0"
|
||||||
xml:id="nova-network">
|
xml:id="nova-network">
|
||||||
<title>Enabling Networking</title>
|
<title>Enabling Networking</title>
|
||||||
<para>Configuring Networking can be one of the most bewildering experiences
|
<para>Configuring Networking can be one of the most bewildering experiences you will encounter
|
||||||
you will encounter when working with OpenStack. To assist in this we have
|
when working with OpenStack. To assist in this we have chosen the simplest production-ready
|
||||||
chosen the simplest production-ready configuration for this guide: the legacy
|
configuration for this guide: the legacy networking in OpenStack Compute, with a flat network,
|
||||||
networking in OpenStack Compute, with a flat network, that takes care of DHCP
|
that takes care of DHCP.</para>
|
||||||
and is made highly available by splitting across multiple hosts.</para>
|
<para>This setup uses "multi-host" functionality: the networking is configured to be highly
|
||||||
|
available by splitting networking functionality across multiple hosts. As a result, there is no
|
||||||
|
single network controller that acts as a single point of failure. Because each compute node is
|
||||||
|
configured for networking in this setup, no additional networking configuration is required on
|
||||||
|
the controller.</para>
|
||||||
<note><para>If you require the full software-defined networking stack, see <link
|
<note><para>If you require the full software-defined networking stack, see <link
|
||||||
linkend="ch_neutron">Using Neutron Networking</link>.</para></note>
|
linkend="ch_neutron">Using Neutron Networking</link>.</para></note>
|
||||||
<procedure>
|
<procedure>
|
||||||
|
Loading…
Reference in New Issue
Block a user