Dynamic Cluster only.
Modifies jobs with the specified Dynamic Cluster templates that the job can use. Specify the name of one or more Dynamic Cluster templates that the job can use, or use the any or none keywords. Separate names in the list with space. Using this option makes the job use Dynamic Cluster provisioning.
Specify -dc_tmpl none to use none of the templates, and the job also ignores the -dc_mtype and -dc_vmaction options.
When you define Dynamic Cluster templates on the command line, DC_MACHINE_TEMPLATES in lsb.applications is ignored.
Dynamic Cluster only.
Cancels previous -dc_tmpl settings.
Dynamic Cluster only.
Modifies the Dynamic Cluster job to run on a particular type of machine. This value is ignored if -dc_tmpl is not also used or if you used -dc_tmpl none.
Specify -dc_mtype vm if you want the Dynamic Cluster job to be a VM job.
Specify -dc_mtype pm if you want the job to run on physical machines.
By default, Dynamic Cluster jobs run on any machines. The syntax -dc_mtype any is supported to specify this explicitly (physical machines are selected before virtual machines).
When you define Dynamic Cluster templates on the command line, DC_MACHINE_TYPE in lsb.applications is ignored.
The default value for -dc_mtype is -dc_mytype any if you modify a job that was previously not a Dynamic Cluster and specify -dc_tmpl without specifying a value for -dc_mtype.
Dynamic Cluster only.
Modifies the preemption action for the Dynamic Cluster job. This value is ignored if -dc_tmpl and -dc_mtype vm are not also used or if you used -dc_tmpl none. Specify -dc_vmaction action to specify an action on the VM if this job is preempted.
The following are a list of preemption actions that you can specify with this option:
-dc_vmaction savevm: Save the VM.
Saving the VM allows this job to continue later on. This option defines the action that the lower priority (preempted) job should take upon preemption, not the one the higher priority (preempting) job should initiate.
-dc_vmaction livemigvm: Live migrate the VM (and the jobs running on them) from one hypervisor host to another.
The system releases all resources normally used by the job from the hypervisor host, then migrates the job to the destination host without any detectable delay. During this time, the job remains in a RUN state.
RHEL KVM hypervisors do not support live migration with VM job checkpointing. Do not use -dc_chkpntvm with -dc_vmaction livemigvm.
-dc_vmaction requeuejob: Kill the VM job and resubmit it to the queue.
The system kills the VM job and submits a new VM job request to the queue.
The default value for -dc_vmaction is undefined (no action taken) if you modify a job that was previously not a Dynamic Cluster and specify -dc_tmpl without specifying a value for -dc_vmaction.
The action defines the behavior only when this job is the lower priority (preempted) job, not the higher priority (preempting) job.
When you define the preemption action on the command line, DC_VM_PREEMPTION_ACTION in lsb.applications is ignored.
When using livemigvm to specify a live migration preemption action, you can also specify a second preemption action to trigger if the live migration action fails. Use a space to separate the two actions and quotation marks to enclose the two actions:
-dc_vmaction "livemigvm[details] second_action"
For example,
bmod -dc_vmaction "livemigvm[wait_trigger_time=100:livemig_max_downtime=0:livemig_max_exectime=1000] requeuejob" \
myjobIf the live migration fails (because the trigger time or execute time is exceeded), the requeuejob action triggers.