cclscratch00.cse.nd.edu cclscratch01.cse.nd.edu cclscratch02.cse.nd.edu cclscratch03.cse.nd.eduUse ssh to connect to these machines. Accounts were created for everyone in the class at the beginning of the semester. If you do not have an account (perhaps you registered late) email the instructor. (Don't wait until the last minute.) If you find one of these machines to be overloaded or unresponsive, you can always log into another one.
For a warm up assignment, you will make some observations about several Condor pools, and then learn how to submit simple jobs. To begin, read these two pages:
Exercise 0: Create a directory called /tmp/YOURNAME. Make it private by executing chmod 700 /tmp/YOURNAME. Move to that directory, and use it to store any temporary files that you may create in this assignment. If you want to keep any data that you create, copy it to your home directory when done.
Exercise 1: Answer the following questions about each of the Notre Dame, Purdue, and Wisconsin Condor pools.
Hint: Use the condor_status command. To show data for Purdue and Wisconsin, use the -pool flamingo.rcac.purdue.edu and -pool condor.cs.wisc.edu options. There is much more information about each machine than is shown by default. Use the -l option to display absolutely everything. To pick out different values, try this command:
condor_status -format "%s\t" Name -format "%d\t" TotalMemory -format "%d\t" TotalCpus -format "%d\t" Disk -format "%d\n" Mips
Exercise 2: Submit one Condor job that simply runs the following script and returns the output:
#!/bin/sh uname -a date
Once you are 100 percent sure that one job works correctly, then write a single condor_submit script that submits one thousand jobs like the one above, each writing output to a separate file. Make sure that your submit script generates a user log file as follows:
log = userlog.logOnce the batch is complete, the file userlog.log will tell you everything that Condor did on your behalf to execute the jobs.