I don't know of a way to make xCAT work the way you're asking, but to get around this in the past I have gone 1 of 2 routes:
1. Manually define all external hostnames such that external routable hostnames do not have a -iface ( ed. -eth1) suffix. Then I set the system hostname in postscripting by editing /etc/sysconfig/network file (/etc/HOSTNAME in IIRC) before the reboot. This would leave me with something like login01.cluster.net on the internal net and hpclogin01.customer.com on the routable customer net. 2. Define all hosts in the hosts table and use the hosts.hostnames field to define aliases. In this instance, my internal hostname is the same as above, but my external hostname would be login01-eth0.customer.com with an alias (defined on the xCAT MN) of hpclogin01.customer.com. Again, I would set the system hostname in postscripting the same as above. As for setting internal hostnames, leaving off the suffix makes administrative tasks on larger clusters somewhat easier (eg. nodeset node1-node4000 shell), but there's nothing saying you can't have your nodes named the way you want them while maintaining the use of node ranges: nodeadd node[001-100]-e0 groups=... nodeset node[001-100]-e0 In some instances, I've even created internal node names that cumbersome and made each node a member of it's own group: nodeadd plcompts1a groups=node001,compute... The only limitation to that approach that I've seen is you can't use 'rcons node001' since 'node001' is a group and rcons will only work on a single node. 'wcons' works fine with this config. Hope that helps. Regards, Christian Caruthers Senior Consultant - System x Linux HPC Mobile: 757-289-9872 -----Original Message----- From: Allison Andrews [mailto:[email protected]] Sent: Friday, March 06, 2015 6:34 PM To: [email protected] Subject: [xcat-user] managing names in a multiple network environment. Hi, I was wondering if someone could answer one of my xCAT questions. In xCAT, you give a node a name, and xcat by default associates that name with the IP address that the node installs itself via. In our world, This will be a private management interface on an unroutable network(10.0.0.0/24 for example) which should be named <nodename>-e0. When generating /etc/hosts etc, xCAT will assign the base hostname to that IP address(e.g. <nodename> would be 10.0.0.32, rather than the public routeable interface 128.xx.yy.zz) and allow you to name other interfaces by either adding a prefix, or suffix to the name on a per-interface basis. this scheme would result in a hosts table like: 10.0.0.32 <nodename> <nodename>.<domainname> # install interface. 128.xx.yy.zz <nodename>-pub <nodename>-pub.<domainname> # additional routeable interface I'd like the routeable interface to get the unadorned name, and for the management net to get an -e0 suffix. This would result in a hosts table like: 10.0.0.32 <nodename>-e0 <nodename>-e0.<domainname> # install interface. 128.xx.yy.zz <nodename> <nodename>.<domainname> # additional routeable interface I'd expect this would be a problem for anyone wanting to install over a non-routable management network(you'd presumably want users coming in over the routeable interface to be able to use the unadorned name.) How do folks deal with this? Is this an unusual configuration? do people just live with addorned names like <nodename>-pub for their outward facing network interfaces? -Allie ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ xCAT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcat-user ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ xCAT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcat-user
