openstack/neutron
Code Issues Proposed changes

Documentation for adding extra port conflict fix

Browse Source 
Notes added to notify the user about the change of
behaviour in dns_name when conflict happens

Change-Id: I56132ef4f569cfe931612cfafbc865e8f599fefe
This commit is contained in:
hamalq 2020-10-22 18:19:24 +00:00 committed by Rodolfo Alonso
parent c9708e692f
commit 6501ebc6ca
2 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/source/admin/config-dns-int-ext-serv.rst
View File

@ -117,6 +117,12 @@ the following:
will fail.
#. Create a floating IP and associate it to the port.
.. note::
To avoid dns_name conflicts in designate if the dns_name already exists
in designate zone records a dns_name is generated using the IP of the
port like dns_name.ip_hash, this helps also in the case of adding
multiple ports to the same instance
Following is an example of these steps:
.. code-block:: console

6
doc/source/admin/config-dns-int.rst
View File

@ -134,6 +134,12 @@ its display name. As a consequence, at the end of the boot process, the
allocated ports will be known in the dnsmasq associated to their networks by
their instance ``hostname``.
.. note::
To avoid dns_name conflicts in designate if the dns_name already exists
in designate zone records a dns_name is generated using the IP of the
port like dns_name.ip_hash, this helps also in the case of adding
multiple ports to the same instance
The following is an example of an instance creation, showing how its
``hostname`` populates the ``dns_name`` attribute of the allocated port: