Bug 2138356

Summary: [RFE][BDI] - Users are unable to set instance FQDN (neutron)
Product: Red Hat OpenStack Reporter: Riccardo Bruzzone <rbruzzon>
Component: openstack-neutronAssignee: OSP Team <rhos-maint>
Status: NEW --- QA Contact: Eran Kuris <ekuris>
Severity: high Docs Contact:
Priority: high    
Version: 17.1 (Wallaby)CC: bcafarel, chrisw, gurpsing, scohen
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Riccardo Bruzzone 2022-10-28 09:49:46 UTC 
[RFE][BDI] - Users are unable to set instance FQDN (nova)

BDI si asking the possibility to set their own FQDN (one subdomain for each Tenant domain)to the VMs deployed via Red Hat OpenStack.
From OSP 17.x the FIX planned for BZ#1919855 will be restored (it was relaxed in OSP 16.2) with the result that, starting from this OSP major release, nova unconditionally will turn all dots in the instance name into dashes, making the instance name a short name again.

About this point, the Customer is asking the possibility to manage the VM domain separately from the sanytized visual name planned in OSP 17.x 
    > [nova] Spec API

Customer is also asking the possibility to extend the subdomain management via DHCP as was covered in these two Specs withdrawn for OSP 17.x
    > [neutron] Support DNS subdomains at a network level 
    > [nova] Domain names in metadata