openstack-manuals/doc/install-guide/section_nova-networking-initial-network.xml
Matt Kassawara 17fc8c8a8b Release candidate updates for Networking chapter
As part of the installation guide improvement project, I performed
the following operations on the Networking chapter:

1) Moved Neutron ML2 sections before OVS sections and updated
   associated notes to steer users toward ML2.
2) Removed database population steps because Neutron populates the
   database at first run.
3) Moved 'enable_security_group' key to [securitygroup] section.
4) Removed extraneous colons from procedure titles.
5) Added command output to Neutron initial networks section.
6) Added command output to Nova initial networks section.

Change-Id: Ie677d199d2c64ef2a564eaa551295e1a321db02c
Partial-Bug: #1291071
Implements: blueprint networking-install-guide-improvements
2014-04-10 21:16:47 -06:00

56 lines
2.8 KiB
XML

<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="nova-network-initial-network">
<title>Create initial network</title>
<para>Before launching your first instance, you must create the necessary
virtual network infrastructure to which the instance will connect.
This network typically provides internet access
<emphasis>from</emphasis> instances. You can enable internet access
<emphasis>to</emphasis> individual instances using a
<glossterm>floating IP address</glossterm> and suitable
<glossterm>security group</glossterm> rules. The <literal>admin</literal>
tenant owns this network because it provides external network access
for multiple tenants.</para>
<para>This network shares the same <glossterm>subnet</glossterm>
associated with the physical network connected to the external
<glossterm>interface</glossterm> on the compute node. You should specify
an exclusive slice of this subnet to prevent interference with other
devices on the external network.</para>
<note>
<para>Perform these commands on the controller node.</para>
</note>
<procedure>
<title>To create the network</title>
<step>
<para>Source the <literal>admin</literal> tenant credentials:</para>
<screen><prompt>$</prompt> <userinput>source admin-openrc.sh</userinput></screen>
</step>
<step>
<para>Create the network:</para>
<para>Replace <replaceable>NETWORK_CIDR</replaceable> with the subnet
associated with the physical network.</para>
<screen><prompt>$</prompt> <userinput>nova network-create demo-net --bridge br100 --multi-host T \
--fixed-range-v4 <replaceable>NETWORK_CIDR</replaceable></userinput></screen>
<para>For example, using an exclusive slice of
<literal>203.0.113.0/24</literal> with IP address range
<literal>203.0.113.24</literal> to <literal>203.0.113.32</literal>:
</para>
<screen><prompt>$</prompt> <userinput>nova network-create demo-net --bridge br100 --multi-host T \
--fixed-range-v4 203.0.113.24/29</userinput></screen>
<note>
<para>This command provides no output.</para>
</note>
</step>
<step>
<para>Verify creation of the network:</para>
<screen><prompt>$</prompt> <userinput>nova net-list</userinput>
<computeroutput>+--------------------------------------+----------+------------------+
| ID | Label | CIDR |
+--------------------------------------+----------+------------------+
| 84b34a65-a762-44d6-8b5e-3b461a53f513 | demo-net | 203.0.113.24/29 |
+--------------------------------------+----------+------------------+</computeroutput></screen>
</step>
</procedure>
</section>