Open topic with navigation

You are here: 1.0 Deploying the Operating Systems > Deploying Compute Nodes

1.4 Deploying Compute Nodes
  1. Create the Linux and Windows tftpboot configuration files.

    1.4.1 Sample files for single disk systems:

    Windows: 

    DEFAULT windows
PROMPT 0
TIMEOUT 30
LABEL windows
  KERNEL chain.c32
  APPEND hd0 1
LABEL linux
  KERNEL chain.c32
  APPEND hd0 2

    Linux: 

    DEFAULT linux
PROMPT 0
TIMEOUT 30
LABEL windows
  KERNEL chain.c32
  APPEND hd0 1
LABEL linux
  KERNEL chain.c32
  APPEND hd0 2

    1.4.2 Sample files for dual disk systems:

    Windows: 

    DEFAULT windows
PROMPT 0
TIMEOUT 30
LABEL windows
  KERNEL chain.c32
  APPEND hd0 1
LABEL linux
  KERNEL chain.c32
  APPEND hd1 1

    Linux: 

    DEFAULT linux
PROMPT 0
TIMEOUT 30
LABEL windows
  KERNEL chain.c32
  APPEND hd0 1
LABEL linux
  KERNEL chain.c32
  APPEND hd1 1
  2. Set up the env.hpc shipped with the MSMHPC_tools to reflect your environment.

    env.hpc

    export RMNAME=MSMHPC
export PUBKEY=user
export DOMAIN=SGE
export  PROXY=http://WINDOWSHEADNODE:5343/MSMHPC
export  PRIVKEYFILE=/root/moab-private.cfg
    NoteThe DOMAIN variable does not need to be the full domain name, but should match the login domain, such as DOMAIN\user.

    moab-private.cfg: 

    CLIENTCFG[RM:MSMHPC] KEY=moab
  3. Run the deploy.hpc.node.pl script to deploy a new node. 
    > . ./env.hpc
> /root/MSMHPC_tools/MSMHPC/scripts/deploy.hpc.node.pl
USAGE: ./deploy.hpc.node.pl  <NODENAME> <MACADDRESS> <NODE TEMPLATE> <DOMAIN NAME>
ie: ./deploy.hpc.node.pl node01  AA:BB:CC:DD:EE:FF "Default ComputeNode Template" MYDOMAIN at  /root/MSMHPC_tools/MSMHPC/scripts/deploy.hpc.node.pl line 26.
> /root/MSMHPC_tools/MSMHPC/scripts/deploy.hpc.node.pl node01 00:50:56:35:bb:cc  "Default ComputeNode Template" SGE
  4. Check in the HPC Cluster Manager to see if the node is ready to be provisioned.
  5. Start the compute node, ensuring that it is set up to PXE boot. The compute node starts deploying Windows.
  6. When Windows finishes deploying, change the dhcpd.conf file so that the Linux deployment can start. 
    host node01 {
fixed-address      10.0.0.101;
hardware ethernet 00:50:56:35:bb:cc;
option host-name    "node01";
next-server        10.0.0.200;
filename           "pxelinux.0";
#next-server        10.0.0.100;
#filename           "Boot\\x64\\WdsNbp.com";
#option domain-name-servers 10.0.0.100;
}
  7. Restart the DHCPD service.
  8. Create a symlink for the compute node's address. Point it to a file with the same name as the compute node, and point that file to the kickstart or autoyast tftp boot file. 
    ln –sf NODE01 01-00-50-56-35-bb-cc
ln –sf kickstart NODE01
    ln –sf NODE01 01-00-50-56-35-bb-cc
ln –sf autoyast NODE01
    NoteNote that the 01 at the beginning of the mac address is needed for PXE booting.
  9. Reboot the compute node to start the Linux deployment. You can immediately change the configuration so that the node boots to Linux when the deployment finishes. 
    ln –sf linux NODE01
Note To enable centralized authentication, give the Linux host a different name from the Windows host name. This allows both operating systems to be joined simultaneously in the domain. To do this:
  1. Name the Windows node node01 and the Linux node node01l.
  2. Create the necessary aliases in /etc/hosts directory of the machine that runs the pbs_server daemon.
  3. Include only the Windows name in the /var/spool/torque/server_priv/nodes file so that TORQUE reports the same node name and Moab can map the cluster state on all the resource managers.

Copyright © 2011 Adaptive Computing Enterprises, Inc.®