Clarify no controller setup for nova-network

Add some text to make it clearer that no network config is required
on the controller when using multi-host with nova network.

backport: havana

Change-Id: Idf81fa399207ba39ee7979317cbd8ab72c320c32
This commit is contained in:
Lorin Hochstein 2013-10-25 11:27:19 -04:00
parent 86a9df0868
commit 8ac12422f2

View File

@ -4,11 +4,15 @@
version="5.0"
xml:id="nova-network">
<title>Enabling Networking</title>
<para>Configuring Networking can be one of the most bewildering experiences
you will encounter when working with OpenStack. To assist in this we have
chosen the simplest production-ready configuration for this guide: the legacy
networking in OpenStack Compute, with a flat network, that takes care of DHCP
and is made highly available by splitting across multiple hosts.</para>
<para>Configuring Networking can be one of the most bewildering experiences you will encounter
when working with OpenStack. To assist in this we have chosen the simplest production-ready
configuration for this guide: the legacy networking in OpenStack Compute, with a flat network,
that takes care of DHCP.</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
linkend="ch_neutron">Using Neutron Networking</link>.</para></note>
<procedure>