Bug 2138356 - [RFE][BDI] - Users are unable to set instance FQDN (neutron)
Summary: [RFE][BDI] - Users are unable to set instance FQDN (neutron)
Keywords:
Status: NEW
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 17.1 (Wallaby)
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
: ---
Assignee: OSP Team
QA Contact: Eran Kuris
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-10-28 09:49 UTC by Riccardo Bruzzone
Modified: 2023-08-01 08:54 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-19765 0 None None None 2022-10-28 10:05:35 UTC

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
Note You need to log in before you can comment on or make changes to this bug.