Using CCQ

ccqsub Command and Arguments

CCQ is a wrapper for common schedulers such as Torque and Slurm. It gives the schedulers autoscaling capability within GCP. When a user submits a job using this script, the job script will be parsed, the number of instances needed determined, and the instances will be launched for the job at run-time. Commands that are specified in the job script take precedence over the options specified on the command line. These commands can be denoted inside of the jobscript itself by using the #CC directive.

The commands that are available through the #CC directive are -it (instance type), -nt (network type), -ni (number of instances requested), -op (optimization type), -p (criteria priority), -cpu (number of CPUs requested), -mem (amount of memory in MB requested), -s (scheduler to use), -st (scheduler type), -jn (job name), -vt (volume type), -up (use preemptible).

Each command must appear on its own line with the #CC directive.

CCQ also understands several #PBS and #SBATCH directives. These will control instance type if it is not explicitly requested. CCQ will ignore any line which contains directives which it does not understand, but they will be passed through to the underlying scheduler.

The output files from the job will appear in the CloudyCluster user’s home directory on the instance the job was submitted from by default if you are using a CloudyCluster instance to submit your files. However there may be a minute or two delay between when the job finishes and when the files appear on the machine the job was submitted from due to extra processing needed.

If you submit from a host outside of CloudyCluster the output files will be stored in the CloudyCluster user’s home directory on the Login Instance associated with the Cluster that the job was submitted to. This behavior can be changed by specifying the -o and -e PBS directives in your job scripts or using the -o and -e ccqsub command line arguments. These tell the scheduler to output the files to the directories specified inside of the job script instead of the defaults. If an output file is missing check the /opt/CloudyCluster/ccqsub/undeliveredJobOutput/{CloudyCluster_user_name} directory on the Scheduler the job was submitted on as this is the default directory for undeliverable job output files.

Billing

All instances started will be given the label ccuser with the present username as the value. The label ccbilling can be added with the -pj option. These labels are intended to track the amount spent on a per user or per project basis. If ccbilling is added, the label ccbillinguser will also be added with the value project-user where project is the name of the project and user is the name of the user.


CCQ Submit

This is the list of possible options that can be used with ccqsub. The CCQ Directive may be used with CCQ in a job script.

- usage: | ccqsub

GPU with ccqsub

CloudyCluster allows you to leverage the powser of GPU processing speed by calling the GPU compute node configuration when submitting your job to the scheduler.