submit_jobs_to_a_virtual_machine_beta

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
submit_jobs_to_a_virtual_machine_beta [2012/11/27 17:04]
jahrens
submit_jobs_to_a_virtual_machine_beta [2012/11/28 14:58] (current)
jahrens
Line 1: Line 1:
 +====Currently job submission to the queue atlastest is restricted and not open for users====
 +
 ===MOTIVATION=== ===MOTIVATION===
 Many ATLAS-Jobs use the experiment specific software ATHENA, which is currently running exclusively under the OS Scientific Linux 5.x. The native OS installed on all nodes of MOGON is Scientific Linux 6.2. Most nodes (95%) of MOGON are 4-socket 16 core AMD Bulldozer machines that require a kernel newer than the one shipped with SL5.x. A native SL5.x install on such a node would be technically possible but come along with huge penalties on the performance. Many ATLAS-Jobs use the experiment specific software ATHENA, which is currently running exclusively under the OS Scientific Linux 5.x. The native OS installed on all nodes of MOGON is Scientific Linux 6.2. Most nodes (95%) of MOGON are 4-socket 16 core AMD Bulldozer machines that require a kernel newer than the one shipped with SL5.x. A native SL5.x install on such a node would be technically possible but come along with huge penalties on the performance.
Line 12: Line 14:
  
 Currently the VMs have restricted outside connectivity via NAT, that is done by the Hypervisor node. You may reach all machines on campus, but only a few in the external internet. This access should not be used to download big files to the node! Currently the VMs have restricted outside connectivity via NAT, that is done by the Hypervisor node. You may reach all machines on campus, but only a few in the external internet. This access should not be used to download big files to the node!
 +
 +Details about the processes involved during job submission to and execution in VMs can be found in [[Jobsubmission to VMs in LSF - Technical details]]
 +
 +
 ===VM SPECIFIC INFORMATION IN JOB SUBMISSION=== ===VM SPECIFIC INFORMATION IN JOB SUBMISSION===
  
Line 23: Line 29:
 | ''-rd='' | Size of the RAM disk | 1GByte | Size of the RAM disk for the VM. ''-rd=1G = 1000M = 1000000k = 1000000000'' are all eqivalent - if not set, the default of 1GByte will be used | | ''-rd='' | Size of the RAM disk | 1GByte | Size of the RAM disk for the VM. ''-rd=1G = 1000M = 1000000k = 1000000000'' are all eqivalent - if not set, the default of 1GByte will be used |
 | ''-cpus='' | Number of virtual cpus | 1 CPU | Number of cpus for the VM. If not set. the default of 1 cpu will be used. PLEASE NOTE: Currently only single core VMs are allowed (''-cpus=1''), request for more cpus will be ignored | | ''-cpus='' | Number of virtual cpus | 1 CPU | Number of cpus for the VM. If not set. the default of 1 cpu will be used. PLEASE NOTE: Currently only single core VMs are allowed (''-cpus=1''), request for more cpus will be ignored |
-| ''-vmos='' | OS for the VM | vm-sl58 |  OS installed on the VM. Currently only SL5.8 is allowed ''-vmos=vm-sl58'' - if not set, the default OS vm-sl58 will be used |+| ''-vmos='' | OS for the VM | vm-sl58 | OS installed on the VM. Currently only SL5.8 is allowed ''-vmos=vm-sl58'' - if not set, the default OS vm-sl58 will be used |
 | ''-ak='' | User's Auth. Keys file | None | Absolute path to the location to the authorized_keys file of the user - if not set, no user login to the VM via ''vmssh'' will be possible | | ''-ak='' | User's Auth. Keys file | None | Absolute path to the location to the authorized_keys file of the user - if not set, no user login to the VM via ''vmssh'' will be possible |
-| ''-verb='' | Verbose output about VM | off | With this option set (-verb=on), the user get a detailed output of the process of VM creation appended to his ''stderr'' file of the job - if not set -verb=off is assumed |+| ''-verb='' | Verbose output about VM creation | off | With this option set (-verb=on), the user get a detailed output of the process of VM creation appended to his ''stderr'' file of the job - if not set -verb=off is assumed |
  
 ==Example== ==Example==
Line 46: Line 52:
  
 ==Complete example== ==Complete example==
-How job submission on LSF is done can be looked up in this section. However here is an example for a complete command for  +How job submission on LSF is done can be looked up in the section [[Submit and manage jobs on Mogon (Quickstart)]]. However here is an example for a complete command for  
-job submission to **atlstest**:+job submission to **atlastest**:
  
 <code> <code>
Line 62: Line 68:
 vmssh <JOBID> vmssh <JOBID>
 </code> </code>
 +Please keep in mind that the login is only possible after the job state is 'RUN' and after the time the VM needs to boot and start its sshd (about 30s).
  
 ==Copy new files to the RAM disk== ==Copy new files to the RAM disk==
  • submit_jobs_to_a_virtual_machine_beta.1354032241.txt.gz
  • Last modified: 2012/11/27 17:04
  • by jahrens