We see the short name in all of the xCAT keys. When the node is installed,
"hostname" returns the short name, and not the FQDN. This short name is set
by /etc/sysconfig/network, in contrast to /etc/hosts and DNS, which have the
FQDN listed first. (See end of first thread post for details.) BTW. We
manage our /etc/hosts and DNS outside of xCAT.
We're running 2.7.4, but I don't remember if our hostnames were any different
with previous versions.
BTW. The dhcpd.leases file contains the short name as well:
host develkv8 {
dynamic;
hardware ethernet 00:25:90:49:34:e8;
fixed-address 149.77.53.121;
supersede server.ddns-hostname = "develkv8";
supersede host-name = "develkv8";
if option vendor-class-identifier = "ScaleMP" {
supersede server.filename = "vsmp/pxelinux.0";
} else {
supersede server.filename = "pxelinux.0";
}
supersede server.next-server = 95:4d:35:fc;
}
Thanks
From: Russell Jones [mailto:[email protected]]
Sent: Tuesday, November 20, 2012 4:51 PM
To: [email protected]
Subject: Re: [xcat-user] Can a short hostname be converted to a FQDN during an
install?
> We'd like to use short hostnames as all of our keys in the xCAT tables, to
> save typing, and have the FQDN assigned as the hostname after an install.
This should already be the standard behavior as long as your nodeadd contained
the short hostname and not the FQDN. What are you seeing on your end?
On 11/20/2012 3:22 PM, Pocina, Goran wrote:
We'd like to use short hostnames as all of our keys in the xCAT tables, to save
typing, and have the FQDN assigned as the hostname after an install.
We could fix the hostname with a postscript, or perhaps a Kickstart statement,
however we'd prefer to have it done more transparently.
It would be great if we could use something like a regex in
"network.nodehostname="/\z/.nyc.desres.deshaw.com/" to do this automatically:
[root@drdkvm0003 dump1]# lsdef -t network 149_77_52_0-255_255_254_0
Object name: 149_77_52_0-255_255_254_0
ddnsdomain=nyc.desres.deshaw.com
domain=nyc.desres.deshaw.com
dynamicrange=149.77.53.132-149.77.53.191
gateway=149.77.52.10
mask=255.255.254.0
mgtifname=!remote!
nameservers=149.77.52.53,149.77.52.35,10.232.15.130
net=149.77.52.0
nodehostname=/\z/.nyc.desres.deshaw.com/
ntpservers=149.77.52.24,149.77.52.41,149.77.52.138,149.77.52.129
tftpserver=149.77.53.252
But this doesn't seem to have any effect on the DHCP host-name entry generated
in the leases file, or on the "HOSTNAME=develkv8" entry put in
/etc/sysconfig/network after the install.
BTW. We do have the FQDN listed first in /etc/hosts and DNS:
[root@develkv8 ~]# hostname
develkv8
[root@develkv8 ~]# host 149.77.53.121
121.53.77.149.in-addr.arpa domain name pointer develkv8.nyc.desres.deshaw.com.
[root@develkv8 ~]# grep develkv8 /etc/hosts
>>> 149.77.53.121 develkv8.nyc.desres.deshaw.com develkv8 #
>>> row 0 rack 0 rank 0
Is there a transparent way to do this?
Thanks.
------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
xCAT-user mailing list
[email protected]<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/xcat-user
------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user
