This page describes the steps required to start a new instance of the Stage VM and configure the VM to setup an operational Grid Gateway.
Download the VM
Download the VM from a known location [Are we going to provide this for all or do we say contact xyz@uab.edu to get a copy of the VM].
Convert VM for use on VMware ESX
To create disk files that are compatible with VMware ESX, use the command-line program vmfsktools to convert the disk files.
# cd /directory/where/vmfiles/were/extracted # mkdir /directory/for/converted/files # vmkfstools -i /directory/where/vmfiles/were/extracted/diskfile.vmdk /directory/for/converted/files/diskfile.vmdk # cp nvram *.vmsd *.vmx /directory/for/converted/files
Set up the New VM
Configure a new VM to use the disk file located in /directory/for/converted/files, and start the VM as per usual. Depending on your environment, you may need to set up DHCP server entries for this MAC address and change the client to use DHCP to get its network information (currently, it comes configured with a static IP).
Configuring the VM
We need to perform several cleanup operations to remove host-specific configurations that were done on the original image on stage.uabgrid.uab.edu
0. Make sure the date and time are set correctly. I noticed that there was a time lag, I had to fix the time.
1. Set the new hostname. I have used the following to set the hostname:
# cat > hostname.txt gridgateway.cis.uab.edu ^D # hostname --file hostname.txt
2. Remove user home directories (it worked out great that my home directory was available but we had to remove other users home directories).
3. Corresponding to the home directories removed, we also need to remove the corresponding entries from the grid-mapfile.
4. Remove the files: /etc/grid-security/host{cert,key}.pem and /etc/grid-security/container{cert,key}.pem.
5. Create a new host certificate request following the instructions at http://dev.uabgrid.uab.edu/uabgrid-ca/wiki/BuildingUABgridCA#RequestingUABgridCredentials. Once you have obtained the signed host certificate copy it to /etc/grid-security directory and execute the following commands in the /etc/grid-security directory:
# cp hostcert.pem containercert.pem # cp hostkey.pem containerkey.pem # chown globus:globus container*.pem # ls -l *.pem -r-------- 1 root root 887 Oct 17 15:37 hostkey.pem -rw-r--r-- 1 root root 1473 Oct 20 08:16 hostcert.pem -rw-r--r-- 1 globus globus 1473 Oct 20 08:45 containercert.pem -r-------- 1 globus globus 887 Oct 20 08:45 containerkey.pem
6. Restart the Globus Container:
# /etc/init.d/globus restart
7. Login as user "gwadmin" and start the GridWay daemon (update the file $GW_LOCATION/etc/gwd.conf appropriately to include the resources that you would like to be part of GridWay hostlist):
# su - gwadmin [gwadmin@gridgateway ~]$ gwd -m [gwadmin@gridgateway ~]$
8. Login as a user with valid credentials and test GridWay.
[puri@gridgateway ~]$ gwhost
HID PRIO OS ARCH MHZ %CPU MEM(F/T) DISK(F/T) N(U/F/T) LRMS HOSTNAME
0 1 Linux2.6.9-42.0 x86_6 3200 200 3473/3943 53993/63479 0/115/115 SGE olympus.cis.uab.edu
1 1 NULLNULL NULL 0 0 0/0 0/0 0/25/25 SGE everest.cis.uab.edu
[puri@gridgateway ~]$ cat gwtest.jt
EXECUTABLE = /bin/uname
ARGUMENTS = -a
STDIN_FILE = /dev/null
STDOUT_FILE = gw.out.${JOB_ID}
STDERR_FILE = gw.err.${JOB_ID}
REQUIREMENTS = HOSTNAME = "everest.cis.uab.edu"
[puri@gridgateway ~]$ gwsubmit -v -t gwtest.jt
JOB ID: 1
[puri@gridgateway ~]$ gwps
USER JID DM EM START END EXEC XFER EXIT NAME HOST
puri 1 pend ---- 14:44:10 --:--:-- 0:00:00 0:00:00 -- gwtest.jt --
[puri@gridgateway ~]$ gwps
USER JID DM EM START END EXEC XFER EXIT NAME HOST
puri 1 done ---- 14:44:10 14:45:10 0:00:32 0:00:01 0 gwtest.jt everest.cis.uab.edu/SGE
[puri@gridgateway ~]$ cat gw.out.1
Linux compute-0-21.local 2.6.18-53.1.14.el5 #1 SMP Wed Mar 5 11:37:38 EST 2008 x86_64 x86_64 x86_64 GNU/Linux
[puri@gridgateway ~]$
