Full FQDN should be set if passed in nova boot call
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| OpenStack Compute (nova) |
Wishlist
|
Brian Lamar |
Bug Description
If I create a new host with a fully-qualified domain name, the hostname is set to the FQDN with the periods removed.
Example:
nova boot nova1.broadpool.net --flavor 3 --image 2
results in the hostname of the server being set to "nova1broadpool
Glen Campbell (glen-campbell) wrote : | #2 |
Yes, since that's what the person intended. Otherwise, you're merely creating extra work for people that's in no way required. In the case of Rackspace, it breaks backwards compatibility with our legacy cloud servers, which properly sets the FQDN if that's what the server name is.
If I set the server name to "nova1.
summary: |
- Periods are removed from host name + Full FQDN should be set if passed in nova boot call |
Changed in nova: | |
importance: | Undecided → Wishlist |
status: | Incomplete → Confirmed |
Changed in nova: | |
assignee: | nobody → Brian Lamar (blamar) |
Brian Lamar (blamar) wrote : | #3 |
We should at the very least be following RFCs 952 and 1123 which allow for periods in hostnames. After that it's up to the agent to correctly set the hostname on the instance. I have a patch that I'll be submitting which addresses this.
Reviewed: https:/
Committed: http://
Submitter: Jenkins
Branch: master
status fixcommitted
done
commit bcfff3dd530994d
Author: Brian Lamar <email address hidden>
Date: Wed Nov 9 18:16:24 2011 -0500
Follow hostname RFCs
Updated hostname sanitization method to more closely follow RFC-952
and RFC-1123. Also moved it to nova.utils, where it seems to fit
better.
Fixes bug 885374
(Patch Set 1) Updated hostname sanitization with more efficient and
Change-Id: I60d7ee89867c05
Changed in nova: | |
status: | Confirmed → Fix Committed |
Changed in nova: | |
milestone: | none → essex-2 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | essex-2 → 2012.1 |
The current code only sets a hostname (not a domain name), and reuses the name provided in the nova boot call as a hint, stripping all characters that are not acceptable for a hostname (including the period). I am not really sure that should be changed... Are you asking that we also set the domain name on the VMs we create ?