Users can create ports for IPs outside of allocation_pool

- Indicated that the pool of allocated IPs is set by their cloud provider
- User would actually see the bug when deleting a port, but we don't
document that procedure.
- To close the bug, will also update the Networking API 2.0 doc

Change-Id: I94fafd62a7f9b66dfcf2392186801d6a1e935cd6
Partial-bug: 1078013
This commit is contained in:
Anne Gentle 2014-04-21 12:14:50 -05:00
parent 4bb27a9906
commit df8fe30fe5

View File

@ -198,6 +198,12 @@ export OS_AUTH_URL=http://localhost:5000/v2.0</programlisting>
ip_address=192.168.2.40</literal> is an
option, which specifies the port's fixed IP
address we wanted.</para>
<note>
<para>When creating a port, you can specify any unallocated
IP in the subnet even if the address is not in a
pre-defined pool of allocated IP addresses (set by your
cloud provider).</para>
</note>
</step>
<step>
<para>Create a port without specified IP
@ -220,9 +226,10 @@ export OS_AUTH_URL=http://localhost:5000/v2.0</programlisting>
| status | DOWN |
| tenant_id | 3671f46ec35e4bbca6ef92ab7975e463 |
+----------------------+------------------------------------------------------------------------------------+</computeroutput></screen>
<para>We can see that the system will allocate one IP
address if we do not specify the IP address in
command line.</para>
<note>
<para>Note that the system allocates one IP address if you
do not specify an IP address in the <command>neutron
port-create</command> command.</para></note>
</step>
<step>
<para>Query ports with specified fixed IP