openstack
/
openstack-manuals
Code Issues Proposed changes

Be explicit about the use of the default flag for external networks 

Users may attempt to set the flag on regular networks, but currently
it has no effect. That may change in the future, when/if we expand
the feature use cases.

Closes-bug: #1691340
Related-bug: #1690439

Change-Id: I42df1bdc3eca4bfb829b111960e87f8bed8b9b82
(cherry picked from commit 158e5e499c)
This commit is contained in:
Armando Migliaccio 2017-05-17 12:15:54 -07:00
parent 908dbe6a47
commit e71ce42d0b
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/networking-guide/source/config-auto-allocation.rst
View File

@ -33,13 +33,19 @@ topology creation. To perform this task, proceed with the following steps:
`OpenStack Administrator Guide
<http://docs.openstack.org/admin-guide/networking-adv-features.html>`_.
Assuming the external network to be used for the auto-allocation feature
is named ``public``, make it the default external network
is named ``public``, make it the ``default`` external network
with the following command:
.. code-block:: console
$ neutron net-update public --is-default=True
.. note::
The flag ``--default`` (and ``--no-default`` flag) is only effective
with external networks and has no effects on regular (or internal)
networks.
#. Create default subnetpools
The auto-allocation feature requires at least one default