Harald Jensås b72fa56599 Set dns_name propery on ports and networks ... Neutron's dns_assignments field includes a nice pice of structured data. This is a prerequirement for Designate usage. (No plan's to use that, but being a bit ready does'nt hurt.) {"hostname": "my-vm", "ip_address": "192.0.2.16", "fqdn": "my-vm.example.org."} Enable for the undercloud: - dns_domain_ports ml2 extension driver Need to backport this to train because network-v2 idempotency rely on the dns_doman. In Ie326f30fcc3d93533f4269cdfec40d3634684e22 idempotency was change to use dns_domain instead of a neutron tag with the hostname because of neutron's limit on 60 chars per tag. Without this change the provisioning workflow will create duplicate ports when FFU upgrade is performed. Conflicts: overcloud.j2.yaml Closes-Bug: #1970936 Change-Id: I46eb9a24dd66821b27524fe4d1fdab617b6fa948 (cherry picked from commit 679ecaada0)		2022-04-29 14:19:18 +02:00
..
all_nodes	Remove mac_hostname & random_string	2019-07-18 19:10:31 +00:00
nova_metadata/krb-service-principals	Fix krb-service-principals with service_net_map_replace	2020-02-24 19:41:32 +00:00
post_deploy	Set dns_name propery on ports and networks	2022-04-29 14:19:18 +02:00