ccb80d725d
Updated a typo (keystone-mange -> keystone-manage) Updated a few capitalization errors in titles Change-Id: I38ec2a6c53b9e3a1e1bf330b54c26f293a764d94 author: diane fleming
135 lines
8.2 KiB
XML
135 lines
8.2 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<section xml:id="manage_ip_addresses"
|
|
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">
|
|
<title>Manage IP addresses</title>
|
|
<para>Each instance can have a private, or <emphasis role="italic"
|
|
>fixed</emphasis>, IP address and an IP address, often
|
|
public, that is movable from instance to instance called a
|
|
<emphasis role="italic">floating</emphasis> IP
|
|
address.</para>
|
|
<para>Private IP addresses are used for communication between
|
|
instances and public ones are used for communication with the
|
|
outside world.</para>
|
|
<para>When you launch an instance, it is automatically assigned a
|
|
private IP address that stays the same until you explicitly
|
|
terminate the instance. Rebooting an instance has no effect on
|
|
its private IP address.</para>
|
|
<para>The cloud operator must configure a pool of floating IP
|
|
addresses. Then, you can allocate a certain number of floating
|
|
IP addresses from this pool to a project. A project quota
|
|
defines the maximum number of floating IP addresses for the
|
|
project.</para>
|
|
<para>You can add a floating IP address from this pool to an
|
|
instance in the project. You can dynamically associate
|
|
floating IP addresses with or disassociate floating IP
|
|
addresses from instances in the same project at any
|
|
time.</para>
|
|
<para>Before you can assign a floating IP address to an instance,
|
|
you must allocate floating IP addresses to a project. After
|
|
you allocate floating IP addresses to the current project, you
|
|
can assign them to running instances.</para>
|
|
<para>You can assign one floating IP address to only one instance
|
|
at a time. Use the <command>nova *floating-ip-*</command>
|
|
commands to manage floating IP addresses.</para>
|
|
<procedure>
|
|
<title>To manage floating IP addresses</title>
|
|
<step>
|
|
<para>To list the floating IP address pools:</para>
|
|
<screen><prompt>$</prompt> <userinput>nova floating-ip-pool-list</userinput>
|
|
<computeroutput>+--------+
|
|
| name |
|
|
+--------+
|
|
| public |
|
|
| test |
|
|
+--------+</computeroutput></screen>
|
|
<note>
|
|
<para>If this list is empty, the cloud operator must configure a pool of floating IP
|
|
addresses.</para>
|
|
</note>
|
|
</step>
|
|
<step>
|
|
<para>To allocate a floating IP address to the current
|
|
project:</para>
|
|
<screen><prompt>$</prompt> <userinput>nova floating-ip-create</userinput>
|
|
<computeroutput>+--------------+-------------+----------+--------+
|
|
| Ip | Instance Id | Fixed Ip | Pool |
|
|
+--------------+-------------+----------+--------+
|
|
| 172.24.4.226 | None | None | public |
|
|
+--------------+-------------+----------+--------+</computeroutput></screen>
|
|
<para>By default, the floating IP address is allocated
|
|
from the <literal>public</literal> pool. The command
|
|
shows the allocated IP address.</para>
|
|
<para>If more than one IP address pool is available, you
|
|
can specify the pool from which to allocate the
|
|
address:</para>
|
|
<screen><prompt>$</prompt> <userinput>nova floating-ip-create <replaceable>POOL_NAME</replaceable></userinput></screen>
|
|
</step>
|
|
<step>
|
|
<para>To list floating IP addresses that are allocated to
|
|
the current project:</para>
|
|
<screen><prompt>$</prompt> <userinput>nova floating-ip-list</userinput>
|
|
<computeroutput>+--------------+--------------------------------------+----------+--------+
|
|
| Ip | Instance Id | Fixed Ip | Pool |
|
|
+--------------+--------------------------------------+----------+--------+
|
|
| 172.24.4.225 | 4a60ff6a-7a3c-49d7-9515-86ae501044c6 | 10.0.0.2 | public |
|
|
| 172.24.4.226 | None | None | public |
|
|
+--------------+--------------------------------------+----------+--------+</computeroutput></screen>
|
|
<para>For each floating IP address that is allocated to
|
|
the current project, the command shows the floating IP
|
|
address, the ID for the instance to which the floating
|
|
IP address is assigned, the associated fixed IP
|
|
address, and the pool from which the floating IP
|
|
address was allocated.</para>
|
|
</step>
|
|
<step>
|
|
<para>To associate a floating IP address with an instance,
|
|
first allocate that address to the current
|
|
project:</para>
|
|
<screen><prompt>$</prompt> <userinput>nova floating-ip-create</userinput>
|
|
<computeroutput>+--------------+-------------+----------+--------+
|
|
| Ip | Instance Id | Fixed Ip | Pool |
|
|
+--------------+-------------+----------+--------+
|
|
| 172.24.4.226 | None | None | public |
|
|
+--------------+-------------+----------+--------+</computeroutput></screen>
|
|
<para>List instances to get the instance ID:</para>
|
|
<screen><prompt>$</prompt> <userinput>nova list</userinput>
|
|
<computeroutput>+--------------------------------------+-------------+--------+------------+-------------+--------------------------------+
|
|
| ID | Name | Status | Task State | Power State | Networks |
|
|
+--------------------------------------+-------------+--------+------------+-------------+--------------------------------+
|
|
| 4a60ff6a-7a3c-49d7-9515-86ae501044c6 | my-instance | ACTIVE | None | Running | private=10.0.0.2, 172.24.4.225 |
|
|
+--------------------------------------+-------------+--------+------------+-------------+--------------------------------+</computeroutput></screen>
|
|
<para>Then, assign the floating IP address to the
|
|
instance, as follows:</para>
|
|
<screen><prompt>$</prompt> <userinput>nova add-floating-ip my-instance 172.24.4.226</userinput></screen>
|
|
<para>Notice that the instance is now associated with two
|
|
floating IP addresses:</para>
|
|
<screen><prompt>$</prompt> <userinput>nova list</userinput>
|
|
<computeroutput>+--------------------------------------+-------------+--------+------------+-------------+----------------------------------------------+
|
|
| ID | Name | Status | Task State | Power State | Networks |
|
|
+--------------------------------------+-------------+--------+------------+-------------+----------------------------------------------+
|
|
| 4a60ff6a-7a3c-49d7-9515-86ae501044c6 | my-instance | ACTIVE | None | Running | private=10.0.0.2, 172.24.4.225, 172.24.4.226 |
|
|
+--------------------------------------+-------------+--------+------------+-------------+----------------------------------------------+</computeroutput></screen>
|
|
<para>To assign a fixed IP address to a floating IP
|
|
address that you assign to an instance, add the fixed
|
|
IP address as an optional parameter:</para>
|
|
<screen><prompt>$</prompt> <userinput>nova add-floating-ip --fixed-address=<replaceable>FIXED_IP_ADDRESS</replaceable> <replaceable>INSTANCE_NAME_OR_ID</replaceable> <replaceable>FLOATING_IP_ADDRESS</replaceable></userinput></screen>
|
|
<para>After you assign the floating IP address and
|
|
configure security group rules for the instance, the
|
|
instance is publicly available at the floating IP
|
|
address.</para>
|
|
</step>
|
|
<step>
|
|
<para>To release a floating IP address from the current
|
|
project:</para>
|
|
<screen><prompt>$</prompt> <userinput>nova floating-ip-delete <replaceable>FLOATING_IP_ADDRESS</replaceable></userinput></screen>
|
|
<para>The floating IP address is returned to the floating
|
|
IP address pool that is available to all projects. If
|
|
a floating IP address is assigned to a running
|
|
instance, it is automatically disassociated from that
|
|
instance.</para>
|
|
</step>
|
|
</procedure>
|
|
</section>
|