openstack-manuals/doc/install-guide/section_basics-networking-neutron.xml

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE section [
<!ENTITY % openstack SYSTEM "../common/entities/openstack.ent">
%openstack;
]>
<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="basics-networking-neutron">
  <?dbhtml stop-chunking?>
  <title>OpenStack Networking (neutron)</title>
  <para>The example architecture with OpenStack Networking (neutron) requires
    one controller node, one network node, and at least one compute node.
    The controller node contains one network interface on the
    <glossterm>management network</glossterm>. The network node contains
    one network interface on the management network, one on the
    <glossterm>instance tunnels network</glossterm>, and one on the
    <glossterm>external network</glossterm>. The compute node contains
    one network interface on the management network and one on the
    instance tunnels network.</para>
  <para>The example architecture assumes use of the following networks:</para>
  <itemizedlist>
    <listitem>
      <para>Management on 10.0.0.0/24 with gateway 10.0.0.1</para>
      <note>
        <para>This network requires a gateway to provide Internet
          access to all nodes for administrative purposes such as
          package installation, security updates,
          <glossterm>DNS</glossterm>, and
          <glossterm baseform="Network Time Protocol (NTP)"
          >NTP</glossterm>.</para>
      </note>
    </listitem>
    <listitem>
      <para>Instance tunnels on 10.0.1.0/24 without a gateway</para>
      <note>
        <para>This network does not require a gateway because communication
          only occurs among network and compute nodes in your OpenStack
          environment.</para>
      </note>
    </listitem>
    <listitem>
      <para>External on 203.0.113.0/24 with gateway 203.0.113.1</para>
      <note>
        <para>This network requires a gateway to provide Internet
          access to instances in your OpenStack environment.</para>
      </note>
    </listitem>
  </itemizedlist>
  <para>You can modify these ranges and gateways to work with your
    particular network infrastructure.</para>
  <note>
    <para>Network interface names vary by distribution. Traditionally,
      interfaces use "eth" followed by a sequential number. To cover all
      variations, this guide simply refers to the first interface as the
      interface with the lowest number, the second interface as the
      interface with the middle number, and the third interface as the
      interface with the highest number.</para>
  </note>
  <figure>
    <title>Minimal architecture example with OpenStack Networking
      (neutron)&mdash;Network layout</title>
    <mediaobject>
      <imageobject>
        <imagedata contentwidth="6in"
          fileref="../common/figures/installguidearch-neutron-networks.png"/>
      </imageobject>
    </mediaobject>
  </figure>
  <para>Unless you intend to use the exact configuration provided in this
    example architecture, you must modify the networks in this procedure to
    match your environment. Also, each node must resolve the other nodes
    by name in addition to IP address. For example, the
    <replaceable>controller</replaceable> name must resolve to
    <literal>10.0.0.11</literal>, the IP address of the management
    interface on the controller node.</para>
  <warning>
    <para>Reconfiguring network interfaces will interrupt network
      connectivity. We recommend using a local terminal session for these
      procedures.</para>
  </warning>
  <section xml:id="basics-neutron-networking-controller-node">
    <title>Controller node</title>
    <procedure>
      <title>To configure networking:</title>
      <step>
        <para>Configure the first interface as the management interface:</para>
        <para>IP address: 10.0.0.11</para>
        <para>Network mask: 255.255.255.0 (or /24)</para>
        <para>Default gateway: 10.0.0.1</para>
      </step>
      <step>
        <para>Reboot the system to activate the changes.</para>
      </step>
    </procedure>
    <procedure>
      <title>To configure name resolution:</title>
      <step>
        <para>Set the hostname of the node to
          <code><replaceable>controller</replaceable></code>.</para>
      </step>
      <step>
        <para>Edit the <filename>/etc/hosts</filename> file to contain the
          following:</para>
        <programlisting># controller
10.0.0.11       controller

# network
10.0.0.21       network

# compute1
10.0.0.31       compute1</programlisting>
        <warning>
          <para>Some distributions add an extraneous entry in the
             <filename>/etc/hosts</filename> file that resolves the actual
             hostname to another loopback IP address such as
             <literal>127.0.1.1</literal>. You must comment out or remove
             this entry to prevent name resolution problems.</para>
        </warning>
      </step>
    </procedure>
  </section>
  <section xml:id="basics-neutron-networking-network-node">
    <title>Network node</title>
    <procedure>
      <title>To configure networking:</title>
      <step>
        <para>Configure the first interface as the management interface:</para>
        <para>IP address: 10.0.0.21</para>
        <para>Network mask: 255.255.255.0 (or /24)</para>
        <para>Default gateway: 10.0.0.1</para>
      </step>
      <step>
        <para>Configure the second interface as the instance tunnels
          interface:</para>
        <para>IP address: 10.0.1.21</para>
        <para>Network mask: 255.255.255.0 (or /24)</para>
      </step>
      <step>
        <para>The external interface uses a special configuration without an
          IP address assigned to it. Configure the third interface as the
          external interface:</para>
        <para>Replace <replaceable>INTERFACE_NAME</replaceable> with the
          actual interface name. For example, <emphasis>eth2</emphasis> or
          <emphasis>ens256</emphasis>.</para>
        <substeps>
          <step os="ubuntu;debian">
            <para>Edit the <filename>/etc/network/interfaces</filename> file
              to contain the following:</para>
            <programlisting># The external network interface
auto <replaceable>INTERFACE_NAME</replaceable>
iface <replaceable>INTERFACE_NAME</replaceable> inet manual
        up ip link set dev $IFACE up
        down ip link set dev $IFACE down</programlisting>
          </step>
          <step os="rhel;centos;fedora">
            <para>Edit the
              <filename>/etc/sysconfig/network-scripts/ifcfg-<replaceable>INTERFACE_NAME</replaceable></filename>
              file to contain the following:</para>
            <para>Do not change the <literal>HWADDR</literal> and
              <literal>UUID</literal> keys.</para>
            <programlisting>DEVICE=<replaceable>INTERFACE_NAME</replaceable>
TYPE=Ethernet
ONBOOT="yes"
BOOTPROTO="none"</programlisting>
          </step>
          <step os="sles;opensuse">
            <para>Edit the
              <filename>/etc/sysconfig/network/ifcfg-<replaceable>INTERFACE_NAME</replaceable></filename> file to
              contain the following:</para>
            <programlisting>STARTMODE='auto'
BOOTPROTO='static'</programlisting>
          </step>
        </substeps>
      </step>
      <step>
        <para>Reboot the system to activate the changes.</para>
      </step>
    </procedure>
    <procedure>
      <title>To configure name resolution:</title>
      <step>
        <para>Set the hostname of the node to <code>network</code>.</para>
      </step>
      <step>
        <para>Edit the <filename>/etc/hosts</filename> file to contain the
          following:</para>
        <programlisting># network
10.0.0.21       network

# controller
10.0.0.11       controller

# compute1
10.0.0.31       compute1</programlisting>
        <warning>
          <para>Some distributions add an extraneous entry in the
             <filename>/etc/hosts</filename> file that resolves the actual
             hostname to another loopback IP address such as
             <literal>127.0.1.1</literal>. You must comment out or remove
             this entry to prevent name resolution problems.</para>
        </warning>
      </step>
    </procedure>
  </section>
  <section xml:id="basics-neutron-networking-compute-node">
    <title>Compute node</title>
    <procedure>
      <title>To configure networking:</title>
      <step>
        <para>Configure the first interface as the management interface:</para>
        <para>IP address: 10.0.0.31</para>
        <para>Network mask: 255.255.255.0 (or /24)</para>
        <para>Default gateway: 10.0.0.1</para>
        <note>
          <para>Additional compute nodes should use 10.0.0.32, 10.0.0.33,
            and so on.</para>
        </note>
      </step>
      <step>
        <para>Configure the second interface as the instance tunnels
          interface:</para>
        <para>IP address: 10.0.1.31</para>
        <para>Network mask: 255.255.255.0 (or /24)</para>
        <note>
          <para>Additional compute nodes should use 10.0.1.32, 10.0.1.33,
            and so on.</para>
        </note>
      </step>
      <step>
        <para>Reboot the system to activate the changes.</para>
      </step>
    </procedure>
    <procedure>
      <title>To configure name resolution:</title>
      <step>
        <para>Set the hostname of the node to <code>compute1</code>.</para>
      </step>
      <step>
        <para>Edit the <filename>/etc/hosts</filename> file to contain the
          following:</para>
        <programlisting># compute1
10.0.0.31       compute1

# controller
10.0.0.11       controller

# network
10.0.0.21       network</programlisting>
        <warning>
          <para>Some distributions add an extraneous entry in the
             <filename>/etc/hosts</filename> file that resolves the actual
             hostname to another loopback IP address such as
             <literal>127.0.1.1</literal>. You must comment out or remove
             this entry to prevent name resolution problems.</para>
        </warning>
      </step>
    </procedure>
  </section>
  <section xml:id="basics-neutron-networking-verify">
    <title>Verify connectivity</title>
    <para>We recommend that you verify network connectivity to the Internet
      and among the nodes before proceeding further.</para>
    <procedure>
      <step>
        <para>From the <emphasis>controller</emphasis> node,
          <command>ping</command> a site on the Internet:</para>
        <screen><prompt>#</prompt> <userinput>ping -c 4 openstack.org</userinput>
<computeroutput>PING openstack.org (174.143.194.225) 56(84) bytes of data.
64 bytes from 174.143.194.225: icmp_seq=1 ttl=54 time=18.3 ms
64 bytes from 174.143.194.225: icmp_seq=2 ttl=54 time=17.5 ms
64 bytes from 174.143.194.225: icmp_seq=3 ttl=54 time=17.5 ms
64 bytes from 174.143.194.225: icmp_seq=4 ttl=54 time=17.4 ms

--- openstack.org ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3022ms
rtt min/avg/max/mdev = 17.489/17.715/18.346/0.364 ms</computeroutput></screen>
      </step>
      <step>
        <para>From the <emphasis>controller</emphasis> node,
        <command>ping</command> the management interface on the
        <emphasis>network</emphasis> node:</para>
        <screen><prompt>#</prompt> <userinput>ping -c 4 <replaceable>network</replaceable></userinput>
<computeroutput>PING network (10.0.0.21) 56(84) bytes of data.
64 bytes from network (10.0.0.21): icmp_seq=1 ttl=64 time=0.263 ms
64 bytes from network (10.0.0.21): icmp_seq=2 ttl=64 time=0.202 ms
64 bytes from network (10.0.0.21): icmp_seq=3 ttl=64 time=0.203 ms
64 bytes from network (10.0.0.21): icmp_seq=4 ttl=64 time=0.202 ms

--- network ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3000ms
rtt min/avg/max/mdev = 0.202/0.217/0.263/0.030 ms</computeroutput></screen>
      </step>
      <step>
        <para>From the <emphasis>controller</emphasis> node,
        <command>ping</command> the management interface on the
        <emphasis>compute</emphasis> node:</para>
        <screen><prompt>#</prompt> <userinput>ping -c 4 <replaceable>compute1</replaceable></userinput>
<computeroutput>PING compute1 (10.0.0.31) 56(84) bytes of data.
64 bytes from compute1 (10.0.0.31): icmp_seq=1 ttl=64 time=0.263 ms
64 bytes from compute1 (10.0.0.31): icmp_seq=2 ttl=64 time=0.202 ms
64 bytes from compute1 (10.0.0.31): icmp_seq=3 ttl=64 time=0.203 ms
64 bytes from compute1 (10.0.0.31): icmp_seq=4 ttl=64 time=0.202 ms

--- network ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3000ms
rtt min/avg/max/mdev = 0.202/0.217/0.263/0.030 ms</computeroutput></screen>
      </step>
      <step>
        <para>From the <emphasis>network</emphasis> node,
          <command>ping</command> a site on the Internet:</para>
        <screen><prompt>#</prompt> <userinput>ping -c 4 openstack.org</userinput>
<computeroutput>PING openstack.org (174.143.194.225) 56(84) bytes of data.
64 bytes from 174.143.194.225: icmp_seq=1 ttl=54 time=18.3 ms
64 bytes from 174.143.194.225: icmp_seq=2 ttl=54 time=17.5 ms
64 bytes from 174.143.194.225: icmp_seq=3 ttl=54 time=17.5 ms
64 bytes from 174.143.194.225: icmp_seq=4 ttl=54 time=17.4 ms

--- openstack.org ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3022ms
rtt min/avg/max/mdev = 17.489/17.715/18.346/0.364 ms</computeroutput></screen>
      </step>
      <step>
        <para>From the <emphasis>network</emphasis> node,
          <command>ping</command> the management interface on the
          <emphasis>controller</emphasis> node:</para>
        <screen><prompt>#</prompt> <userinput>ping -c 4 <replaceable>controller</replaceable></userinput>
<computeroutput>PING controller (10.0.0.11) 56(84) bytes of data.
64 bytes from controller (10.0.0.11): icmp_seq=1 ttl=64 time=0.263 ms
64 bytes from controller (10.0.0.11): icmp_seq=2 ttl=64 time=0.202 ms
64 bytes from controller (10.0.0.11): icmp_seq=3 ttl=64 time=0.203 ms
64 bytes from controller (10.0.0.11): icmp_seq=4 ttl=64 time=0.202 ms

--- controller ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3000ms
rtt min/avg/max/mdev = 0.202/0.217/0.263/0.030 ms</computeroutput></screen>
      </step>
      <step>
        <para>From the <emphasis>network</emphasis> node,
          <command>ping</command> the instance tunnels interface on the
          <emphasis>compute</emphasis> node:</para>
        <screen><prompt>#</prompt> <userinput>ping -c 4 10.0.1.31</userinput>
<computeroutput>PING 10.0.1.31 (10.0.1.31) 56(84) bytes of data.
64 bytes from 10.0.1.31 (10.0.1.31): icmp_seq=1 ttl=64 time=0.263 ms
64 bytes from 10.0.1.31 (10.0.1.31): icmp_seq=2 ttl=64 time=0.202 ms
64 bytes from 10.0.1.31 (10.0.1.31): icmp_seq=3 ttl=64 time=0.203 ms
64 bytes from 10.0.1.31 (10.0.1.31): icmp_seq=4 ttl=64 time=0.202 ms

--- 10.0.1.31 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3000ms
rtt min/avg/max/mdev = 0.202/0.217/0.263/0.030 ms</computeroutput></screen>
      </step>
      <step>
        <para>From the <emphasis>compute</emphasis> node,
          <command>ping</command> a site on the Internet:</para>
        <screen><prompt>#</prompt> <userinput>ping -c 4 openstack.org</userinput>
<computeroutput>PING openstack.org (174.143.194.225) 56(84) bytes of data.
64 bytes from 174.143.194.225: icmp_seq=1 ttl=54 time=18.3 ms
64 bytes from 174.143.194.225: icmp_seq=2 ttl=54 time=17.5 ms
64 bytes from 174.143.194.225: icmp_seq=3 ttl=54 time=17.5 ms
64 bytes from 174.143.194.225: icmp_seq=4 ttl=54 time=17.4 ms

--- openstack.org ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3022ms
rtt min/avg/max/mdev = 17.489/17.715/18.346/0.364 ms</computeroutput></screen>
      </step>
      <step>
        <para>From the <emphasis>compute</emphasis> node,
          <command>ping</command> the management interface on the
          <emphasis>controller</emphasis> node:</para>
        <screen><prompt>#</prompt> <userinput>ping -c 4 <replaceable>controller</replaceable></userinput>
<computeroutput>PING controller (10.0.0.11) 56(84) bytes of data.
64 bytes from controller (10.0.0.11): icmp_seq=1 ttl=64 time=0.263 ms
64 bytes from controller (10.0.0.11): icmp_seq=2 ttl=64 time=0.202 ms
64 bytes from controller (10.0.0.11): icmp_seq=3 ttl=64 time=0.203 ms
64 bytes from controller (10.0.0.11): icmp_seq=4 ttl=64 time=0.202 ms

--- controller ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3000ms
rtt min/avg/max/mdev = 0.202/0.217/0.263/0.030 ms</computeroutput></screen>
      </step>
      <step>
        <para>From the <emphasis>compute</emphasis> node,
          <command>ping</command> the instance tunnels interface on the
          <emphasis>network</emphasis> node:</para>
        <screen><prompt>#</prompt> <userinput>ping -c 4 10.0.1.21</userinput>
<computeroutput>PING 10.0.1.21 (10.0.1.21) 56(84) bytes of data.
64 bytes from 10.0.1.21 (10.0.1.21): icmp_seq=1 ttl=64 time=0.263 ms
64 bytes from 10.0.1.21 (10.0.1.21): icmp_seq=2 ttl=64 time=0.202 ms
64 bytes from 10.0.1.21 (10.0.1.21): icmp_seq=3 ttl=64 time=0.203 ms
64 bytes from 10.0.1.21 (10.0.1.21): icmp_seq=4 ttl=64 time=0.202 ms

--- 10.0.1.21 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3000ms
rtt min/avg/max/mdev = 0.202/0.217/0.263/0.030 ms</computeroutput></screen>
      </step>
    </procedure>
  </section>
</section>