677865def5
According to bug #1284633, the configuration included with nova packages on SUSE apparently doesn't default to nova-networking. We should avoid implicit configuration assumptions on all distributions and explicitly configure the following keys in nova.conf on the controller and compute nodes for nova-networking: network_api_class = nova.network.api.API security_group_api = nova Prior to this issue, we only included compute node configuration for nova-networking. I added a new section for the controller node to resolve this issue. This patch also includes some minor structural changes and clarifications to conform with other portions of the guide. Change-Id: I8224f32062f279b6032aa06ee0a72ea28f549a4d Closes-Bug: #1284633
74 lines
3.4 KiB
XML
74 lines
3.4 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<chapter xmlns="http://docbook.org/ns/docbook"
|
|
xmlns:xi="http://www.w3.org/2001/XInclude"
|
|
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"
|
|
xml:id="ch_networking">
|
|
<title>Add a networking service</title>
|
|
<!-- FIXME Temporarily replacing this warning.
|
|
<warning>
|
|
<para>This chapter is a bit more adventurous than we would
|
|
like. We are working on cleanup and improvements to it.
|
|
Like for the rest of the Installation Guide, feedback
|
|
through bug reports and patches to improve it are
|
|
welcome.</para>
|
|
</warning>
|
|
-->
|
|
<warning>
|
|
<para>We are updating this material for Icehouse. You may find
|
|
structure and/or content issues during this process.</para>
|
|
</warning>
|
|
<para>Configuring networking in OpenStack can be a bewildering
|
|
experience. This guide provides step-by-step instructions for both
|
|
OpenStack Networking (neutron) and the legacy networking (nova-network)
|
|
service. If you are unsure which to use, we recommend trying
|
|
OpenStack Networking because it offers a considerable number of
|
|
features and flexibility including <glossterm baseform="plug-in"
|
|
>plug-ins</glossterm> for a variety of emerging products
|
|
supporting <glossterm>virtual networking</glossterm>. See the
|
|
<link
|
|
xlink:href="http://docs.openstack.org/admin-guide-cloud/content/ch_networking.html"
|
|
>Networking</link> chapter of the <citetitle>OpenStack Cloud
|
|
Administrator Guide</citetitle> for more information.</para>
|
|
<section xml:id="section_neutron-networking">
|
|
<title>Networking (neutron)</title>
|
|
<xi:include href="section_neutron-concepts.xml"/>
|
|
<section xml:id="section_neutron-networking-ml2">
|
|
<title>Modular Layer 2 (ML2) plug-in</title>
|
|
<note>
|
|
<para>We primarily tested the Modular Layer 2 (ML2) plug-in on
|
|
Icehouse and suggest that you implement it instead of the
|
|
traditional Open vSwitch (OVS) plug-in.</para>
|
|
</note>
|
|
<xi:include href="section_neutron-ml2-controller-node.xml"/>
|
|
<xi:include href="section_neutron-ml2-network-node.xml"/>
|
|
<xi:include href="section_neutron-ml2-compute-node.xml"/>
|
|
</section>
|
|
<section xml:id="section_neutron-networking-ovs">
|
|
<title>Open vSwitch (OVS) plug-in</title>
|
|
<warning>
|
|
<para>We suggest that you implement the Modular Layer 2 (ML2) plug-in
|
|
on Icehouse until we completely test the traditional Open vSwitch
|
|
(OVS) plug-in.</para>
|
|
</warning>
|
|
<xi:include href="section_neutron-ovs-controller-node.xml"/>
|
|
<xi:include href="section_neutron-ovs-network-node.xml"/>
|
|
<xi:include href="section_neutron-ovs-compute-node.xml"/>
|
|
</section>
|
|
<xi:include href="section_neutron-initial-networks.xml"/>
|
|
</section>
|
|
<section xml:id="section_nova-networking">
|
|
<title>Legacy networking</title>
|
|
<xi:include href="section_nova-networking-controller-node.xml"/>
|
|
<xi:include href="section_nova-networking-compute-node.xml"/>
|
|
<xi:include href="section_nova-networking-initial-network.xml"/>
|
|
</section>
|
|
<section xml:id="section_networking_next_steps">
|
|
<title>Next steps</title>
|
|
<para>
|
|
Your OpenStack environment now includes the core components necessary
|
|
to launch a basic instance. You can
|
|
<link linkend="launch-instance">launch an instance</link> or add more
|
|
services to your environment in the following chapters.</para>
|
|
</section>
|
|
</chapter>
|