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
cloud:a_walk_in_the_cloud [2016/12/06 11:48]
cloud:a_walk_in_the_cloud [2018/10/09 16:44]
Line 15: Line 15:
 To use a cloud batch system you login to the "​interactive nodes"​. To use a cloud batch system you login to the "​interactive nodes"​.
-For the NeCTAR tier 3 cloud the nodes are //cxin01//, //cxin02// and //cxsin//.+For the NeCTAR tier 3 cloud the nodes are //cxin01//, //cxin02//, //cxin03// and //cxin04//.
 You login this way: You login this way:
 <​code>​ <​code>​
 ssh -Y <​user_name>​ ssh -Y <​user_name>​
 ssh -Y <​user_name>​ ssh -Y <​user_name>​
 +ssh -Y <​user_name>​
 +ssh -Y <​user_name>​
 </​code>​ </​code>​
 The above nodes are at Melbourne.  ​ The above nodes are at Melbourne.  ​
Line 116: Line 118:
 ^  queue      ^  walltime ​                ^ ^  queue      ^  walltime ​                ^
 |  short      |  maximum 1 hour           ​|  ​ |  short      |  maximum 1 hour           ​|  ​
-|  long       ​|  ​default ​maximum 7 days |  ​+|  long       ​| ​ maximum 7 days |   
 +|  extralong ​ |  maximum 31 days |  ​
 If your batch jobs exceed either the walltime limit they will be terminated. If your batch jobs exceed either the walltime limit they will be terminated.
Line 170: Line 173:
 ========= Getting Email ========= ========= Getting Email =========
-It may be useful to you (especially when starting out) to get an email when your job finishes. +We have disabled ​email from the batch system as it leads to our mail server being blocked for spam
-You do this with these parameters:​ +
-<​code>​ +
-#PBS -m ae +
-#PBS -M <your email address>​ +
-</​code>​ +
- +
-The **ae** part of the first parameter says you want email on an **abort** or a normal **end** of your job. +
-When you have a little experience running jobs you probably want to use **#PBS -m a** which sends you +
-email only on job abort.+
 ========= Selecting a Queue ========= ========= Selecting a Queue =========
Line 193: Line 187:
 </​code>​ </​code>​
-========= Selecting a Zone ========= 
-The cloud has various zones containing VMs that you may use. 
-These zones are in different geographical locations around Australia. 
-At the beginning of the year 2014 the available zones were: 
-^ Zone ^ Location ^ ID ^ 
-| melbourne_qh2 | Melbourne | **MEL** | 
-| monash_01 | Melbourne | **MON** | 
-| sa | Adelaide | **SA** | 
-You can specify which zone you want your job to run in. 
-Which zone you choose depends on what sort of job you want to run. 
-If your job needs little data access then it can run anywhere. 
-However, if your job needs constant, heavy access to a lot of data, it 
-is better to run your job in a zone that is close to where your data is stored. 
-You specify which zone your job will run in by specifying the appropriate **ID** 
-from the table above in a PBS option line.  For instance, to run a job on  
-a Monash VM, you can do this in your batch file: 
-#PBS -l nodes=1:MON 
-The number immediately after the "​**=**"​ sign sets the number of required CPU cores your job needs. 
-You should always set this to **1**. ​ This wiki page doesn'​t address running multi-core jobs. 
-If you don't specify a zone, the batch system will choose a zone at random. 
 ========= Debugging ========= ========= Debugging =========
cloud/a_walk_in_the_cloud.txt · Last modified: 2018/10/09 16:44 by scrosby
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
Recent changes RSS feed Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki