Getting Started: Difference between revisions

From Grid5000
Jump to navigation Jump to search
(28 intermediate revisions by 2 users not shown)
Line 10: Line 10:


== Connecting for the first time ==
== Connecting for the first time ==


The primary way to move around Grid'5000 is using SSH. A [[SSH|reference page for SSH]] is also maintained with advanced configuration options that frequent users will find useful.
The primary way to move around Grid'5000 is using SSH. A [[SSH|reference page for SSH]] is also maintained with advanced configuration options that frequent users will find useful.
Line 27: Line 25:
To connect you will have to type in your credentials twice (first for the HTTP proxy, then for the SSH connection).
To connect you will have to type in your credentials twice (first for the HTTP proxy, then for the SSH connection).


This solution is probably suitable to follow this tutorial, but is unlikely to be suitable for real Grid'5000 usage. So you should probably read the following sections about how to setup and use SSH at some point.
This solution is probably suitable to follow this tutorial, but is unlikely to be suitable for real Grid'5000 usage. So you should probably read the next sections about how to setup and use SSH at some point.


=== Connect to a Grid'5000 access machine ===
=== Connect to a Grid'5000 access machine ===
The <code class="host">access.grid5000.fr</code> address points to two actual machines: <code class="host">access-north</code> (currently hosted in Lille) and <code class="host">access-south</code> (currently hosted in Sophia-Antipolis). Those machines provide SSH access to Grid'5000 from Internet.
To enter the Grid'5000 network from Internet, one must use an access machine: <code class="host">access.grid5000.fr</code> (Note that <code class="host">access.grid5000.fr</code> is a round robin alias to either: <code class="host">access-north</code> which is currently hosted in Lille, or <code class="host">access-south</code> currently hosted in Sophia-Antipolis).
 
For all connections, you must use the <code class="replace">login</code> that was provided to you when you created your Grid'5000 account.


{{Term|location=outside|cmd=<code class="command">ssh</code> <code class="replace">login</code><code class="command">@</code><code class="host">access.grid5000.fr</code>}}
{{Term|location=outside|cmd=<code class="command">ssh</code> <code class="replace">login</code><code class="command">@</code><code class="host">access.grid5000.fr</code>}}
Line 36: Line 36:


