9980b9ad52
Extend microversion 2.90 to allow FQDNs in the hostname parameter. Multi-create with --hostname continues to be refused, returning error 400 to the user. This simplifies the code by not needing to handle any sort of suffix or prefix mangling of the FQDN to handle multiple instances. No other changes are made - not Neutron integration, metadata API changes (the FQDN will appear as-is in places where the hostname currently appears), etc. Change-Id: I47e397dc6da8263762479cc8ae4f8777a6d9d811 Implements: bp/fqdn-in-hostname
23 lines
1.1 KiB
YAML
23 lines
1.1 KiB
YAML
---
|
|
features:
|
|
- |
|
|
The 2.94 microversion has been added. This microversion extends
|
|
microversion 2.90 by allowing Fully Qualified Domain Names (FQDN) wherever
|
|
the ``hostname`` is able to be specified. This consists of creating an
|
|
instance (``POST /servers``), updating an instance
|
|
(``PUT /servers/{id}``), or rebuilding an instance
|
|
(``POST /servers/{server_id}/action (rebuild)``). When using an FQDN as the
|
|
instance hostname, the ``[api]dhcp_domain`` configuration option must be
|
|
set to the empty string in order for the correct FQDN to appear in the
|
|
``hostname`` field in the metadata API.
|
|
|
|
upgrade:
|
|
- |
|
|
In order to make use of microversion's 2.94 FQDN hostnames, the
|
|
``[api]dhcp_domain`` config option must be set to the empty string. If
|
|
this is not done, the ``hostname`` field in the metadata API will be
|
|
incorrect, as it will include the value of ``[api]dhcp_domain`` appended to
|
|
the instance's FQDN. Note that simply not setting ``[api]dhcp_domain`` is
|
|
not enough, as it has a default value of ``novalocal``. It must explicitly
|
|
be set to the empty string.
|