Sets hostname and FQDN of the node. The latest code is hosted at https://github.com/3ofcoins/chef-cookbook-hostname
Setting hostname on FQDN is not (and won't be) supported. Unfortunately, using dots in the hostname can cause inconsistent results for any system that consumes DNS and is not allowed by RFC952. If a user needs additional info in their shell prompt, they can change PS1 in etc/profile to include the FQDN together with any information they find useful (such as the customer, the environment, etc).
node['set_fqdn']- FQDN to set.
The asterisk character will be replaced with
node.name. This way,
you can add this to base role:
default_attributes :set_fqdn => '*.project-domain.com'
and have node set its FQDN and hostname based on its chef node name
(which is provided on
chef-client first run's command line).
node['hostname_cookbook']['hostsfile_ip']-- IP used in
/etc/hoststo correctly set FQDN (default:
node['hostname_cookbook']['hostsfile_aliases']-- list of aliases used in
/etc/hostsfor the ip set above (default: [
node['hostname_cookbook']['hostsfile_include_hostname_in_aliases']-- whether to include the hostname at the end of the aliases list above (default: true)
node['hostname_cookbook']['append_hostsfile_ip']-- Set to
falseto prevent an entry for the node's hostname from being appended in
hostname::default-- will set node's FQDN to value of
set_fqdnattribute, and hostname to its host part (up to first dot).
hostname::vmware-- sets hostname automatically using vmtoolsd. You do not need to set
Author: Maciej Pasternacki email@example.com