{{Note|text=You can modify your SSH keys in the [https://api.grid5000.fr/ui/account account management interface]}}
{{Note|text=You can modify your SSH keys in the [https://api.grid5000.fr/ui/account account management interface]}}
If you prefer (for better bandwidth and latency), you might also be able to connect directly via your local Grid'5000 site. However, per-site access restrictions are applied, so using <code class="host">access.grid5000.fr</code> is usually a simpler choice. See [[External_access]] for details about local access machines.
A VPN service is also available to connect directly to Grid'5000 hosts. See [[VPN|the VPN page]] for more information. If you only require HTTP/HTTPS access to a node, a reverse HTTP proxy is also available, see [[FAQ#How_can_I_connect_to_an_HTTP_or_HTTPS_service_running_on_a_node.3F|this FAQ]].


=== Connecting to a Grid'5000 site ===
=== Connecting to a Grid'5000 site ===
Grid'5000 is structured in '''<code class="host">sites</code>''' (<code class="host">Grenoble</code>, <code class="host">Rennes</code>, <code class="host">Nancy</code>, ...). Each site hosts one or more clusters (homogeneous sets of machines, usually bought at the same time).
Grid'5000 is structured in '''<code class="host">sites</code>''' (<code class="host">Grenoble</code>, <code class="host">Rennes</code>, <code class="host">Nancy</code>, ...). Each site hosts one or more clusters (homogeneous sets of machines, usually bought at the same time).


To connect to a particular site, do the following (blue and red arrow labelled SSH in the figure above).
To connect to a particular site, do the following (blue and red arrow labeled SSH in the figure above).


{{Term|location=access|cmd=<code class="command">ssh</code> <code class="replace">site</code>}}
{{Term|location=access|cmd=<code class="command">ssh</code> <code class="replace">site</code>}}


==== Home directories ====
; Home directories
You have a '''different home directory on each Grid'5000 site''', so you will usually use [[Rsync]] or <code class="command">scp</code> to move data around.
You have a '''different home directory on each Grid'5000 site''', so you will usually use [[Rsync]] or <code class="command">scp</code> to move data around.
On <code class="host">access</code> machines, you have direct access to each of those home directory, through NFS mounts (but using that feature to transfer very large volumes of data is inefficient). Typically, to copy a file to your home directory on the Nancy site, you can use:
On <code class="host">access</code> machines, you have direct access to each of those home directories, through NFS mounts (but using that feature to transfer very large volumes of data is inefficient). Typically, to copy a file to your home directory on the Nancy site, you can use:
{{Term|location=outside|cmd=<code class="command">scp</code> <code class="replace">myfile.c</code> <code class="replace">login@access.grid5000.fr:nancy/targetdirectory/mytargetfile.c</code>}}
{{Term|location=outside|cmd=<code class="command">scp</code> <code class="replace">myfile.c</code> <code class="replace">login</code>@<code class=host>access.grid5000.fr</code>:<code class=file>nancy/targetdirectory/mytargetfile.c</code>}}


'''Grid'5000 does NOT have a BACKUP service for Grid'5000's users home directories''': it is '''your responsibility''' to save important data outside Grid'5000 (or at least to copy data to several Grid'5000 sites in order to increase redundancy).
'''Grid'5000 does NOT have a BACKUP service for users' home directories''': it is '''your responsibility''' to save important data in someplace outside Grid'5000 (or at least to copy data to several Grid'5000 sites in order to increase redundancy).


Quotas are applied on home directories -- by default, you get 25 GB per Grid'5000 site. If your usage of Grid'5000 requires more disk space, it is possible to request quota extensions in the account management interface, or to use other storage solutions (see [[Storage]]).
Quotas are applied on home directories -- by default, you get 25 GB per Grid'5000 site. If your usage of Grid'5000 requires more disk space, it is possible to request quota extensions in the account management interface, or to use other storage solutions (see [[Storage]]).


=== Recommended tips and tricks for efficient use of Grid'5000===
=== Recommended tips and tricks for an efficient use of Grid'5000===
There are also several '''recommended tips and tricks for SSH and related tools''', explained in the [[SSH]] page:
; Better exploit SSH and related tools
* Configure [[SSH#Using_SSH_ProxyCommand_feature_to_ease_the_access_to_hosts_inside_Grid.275000|SSH aliases using the ProxyCommand option]]. Using this, you can avoid the two-steps connection (access machine, then frontend) and connect directly to frontends. Edit your ~/.ssh/config
There are also several '''recommended tips and tricks for SSH and related tools''' (more details in the [[SSH]] page).
* Configure [[SSH#Using_SSH_ProxyCommand_feature_to_ease_the_access_to_hosts_inside_Grid.275000|SSH aliases using the ProxyCommand option]]. Using this, you can avoid the two-hops connection (access machine, then frontend) but establish connections directly to frontends. This requires using OpenSSH, which is the SSH software available on all GNU/Linux systems, MacOS, and also recent versions of Microsoft Windows.
{{Note|text=Please really mind setting up the following ssh configuration on the workstation or laptop from where you access to Grid'5000 (''outside'') if you use Grid'5000 on a regular basis. It significantly eases many tasks.}}


  Host g5k
{{Term|location=outside|cmd=editor <code class=file>~/.ssh/config</code>}}
   User USERNAME
  Host <code class=host>g5k</code>
   User <code class=replace>login</code>
   Hostname access.grid5000.fr
   Hostname access.grid5000.fr
   ForwardAgent no
   ForwardAgent no
  Host *.g5k
   User USERNAME
  Host <code class=host>*.g5k</code>
   User <code class=replace>login</code>
   ProxyCommand ssh g5k -W "$(basename %h .g5k):%p"
   ProxyCommand ssh g5k -W "$(basename %h .g5k):%p"
   ForwardAgent no
   ForwardAgent no
'''Reminder:''' <code class=replace>login</code> is your Grid'5000 username
'''Warning:''' the <code class=command>ProxyCommand</code> line works if your login shell is <code class=command>bash</code>. If not you may have to adapt it.


* Using <code class="command">rsync</code> instead of <code class="command">scp</code> (better performance with multiple files)
Once done, you can establish connections to any machine (first of all: frontends) inside Grid'5000 directly, by suffixing <code class=host>.g5k</code> to its hostname (instead of first having to connect to an access machine). E.g.:
{{Term|location=outside|cmd=<code class=command>ssh</code> <code class=replace>rennes</code>.<code class=host>g5k</code>}}
{{Term|location=outside|cmd=<code class=command>scp</code> <code class=file>a_file</code> <code class=replace>lille</code>.<code class=host>g5k</code>:}}
* Use <code class="command">rsync</code> instead of <code class="command">scp</code> for better performance with multiple files.
* Access your data from your laptop using [[SSH#Mounting_remote_filesystem_.28sshfs.29|SSHFS]]
* Access your data from your laptop using [[SSH#Mounting_remote_filesystem_.28sshfs.29|SSHFS]]
* Edit files over SSH with your favorite text editor, with e.g. <code class="command">vim scp://nancy.g5k/my_file.c</code>
* Edit files over SSH with your favorite text editor, with e.g.:
{{Term|location=outside|cmd=<code class="command">vim</code> <code class=file>scp://nancy.g5k/my_file.c</code>}}
There are more in [http://www.loria.fr/~lnussbau/files/g5kss10-grid5000-efficiently.pdf this talk from Grid'5000 School 2010], and [https://github.com/lnussbaum/slides-lectures/blob/master/ssh/ssh.pdf this talk more focused on SSH].
There are more in [http://www.loria.fr/~lnussbau/files/g5kss10-grid5000-efficiently.pdf this talk from Grid'5000 School 2010], and [https://github.com/lnussbaum/slides-lectures/blob/master/ssh/ssh.pdf this talk more focused on SSH].


Additionally, the '''[[media:G5k_cheat_sheet.pdf|Grid'5000 cheat sheet]]''' provides a nice summary of everything described in the tutorials.
* For a '''better bandwidth or latency''', you may also be able to connect directly via the '''local access machine of one of the Grid'5000 sites'''.
Local accesses use <code class="host">access.</code><code class=replace>site</code><code class=host>.grid5000.fr</code> instead of <code class="host">access.grid5000.fr</code>.
However, mind that '''per-site access restrictions are applied''': see [[External access]] for details about local access machines.
 
; VPN
A VPN service is also available, allowing to connect directly to any Grid'5000 machines (bypassing the access machines). See [[VPN|the VPN page]] for more information.
 
; HTTP reverse proxies
If you only require HTTP/HTTPS access to a node, a reverse HTTP proxy is also available, see the [[HTTP/HTTPs_access]] page.
 
; Cheatsheet
The '''[[media:G5k_cheat_sheet.pdf|Grid'5000 cheat sheet]]''' provides a nice summary of everything described in the tutorials.


== Discovering, visualizing and reserving Grid'5000 resources ==
== Discovering, visualizing and reserving Grid'5000 resources ==
Line 96: Line 115:
{{Note|text=OAR is the resources and jobs management system (a.k.a batch manager) used in Grid'5000, just like in traditional HPC centers. '''However, settings and rules of OAR that are configured in Grid'5000 slightly differ from traditional batch manager setups in HPC centers, in order to match the requirements for an experimentation testbed'''. Please remember to read again '''Grid'5000 [[Grid5000:UsagePolicy#Resources_reservation|Usage Policy]]''' to understand the expected usage.}}
{{Note|text=OAR is the resources and jobs management system (a.k.a batch manager) used in Grid'5000, just like in traditional HPC centers. '''However, settings and rules of OAR that are configured in Grid'5000 slightly differ from traditional batch manager setups in HPC centers, in order to match the requirements for an experimentation testbed'''. Please remember to read again '''Grid'5000 [[Grid5000:UsagePolicy#Resources_reservation|Usage Policy]]''' to understand the expected usage.}}


In Grid'5000 the smallest unit of resource managed by OAR is the core (cpu core), but by default a OAR job reserves a host (physical computer including all its cpu/cores). Hence, what OAR calls ''nodes'' are hosts (physical machines).
In Grid'5000 the smallest unit of resource managed by OAR is the core (cpu core), but by default a OAR job reserves a host (physical computer including all its cpus and cores, and possibly gpus). Hence, what OAR calls ''nodes'' are hosts (physical machines). In the <code class="command">oarsub</code> resource request (<code class="command">-l</code> arguments), ''nodes'' is an alias for ''host'', so both are equivalent. But prefer using ''host'' for consistency with other argumnents and other tools that expose ''host'' not ''nodes''.


{{Note|text=Most of this tutorial uses the site of Nancy (with the frontend: <code class="host">fnancy</code>), but other sites can be used alternatively.}}
{{Note|text=Most of this tutorial uses the site of Nancy (with the frontend: <code class="host">fnancy</code>), but other sites can be used alternatively.}}


To reserve one host (one node), in interactive mode, do:
; Interactive usage
 
To reserve a single host (one node) for one hour, in interactive mode, do:
{{Term|location=fnancy|cmd=<code class="command">oarsub</code> <code>-I</code>}}
{{Term|location=fnancy|cmd=<code class="command">oarsub</code> <code>-I</code>}}


To reserve three hosts (three nodes), in interactive mode, do:
To reserve only one CPU core in interactive mode, run:
{{Term|location=fnancy|cmd=<code class="command">oarsub -l host=3</code> <code>-I</code>}}
{{Term|location=fnancy|cmd=<code class="command">oarsub -l core=1</code> <code>-I</code>}}
or equivalently:
{{Note|text= When reserving only a share of the node's cores, you will have a share of the memory with the same ratio as the cores. If you take the whole node, you will have all the memory of the node. If you take half the cores, you will have half the memory, and so on... You cannot reserve a memory size explicitly.}}
{{Term|location=fnancy|cmd=<code class="command">oarsub -l nodes=3</code> <code>-I</code>}}


To reserve only one core in interactive mode, run:
As soon as the resource becomes available, you will be directly connected to the reserved resource with an interactive shell, as indicated by the shell prompt, and you can run commands on the node:
{{Term|location=fnancy|cmd=<code class="command">oarsub -l core=1</code> <code>-I</code>}}
 
{{Note|text= When reserving only a share of the node's cores, you will have a share of the memory with the same ratio as the cores. If you take the whole node, you will have all the memory of the node. If you take half the cores, you will have half the memory, aso... You cannot reserve a memory size explicitly.}}
{{Term|location=grisou-1|cmd=<code class="command">lscpu</code>}}


As soon as a resource becomes available, you will be directly connected to the reserved resource with an interactive shell, as indicated by the shell prompt.
; Non-interactive usage (scripts)


You can also simply launch your experiment along with your reservation:
You can also simply launch your experiment along with your reservation:
{{Term|location=fnancy|cmd=<code class="command">oarsub -l core=1</code> <code>"my_mono_threaded_script.py --in $HOME/data --out $HOME/results"</code>}}
{{Term|location=fnancy|cmd=<code class="command">oarsub -l core=1</code> <code>"my_mono_threaded_script.py --in $HOME/data --out $HOME/results"</code>}}
Your program will be executed as soon as the requested resources are available (you will have to check for its termination using the oarstat command).
Your program will be executed as soon as the requested resources are available. As this type of job is not interactive, you will have to check for its termination using the <code class="command">oarstat</code> command.


To reserve only one GPU (with the associated cores) in interactive mode, run:
; Other types of resources
 
To reserve only one GPU (with the associated CPU cores and share of memory) in interactive mode, run:
{{Term|location=flille|cmd=<code class="command">oarsub -l gpu=1</code> <code>-I</code>}}
 
{{Note|text=Even if the node has several GPUs, this reservation will only be able to access a single one. It's a good practice if you only need one GPU: other users will be able to run jobs on the same node to access the other GPUs. Of course, if you need all GPUs of a node, you have the option to reserve the entire node which includes all its GPUs.}}
 
Or in Nancy where GPUs are only available in the production queue:
{{Term|location=fnancy|cmd=<code class="command">oarsub -l gpu=1</code> <code>-I</code> <code>-q production</code>}}
{{Term|location=fnancy|cmd=<code class="command">oarsub -l gpu=1</code> <code>-I</code> <code>-q production</code>}}
(nodes with GPU are exclusively in the production queue in Nancy, on other sites, just don't use the <code>-q production</code> option to obtain the same result)
As soon as a resource becomes available, you will be directly connected to the reserved resource with an interactive shell, as indicated by the shell prompt.


; Tips and tricks


To terminate your reservation and return to the frontend, simply exit this shell by typing <code class="command">exit</code> or <code class="command">CTRL+d</code>:
To terminate your reservation and return to the frontend, simply exit this shell by typing <code class="command">exit</code> or <code class="command">CTRL+d</code>:
Line 140: Line 165:
<code class="command">env <nowiki>|</nowiki> grep OAR</code><code> # discover environment variables set by OAR</code>}}  
<code class="command">env <nowiki>|</nowiki> grep OAR</code><code> # discover environment variables set by OAR</code>}}  


Of course, you will probably want to use more than one node on a given site, and you might want them for a different duration than one hour. The -l switch allows you to pass a comma-separated list of parameters specifying the needed resources for the job.
; Choosing the job duration
{{Term|location=fnancy|cmd=<code class="command">oarsub</code> <code>-I -l nodes=2,walltime=0:30</code>}}
 
The walltime is the expected duration you envision to complete your work. Its format is <code>[hour:min:sec|hour:min|hour]</code> (walltime=5 => 5 hours, walltime=1:22 => 1 hour 22 minutes, walltime=0:03:30 => 3 minutes, 30 seconds).
Of course, you might want to run a job for a different duration than one hour. The <code>-l</code> option allows you to pass a comma-separated list of parameters specifying the needed resources for the job, and <code>walltime</code> is a special resource defining the duration of your job:
 
{{Term|location=fnancy|cmd=<code class="command">oarsub -l core=2,walltime=0:30</code> <code>-I</code>}}
The walltime is the expected duration you envision to complete your work. Its format is <code>[hour:min:sec|hour:min|hour]</code>. For instance:
 
* <code>walltime=5</code> => 5 hours
* <code>walltime=1:22</code> => 1 hour and 22 minutes
* <code>walltime=0:03:30</code> => 3 minutes and 30 seconds
 
; Working with more than one node
 
You will probably want to use more than one node on a given site.
 
To reserve two hosts (two nodes), in interactive mode, do:
{{Term|location=fnancy|cmd=<code class="command">oarsub -l host=2</code> <code>-I</code>}}
or equivalently (''nodes'' is an alias for ''host''):
{{Term|location=fnancy|cmd=<code class="command">oarsub -l nodes=2</code> <code>-I</code>}}
 
You will obtain a shell '''on the first node of the reservation'''. It is up to you to connect to the other nodes and distribute work among them.


By default, you can only connect to nodes in your reservation, and only using the <code class="command">oarsh</code> connector to go from one node to the other. The connector supports the same options as the classical <code class="command">ssh</code> command, so it can be used as a replacement for software expecting ssh.  
By default, you can only connect to nodes that are part of your reservation, and only using the <code class="command">oarsh</code> connector to go from one node to the other. The connector supports the same options as the classical <code class="command">ssh</code> command, so it can be used as a replacement for software expecting ssh.  
{{Term|location=gros-49|cmd=<br>
{{Term|location=gros-49|cmd=<br>
<code class="command">uniq</code> <code class="env">$OAR_NODEFILE</code> <code># list of resources of your reservation</code><br>
<code class="command">uniq</code> <code class="env">$OAR_NODEFILE</code> <code># list of resources of your reservation</code><br>
<code class="command">oarsh</code> <code class="replace">gros-1</code><code>    # use a node not in the file (will fail)</code><br>
<code class="command">oarsh</code> <code class="replace">gros-1</code><code>    # try to connect a node not in the file (will fail)</code><br>
<code class="command">oarsh</code> <code class="replace">gros-54</code><code> # use the other node of your reservation</code><br>
<code class="command">oarsh</code> <code class="replace">gros-54</code><code> # connect to the other node of your reservation (should work)</code><br>
<code class="command">ssh</code> <code class="replace">gros-54</code><code> # will fail</code>}}
<code class="command">ssh</code> <code class="replace">gros-54</code><code> # this will fail</code>}}
 
{{Note|text=To take advantage of several nodes and distribute work between them, a good option is [[GNU_Parallel]].}}


<code class="command">oarsh</code> is a wrapper around <code class="command">ssh</code> that enables the tracking of user jobs inside compute nodes (for example, to enforce the correct sharing of resources when two different jobs share a compute node). If your application does not support choosing a different connector, it is possible to avoid using <code class="command">oarsh</code> for <code class="command">ssh</code> with the <code>allow_classic_ssh</code> job type, as in  
<code class="command">oarsh</code> is a wrapper around <code class="command">ssh</code> that enables the tracking of user jobs inside compute nodes (for example, to enforce the correct sharing of resources when two different jobs share a compute node). If your application does not support choosing a different connector, it is possible to avoid using <code class="command">oarsh</code> for <code class="command">ssh</code> with the <code>allow_classic_ssh</code> job type, as in  
{{Term|location=fnancy|cmd=<code class="command">oarsub</code> <code>-I -l nodes=2,walltime=0:30:0 -t </code><code class="env">allow_classic_ssh</code>}}
{{Term|location=fnancy|cmd=<code class="command">oarsub -l host=2,walltime=0:30:0</code> <code>-I</code> <code>-t</code> <code class="env">allow_classic_ssh</code>}}
 
=== Selecting specific resources ===
 
So far, all examples were letting OAR decide which resource to allocate to a job.
It is possible to obtain finer-grained control on the allocated resources by using filters.
 
; Selecting nodes from a specific cluster or cluster type
 
* Reserve nodes from a specific cluster
{{Term|location=fgrenoble|cmd=<code class="command">oarsub</code> <code class="replace">-p "cluster='yeti'"</code> <code class="command">-l host=2,walltime=2</code> <code>-I</code>}}
* Reserve nodes in the [[Grid5000:UsagePolicy#Rules_for_the_production_queue|'''production''' queue]]
{{Term|location=fnancy|cmd=<code class="command">oarsub</code> <code class="replace">-q production</code> <code class="replace">-p "cluster='grappe'"</code> <code class="command">-l host=2,walltime=2</code> <code>-I</code>}}
* Reserve nodes from an '''exotic''' cluster type
{{Term|location=flyon|cmd=<code class="command">oarsub</code> <code class="replace">-t exotic</code> <code class="replace">-p "cluster='pyxis'"</code> <code class="command">-l host=2,walltime=2</code> <code>-I</code>}}
 
Clusters with the '''exotic''' type either have a non-x86 architecture, or are specific enough to warrant this type. Resources with an exotic type are never selected by default by OAR. Using <code class="command">-t exotic</code> is required to obtain such resources.
 
The type of a cluster can be identified on the [[Hardware]] pages, see for instance [[Lyon:Hardware]].
 
{{Warning|text=When using the <code class="command">-t exotic</code> option, you can still obtain non-exotic resources! You should filter on the cluster name or other properties if you want exclusively exotic resources.}}
 
; Using OAR properties
 
The OAR nodes database contains a set of properties for each node, and the <code class="command">-p</code> option actually filters based on these properties:
* Nodes with Infiniband FDR interfaces:
{{Term|location=fnancy|cmd=<code class="command">oarsub</code> <code class="replace">-p "ib='FDR'"</code> <code class="command">-l host=5,walltime=2<code> <code>-I</code>}}
* Nodes with power sensors and GPUs:
{{Term|location=flyon|cmd=<code class="command">oarsub</code> <code class="replace">-p "wattmeter='YES' and gpu_count > 0"</code> <code class="command">-l host=2,walltime=2</code> <code>-I</code>}}
* Nodes with 2 GPUs:
{{Term|location=flille|cmd=<code class="command">oarsub</code> <code class="replace">-p "gpu_count = 2"</code> <code class="command">-l host=3,walltime=2</code> <code>-I</code>}}
* Nodes with a specific CPU model:
{{Term|location=flille|cmd=<code class="command">oarsub</code> <code class="replace">-p "cputype = 'Intel Xeon E5-2630 v4'"</code> <code class="command">-l host=3,walltime=2</code> <code>-I</code>}}
* Since <code class="command">-p</code> accepts SQL, you can write advanced queries:
{{Term|location=fnancy|cmd=<code class="command">oarsub</code> <code class="replace">-p "wattmeter='YES' and host not in ('graffiti-41.nancy.grid5000.fr', 'graffiti-42.nancy.grid5000.fr')"</code> <code class="command">-l host=5,walltime=2</code> <code>-I</code>}}
The OAR properties available on each site are listed on the Monika pages linked from [[Status]] ([https://intranet.grid5000.fr/oar/Nancy/monika.cgi example page for Nancy]). The full list of OAR properties is available on [[OAR_Properties|this page]].


=== Advanced job management topics ===
=== Advanced job management topics ===
Line 160: Line 240:


You can also reserve resources at a specific time in the future, typically to perform large reservations over nights and week-ends, with the <code class="command">-r</code> parameter:
You can also reserve resources at a specific time in the future, typically to perform large reservations over nights and week-ends, with the <code class="command">-r</code> parameter:
{{Term|location=fnancy|cmd=<code class="command">oarsub</code><code> -l nodes=3,walltime=3 </code><code class="command">'''-r'''</code><code> '2020-12-23 16:30:00'</code>}}
{{Term|location=fnancy|cmd=<code class="command">oarsub</code><code> -l host=3,walltime=3 </code><code class="command">'''-r'''</code><code> '2020-12-23 16:30:00'</code>}}


{{Note|text=Remember that '''all your resource reservations must comply with the [[Grid5000:UsagePolicy#Resources_reservation|Usage Policy]]'''. You can verify your reservations' compliance with the Policy with <code>usagepolicycheck -t</code>.}}
{{Note|text=Remember that '''all your resource reservations must comply with the [[Grid5000:UsagePolicy#Resources_reservation|Usage Policy]]'''. You can verify your reservations' compliance with the Policy with <code>usagepolicycheck -t</code>.}}
Line 168: Line 248:
To list jobs currently submitted, use the <code class="command">oarstat</code> command (use -u option to see only your jobs). A job can be deleted with:
To list jobs currently submitted, use the <code class="command">oarstat</code> command (use -u option to see only your jobs). A job can be deleted with:
{{Term|location=fnancy|cmd=<code class="command">oardel</code> <code class="replace">12345</code>}}
{{Term|location=fnancy|cmd=<code class="command">oardel</code> <code class="replace">12345</code>}}
; Selection of resources using OAR properties
The OAR nodes database contains a set of properties for each node, that can be used to request specific resources:
* Nodes from a given cluster
{{Term|location=fluxembourg|cmd=<code class="command">oarsub</code> <code class="replace">-p "cluster='granduc'"</code><code> -l nodes=5,walltime=2 -I</code>}}
* Nodes with Infiniband FDR interfaces
{{Term|location=fnancy|cmd=<code class="command">oarsub</code> <code class="replace">-p "ib='FDR'"</code><code> -l nodes=5,walltime=2 -I</code>}}
* Nodes with power sensors and GPUs
{{Term|location=flyon|cmd=<code class="command">oarsub</code> <code class="replace">-p "wattmeter='YES' and gpu_count > 0"</code><code> -l nodes=2,walltime=2 -I</code>}}
* Since <code class="command">-p</code> accepts SQL, you could write
{{Term|location=fnancy|cmd=<code class="command">oarsub</code> <code class="replace">-p "wattmeter='YES' and host not in ('graffiti-41.nancy.grid5000.fr', 'graffiti-42.nancy.grid5000.fr')"</code><code> -l nodes=5,walltime=2 -I</code>}}
The OAR properties available on each site are listed on the Monika pages linked from [[Status]] ([https://intranet.grid5000.fr/oar/Nancy/monika.cgi example page for Nancy]). The full list of OAR properties is available on [[OAR_Properties|this page]].


; Extending the duration of a reservation
; Extending the duration of a reservation
Line 199: Line 266:


Reserve one node (the <code class="replace">deploy</code> job type is required to allow deployment with Kadeploy):
Reserve one node (the <code class="replace">deploy</code> job type is required to allow deployment with Kadeploy):
{{Term|location=fnancy|cmd=<code class="command">oarsub</code><code> -I -l nodes=1,walltime=1:45 -t </code><code class="replace">deploy</code>}}
{{Term|location=fnancy|cmd=<code class="command">oarsub</code><code> -I -l host=1,walltime=1:45 -t </code><code class="replace">deploy</code>}}


Start a deployment of the <code class="env">debian10-x64-base</code> image on that node (this takes 5 to 10 minutes):
Start a deployment of the <code class="env">debian10-x64-base</code> image on that node (this takes 5 to 10 minutes):

Revision as of 08:49, 22 January 2021

Note.png Note

This page is actively maintained by the Grid'5000 team. If you encounter problems, please report them (see the Support page). Additionally, as it is a wiki page, you are free to make minor corrections yourself if needed. If you would like to suggest a more fundamental change, please contact the Grid'5000 team.

This tutorial will guide you through your first steps on Grid'5000. Before proceeding, make sure you have a Grid'5000 account (if not, follow this procedure), and an SSH client.

Getting support

The Support page describes how to get help during your Grid'5000 usage.

There's also an FAQ page and a cheat sheet with the most common commands.

Connecting for the first time

The primary way to move around Grid'5000 is using SSH. A reference page for SSH is also maintained with advanced configuration options that frequent users will find useful.

As described in the figure below, when using Grid'5000, you will typically:

  1. connect, using SSH, to an access machine
  2. connect from this access machine to a site frontend
  3. on this site frontend, reserve resources (nodes), and connect to those nodes
Grid5000 Access

SSH connection through a web interface

If you want an out-of-the-box solution which does not require you to setup SSH, you can connect through a web interface. The interface is available at https://intranet.grid5000.fr/shell/SITE/. For example, to access nancy's site, use: https://intranet.grid5000.fr/shell/nancy/ To connect you will have to type in your credentials twice (first for the HTTP proxy, then for the SSH connection).

This solution is probably suitable to follow this tutorial, but is unlikely to be suitable for real Grid'5000 usage. So you should probably read the next sections about how to setup and use SSH at some point.

Connect to a Grid'5000 access machine

To enter the Grid'5000 network from Internet, one must use an access machine: access.grid5000.fr (Note that access.grid5000.fr is a round robin alias to either: access-north which is currently hosted in Lille, or access-south currently hosted in Sophia-Antipolis).

For all connections, you must use the login that was provided to you when you created your Grid'5000 account.

Terminal.png outside:
ssh login@access.grid5000.fr

You will get authenticated using the SSH public key you provided in the account creation form. Password authentication is disabled.

Note.png Note

You can modify your SSH keys in the account management interface

Connecting to a Grid'5000 site

Grid'5000 is structured in sites (Grenoble, Rennes, Nancy, ...). Each site hosts one or more clusters (homogeneous sets of machines, usually bought at the same time).

To connect to a particular site, do the following (blue and red arrow labeled SSH in the figure above).

Terminal.png access:
ssh site
Home directories

You have a different home directory on each Grid'5000 site, so you will usually use Rsync or scp to move data around. On access machines, you have direct access to each of those home directories, through NFS mounts (but using that feature to transfer very large volumes of data is inefficient). Typically, to copy a file to your home directory on the Nancy site, you can use:

Terminal.png outside:
scp myfile.c login@access.grid5000.fr:nancy/targetdirectory/mytargetfile.c

Grid'5000 does NOT have a BACKUP service for users' home directories: it is your responsibility to save important data in someplace outside Grid'5000 (or at least to copy data to several Grid'5000 sites in order to increase redundancy).

Quotas are applied on home directories -- by default, you get 25 GB per Grid'5000 site. If your usage of Grid'5000 requires more disk space, it is possible to request quota extensions in the account management interface, or to use other storage solutions (see Storage).

Recommended tips and tricks for an efficient use of Grid'5000

Better exploit SSH and related tools

There are also several recommended tips and tricks for SSH and related tools (more details in the SSH page).

  • Configure SSH aliases using the ProxyCommand option. Using this, you can avoid the two-hops connection (access machine, then frontend) but establish connections directly to frontends. This requires using OpenSSH, which is the SSH software available on all GNU/Linux systems, MacOS, and also recent versions of Microsoft Windows.
Note.png Note

Please really mind setting up the following ssh configuration on the workstation or laptop from where you access to Grid'5000 (outside) if you use Grid'5000 on a regular basis. It significantly eases many tasks.

Terminal.png outside:
editor ~/.ssh/config
Host g5k
  User login
  Hostname access.grid5000.fr
  ForwardAgent no

Host *.g5k
  User login
  ProxyCommand ssh g5k -W "$(basename %h .g5k):%p"
  ForwardAgent no

Reminder: login is your Grid'5000 username

Warning: the ProxyCommand line works if your login shell is bash. If not you may have to adapt it.

Once done, you can establish connections to any machine (first of all: frontends) inside Grid'5000 directly, by suffixing .g5k to its hostname (instead of first having to connect to an access machine). E.g.:

Terminal.png outside:
ssh rennes.g5k
Terminal.png outside:
scp a_file lille.g5k:
  • Use rsync instead of scp for better performance with multiple files.
  • Access your data from your laptop using SSHFS
  • Edit files over SSH with your favorite text editor, with e.g.:
Terminal.png outside:
vim scp://nancy.g5k/my_file.c

There are more in this talk from Grid'5000 School 2010, and this talk more focused on SSH.

  • For a better bandwidth or latency, you may also be able to connect directly via the local access machine of one of the Grid'5000 sites.

Local accesses use access.site.grid5000.fr instead of access.grid5000.fr. However, mind that per-site access restrictions are applied: see External access for details about local access machines.

VPN

A VPN service is also available, allowing to connect directly to any Grid'5000 machines (bypassing the access machines). See the VPN page for more information.

HTTP reverse proxies

If you only require HTTP/HTTPS access to a node, a reverse HTTP proxy is also available, see the HTTP/HTTPs_access page.

Cheatsheet

The Grid'5000 cheat sheet provides a nice summary of everything described in the tutorials.

Discovering, visualizing and reserving Grid'5000 resources

At this point, you should be connected to a site frontend, as indicated by your shell prompt (login@fsite:~$). This machine will be used to reserve and manipulate resources on this site, using the OAR software suite.

Discovering and visualizing resources

There are several ways to learn about the site's resources and their status:

  • The site's MOTD (message of the day) lists all clusters and their features. Additionally, it gives the list of current or future downtimes due to maintenance, which is also available from https://www.grid5000.fr/status/.
  • Site pages on the wiki (e.g. Nancy:Home) contain a detailed description of the site's hardware and network:
  • The Status page links to the resource status on each site, with two different visualizations available:
Example of Drawgantt in Nancy site
  • Hardware pages contain a detailed description of the site's hardware

Reserving resources with OAR: the basics

Note.png Note

OAR is the resources and jobs management system (a.k.a batch manager) used in Grid'5000, just like in traditional HPC centers. However, settings and rules of OAR that are configured in Grid'5000 slightly differ from traditional batch manager setups in HPC centers, in order to match the requirements for an experimentation testbed. Please remember to read again Grid'5000 Usage Policy to understand the expected usage.

In Grid'5000 the smallest unit of resource managed by OAR is the core (cpu core), but by default a OAR job reserves a host (physical computer including all its cpus and cores, and possibly gpus). Hence, what OAR calls nodes are hosts (physical machines). In the oarsub resource request (-l arguments), nodes is an alias for host, so both are equivalent. But prefer using host for consistency with other argumnents and other tools that expose host not nodes.

Note.png Note

Most of this tutorial uses the site of Nancy (with the frontend: fnancy), but other sites can be used alternatively.

Interactive usage

To reserve a single host (one node) for one hour, in interactive mode, do:

Terminal.png fnancy:
oarsub -I

To reserve only one CPU core in interactive mode, run:

Terminal.png fnancy:
oarsub -l core=1 -I
Note.png Note

When reserving only a share of the node's cores, you will have a share of the memory with the same ratio as the cores. If you take the whole node, you will have all the memory of the node. If you take half the cores, you will have half the memory, and so on... You cannot reserve a memory size explicitly.

As soon as the resource becomes available, you will be directly connected to the reserved resource with an interactive shell, as indicated by the shell prompt, and you can run commands on the node:

Terminal.png grisou-1:
lscpu
Non-interactive usage (scripts)

You can also simply launch your experiment along with your reservation:

Terminal.png fnancy:
oarsub -l core=1 "my_mono_threaded_script.py --in $HOME/data --out $HOME/results"

Your program will be executed as soon as the requested resources are available. As this type of job is not interactive, you will have to check for its termination using the oarstat command.

Other types of resources

To reserve only one GPU (with the associated CPU cores and share of memory) in interactive mode, run:

Terminal.png flille:
oarsub -l gpu=1 -I
Note.png Note

Even if the node has several GPUs, this reservation will only be able to access a single one. It's a good practice if you only need one GPU: other users will be able to run jobs on the same node to access the other GPUs. Of course, if you need all GPUs of a node, you have the option to reserve the entire node which includes all its GPUs.

Or in Nancy where GPUs are only available in the production queue:

Terminal.png fnancy:
oarsub -l gpu=1 -I -q production
Tips and tricks

To terminate your reservation and return to the frontend, simply exit this shell by typing exit or CTRL+d:

Terminal.png graffiti-1:
exit

To avoid unanticipated termination of your jobs in case of errors (terminal closed by mistake, network disconnection), you can either use tools such as tmux or screen, or reserve and connect in 2 steps using the job id associated to your reservation. First, reserve a node, and ask it to sleep for a long time:

Terminal.png fnancy:
oarsub "sleep 10d"

(10d stands for 10 days -- the command will be killed when the job expires anyway)

Then:

Terminal.png fnancy:
oarsub -C job_id
Terminal.png grisou-42:
hostname && ps -ef | grep sleep

java -version
mpirun --version
module available # List scientific-related software available using module
whoami

env | grep OAR # discover environment variables set by OAR
Choosing the job duration

Of course, you might want to run a job for a different duration than one hour. The -l option allows you to pass a comma-separated list of parameters specifying the needed resources for the job, and walltime is a special resource defining the duration of your job:

Terminal.png fnancy:
oarsub -l core=2,walltime=0:30 -I

The walltime is the expected duration you envision to complete your work. Its format is [hour:min:sec|hour:min|hour]. For instance:

  • walltime=5 => 5 hours
  • walltime=1:22 => 1 hour and 22 minutes
  • walltime=0:03:30 => 3 minutes and 30 seconds
Working with more than one node

You will probably want to use more than one node on a given site.

To reserve two hosts (two nodes), in interactive mode, do:

Terminal.png fnancy:
oarsub -l host=2 -I

or equivalently (nodes is an alias for host):

Terminal.png fnancy:
oarsub -l nodes=2 -I

You will obtain a shell on the first node of the reservation. It is up to you to connect to the other nodes and distribute work among them.

By default, you can only connect to nodes that are part of your reservation, and only using the oarsh connector to go from one node to the other. The connector supports the same options as the classical ssh command, so it can be used as a replacement for software expecting ssh.

Terminal.png gros-49:

uniq $OAR_NODEFILE # list of resources of your reservation
oarsh gros-1 # try to connect a node not in the file (will fail)
oarsh gros-54 # connect to the other node of your reservation (should work)

ssh gros-54 # this will fail
Note.png Note

To take advantage of several nodes and distribute work between them, a good option is GNU_Parallel.

oarsh is a wrapper around ssh that enables the tracking of user jobs inside compute nodes (for example, to enforce the correct sharing of resources when two different jobs share a compute node). If your application does not support choosing a different connector, it is possible to avoid using oarsh for ssh with the allow_classic_ssh job type, as in

Terminal.png fnancy:
oarsub -l host=2,walltime=0:30:0 -I -t allow_classic_ssh

Selecting specific resources

So far, all examples were letting OAR decide which resource to allocate to a job. It is possible to obtain finer-grained control on the allocated resources by using filters.

Selecting nodes from a specific cluster or cluster type
  • Reserve nodes from a specific cluster
Terminal.png fgrenoble:
oarsub -p "cluster='yeti'" -l host=2,walltime=2 -I
Terminal.png fnancy:
oarsub -q production -p "cluster='grappe'" -l host=2,walltime=2 -I
  • Reserve nodes from an exotic cluster type
Terminal.png flyon:
oarsub -t exotic -p "cluster='pyxis'" -l host=2,walltime=2 -I

Clusters with the exotic type either have a non-x86 architecture, or are specific enough to warrant this type. Resources with an exotic type are never selected by default by OAR. Using -t exotic is required to obtain such resources.

The type of a cluster can be identified on the Hardware pages, see for instance Lyon:Hardware.

Warning.png Warning

When using the -t exotic option, you can still obtain non-exotic resources! You should filter on the cluster name or other properties if you want exclusively exotic resources.

Using OAR properties

The OAR nodes database contains a set of properties for each node, and the -p option actually filters based on these properties:

  • Nodes with Infiniband FDR interfaces:
Terminal.png fnancy:
oarsub -p "ib='FDR'" -l host=5,walltime=2 -I
  • Nodes with power sensors and GPUs:
Terminal.png flyon:
oarsub -p "wattmeter='YES' and gpu_count > 0" -l host=2,walltime=2 -I
  • Nodes with 2 GPUs:
Terminal.png flille:
oarsub -p "gpu_count = 2" -l host=3,walltime=2 -I
  • Nodes with a specific CPU model:
Terminal.png flille:
oarsub -p "cputype = 'Intel Xeon E5-2630 v4'" -l host=3,walltime=2 -I
  • Since -p accepts SQL, you can write advanced queries:
Terminal.png fnancy:
oarsub -p "wattmeter='YES' and host not in ('graffiti-41.nancy.grid5000.fr', 'graffiti-42.nancy.grid5000.fr')" -l host=5,walltime=2 -I

The OAR properties available on each site are listed on the Monika pages linked from Status (example page for Nancy). The full list of OAR properties is available on this page.

Advanced job management topics

Reservations in advance

By default, oarsub will give you resources as soon as possible: once submitted, your request enters a queue. This is good for non-interactive work (when you do not care when exactly it will be scheduled), or when you know that the resources are available immediately.

You can also reserve resources at a specific time in the future, typically to perform large reservations over nights and week-ends, with the -r parameter:

Terminal.png fnancy:
oarsub -l host=3,walltime=3 -r '2020-12-23 16:30:00'
Note.png Note

Remember that all your resource reservations must comply with the Usage Policy. You can verify your reservations' compliance with the Policy with usagepolicycheck -t.

Job management

To list jobs currently submitted, use the oarstat command (use -u option to see only your jobs). A job can be deleted with:

Terminal.png fnancy:
oardel 12345
Extending the duration of a reservation

Provided that the resources are still available after your job, you can extend its duration (walltime) using e.g.:

Terminal.png fnancy:
oarwalltime 12345 +1:30

This will request to add one hour and a half to job 12345.

For more details, see the oarwalltime section of the Advanced OAR tutorial.

Deploying your nodes to get root access and create your own experimental environment

Using oarsub gives you access to resources configured in their default (standard) environment, with a set of software selected by the Grid'5000 team. You can use such an environment to run Java or MPI programs, boot virtual machines with KVM, or access a collection of scientific-related software. However, you cannot deeply customize the software environment in a way or another.

Most Grid'5000 users use resources in a different, much more powerful way: they use Kadeploy to re-install the nodes with their software environment for the duration of their experiment, using Grid'5000 as a Hardware-as-a-Service Cloud. This enables them to use a different Debian version, another Linux distribution, or even Windows, and get root access to install the software stack they need.

Note.png Note

There is a tool, called sudo-g5k (see the sudo-g5k page for details), that provides root access on the standard environment. It does not allow deep reconfiguration as Kadeploy does, but could be enough if you just need to install additional software, with e.g. sudo-g5k apt-get install your-favorite-editor. The node will be transparently reinstalled using Kadeploy after your reservation. Usage of sudo-g5k is logged.

Deploying nodes with Kadeploy

Reserve one node (the deploy job type is required to allow deployment with Kadeploy):

Terminal.png fnancy:
oarsub -I -l host=1,walltime=1:45 -t deploy

Start a deployment of the debian10-x64-base image on that node (this takes 5 to 10 minutes):

Terminal.png fnancy:
kadeploy3 -f $OAR_NODE_FILE -e debian10-x64-base -k

The -f parameter specifies a file containing the list of nodes to deploy. Alternatively, you can use -m to specify a node (such as -m gros-42.nancy.grid5000.fr). The -k parameter asks Kadeploy to copy your SSH key to the node's root account after deployment, so that you can connect without password. If you don't specify it, you will need to provide a password to connect. However, SSH is often configured to disallow root login using password. The root password for all Grid'5000-provided images is grid5000.

Reference images are named debian version-architecture-type. The debian version can be debian10 (Debian 10 "Buster", released in 07/2019) or debian9 (Debian 9 "stretch", released in 06/2017). The architecture is x64 (in the past, 32-bit images were also provided). The type can be:

  • min = a minimalistic image (standard Debian installation) with minimal Grid'5000-specific customization (the default configuration provided by Debian is used): addition of an SSH server, network interface firmware, etc (see changes).
  • base = min + various Grid'5000-specific tuning for performance (TCP buffers for 10 GbE, etc.), and a handful of commonly-needed tools to make the image more user-friendly (see changes). Those could incur an experimental bias.
  • xen = base + Xen hypervisor Dom0 + minimal DomU (see changes).
  • nfs = base + support for mounting your NFS home and accessing other storage services (Ceph), and using your Grid'5000 user account on deployed nodes (LDAP) (see changes).
  • big = nfs + packages for development, system tools, editors, shells (see changes).

And for the standard environment:

  • std = big + integration with OAR. Currently, it is the debian10-x64-std environment which is used on the nodes if you or another user did not "kadeploy" another environment (see changes).

As a result, the environments you are the most likely to use are debian10-x64-min, debian10-x64-base, debian10-x64-xen, debian10-x64-nfs, debian10-x64-big, and their debian9 counterparts.

Environments are also provided and supported for some other distributions, only in the min variant:

  • Ubuntu: ubuntu1804-x64-min and ubuntu2004-x64-min
  • Centos: centos7-x64-min and centos8-x64-min

Last, an environment for the upcoming Debian version (also known as Debian testing) is provided: debiantesting-x64-min (only min as well).

The list of all provided environments is available using kaenv3 -l. Note that environments are versioned, and old versions of reference environments are available in /grid5000/images/ on each frontend (as well as images that are no longer supported, such as CentOS 6 images). This can be used to reproduce experiments even months or years later, still using the same software environment.

Customizing nodes and accessing the Internet

Now that your nodes are deployed, the next step is usually to copy data (usually using scp or rsync) and install software.

First, connect to the node as root:

Terminal.png fnancy:
ssh root@gros-42

You can access websites outside Grid'5000 : for example, to fetch the Linux kernel sources:

Warning.png Warning

Please note that, for legal reasons, your Internet activity from Grid'5000 is logged and monitored.

Let's install stress (a simple load generator) on the node from Debian's APT repositories:

Terminal.png gros-42:
apt-get install stress

Installing all the software needed for your experiment can be quite time-consuming. There are three approaches to avoid spending time at the beginning of each of your Grid'5000 sessions:

  • Always deploy one of the reference environments, and automate the installation of your software environment after the image has been deployed. You can use a simple bash script, or more advanced tools for configuration management such as Ansible, Puppet or Chef.
  • Register a new environment with your modifications, using the tgz-g5k tool. More details are provided in the Advanced Kadeploy tutorial.
  • Use a tool to generate your environment image from a set of rules, such as Kameleon or Puppet. The Grid'5000 technical team uses those two tools to generates all Grid'5000 environments in a clean and reproducible process

All those approaches have different pros and cons. We recommend that you start by scripting software installation after deploying a reference environment, and that you move to other approaches when this proves too limited.

Checking nodes' changes over time

The Grid'5000 team puts on strong focus on ensuring that nodes meet their advertised capabilities. A detailed description of each node is stored in the Reference API, and the node is frequently checked against this description in order to detect hardware failures or misconfigurations.

To see the description of grisou-1.nancy.grid5000.fr, use:

Cleaning up after your reservation

At the end of your resources reservation, the infrastructure will automatically reboot the nodes to put them back in the default (standard) environment. There's no action needed on your side.

Going further

In this tutorial, you learned the basics of Grid'5000:

  • The general structure of Grid'5000, and how to move between sites
  • How to manage you data (one NFS server per site; remember: it is not backed up)
  • How to find and reserve resources using OAR and the oarsub command
  • How to get root access on nodes using Kadeploy and the kadeploy3 command

You should now be ready to use Grid'5000.

Additional tutorials

There are many more tutorials available on the Users Home page. Please have a look at the page to continue learning how to use Grid'5000.