openstack-manuals/doc/install-guide/section_networking-neutron-server-install.xml
annegentle 931398af0a The neutron install chapter didn't have yum package names
Also fixed minor typo (restart not start) in nova-controller.

Change-Id: Idbd306a6c65f3221e31c04511634aa1a2d30c110
Closes-bug: 1240210
2013-10-15 15:58:24 -05:00

110 lines
6.1 KiB
XML
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

<?xml version="1.0" encoding="UTF-8"?>
<section 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="install_neutron_server">
<title>Install neutron-server</title>
<para>The <systemitem class="service"
>neutron-server</systemitem> handles OpenStack Networking's
user requests and exposes the API.<procedure>
<title>To install the neutron-server</title>
<step>
<para>Install neutron-server and CLI for accessing the
API:</para>
<screen os="ubuntu;debian"><prompt>$</prompt> <userinput>sudo apt-get install neutron-server python-neutronclient</userinput> </screen>
<screen os="rhel;centos;fedora"><prompt>#</prompt> <userinput>yum install openstack-neutron python-neutronclient</userinput></screen>
</step>
<step>
<para>You must also install the plugin you choose to use,
for example:</para>
<screen os="ubuntu;debian"><prompt>$</prompt><userinput>sudo apt-get install neutron-plugin-openvswitch</userinput></screen>
<screen os="rhel;centos;fedora"><prompt>#</prompt> <userinput>yum install openstack-neutron-openvswitch</userinput></screen>
</step>
<step>
<para>Most plugins require that you install a database and
configure it in a plugin configuration file.</para>
<para>If you already use a database for other OpenStack
services, you only need to create a neutron
database:</para>
<screen os="ubuntu;debian"><prompt>$</prompt><userinput>mysql -u &lt;user&gt; -p &lt;pass&gt; -e “create database neutron”</userinput></screen>
</step>
<step>
<para>Configure the database in the plugins configuration
file:</para>
<substeps>
<step>
<para>Find the plugin configuration file in
<filename>/etc/neutron/plugins/&lt;plugin-name&gt;</filename>
(for example,
<filename>/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini</filename>).
</para>
</step>
<step>
<para>Set in the file:</para>
<screen><computeroutput>sql_connection = mysql://&lt;user&gt;:&lt;password&gt;@localhost/neutron?charset=utf8</computeroutput></screen>
</step>
</substeps>
</step>
</procedure></para>
<section xml:id="rpc_setup">
<title>RPC Setup</title>
<para>Many OpenStack Networking plugins use RPC to enable
agents to communicate with the main <systemitem
class="service">neutron-server</systemitem> process. If
your plugin requires agents, they can use the same RPC
mechanism used by other OpenStack components like Nova.
These are installed in the Basic Operating System Configuration.</para>
<important>
<para>The <filename>/etc/neutron/neutron.conf</filename>
file should be copied to and used on all hosts running
<systemitem class="service">neutron-server</systemitem>
or any <systemitem class="service"
>neutron-*-agent</systemitem> binaries.</para>
</important>
</section>
<section xml:id="openvswitch_plugin">
<title>Plugin Configuration: OVS Plugin</title>
<para>If you use the Open vSwitch (OVS) plugin in a deployment
with multiple hosts, you will need to use either tunneling
or vlans to isolate traffic from multiple networks.
Tunneling is easier to deploy because it does not require
configuring VLANs on network switches.</para>
<para>The following procedure uses tunneling:</para>
<para>
<procedure>
<title>To configure OpenStack Networking to use the OVS
plugin</title>
<step>
<para>Edit
<filename>/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini
</filename> to specify the following values (for
database configuration, see <xref
linkend="install_neutron_server"/>):</para>
<screen><computeroutput>enable_tunneling=True tenant_network_type=gre tunnel_id_ranges=1:1000 # only required for nodes running agents local_ip=&lt;data-net-IP-address-of-node&gt;</computeroutput></screen>
</step>
<step>
<para>If you are using the neutron DHCP agent, add the
following to
<filename>/etc/neutron/dhcp_agent.ini</filename>:</para>
<screen><computeroutput>dnsmasq_config_file=/etc/neutron/dnsmasq-neutron.conf</computeroutput></screen>
</step>
<step>
<para>Create
<filename>/etc/neutron/dnsmasq-neutron.conf</filename>,
and add the following values to lower the MTU size on
instances and prevent packet fragmentation over the
GRE tunnel:</para>
<screen><computeroutput>dhcp-option-force=26,1400</computeroutput></screen>
</step>
<step>
<para>After performing that change on the node running
<systemitem class="service"
>neutron-server</systemitem>, restart <systemitem
class="service">neutron-server</systemitem> to pick
up the new settings:</para>
<screen><prompt>$</prompt><userinput>sudo service neutron-server restart</userinput></screen>
</step>
</procedure>
</para>
</section>
</section>