Difference between revisions of "Grid5000:UsagePolicy"

From Grid5000
Jump to: navigation, search
Line 3: Line 3:
 
{{Status|Approved}}
 
{{Status|Approved}}
  
== General Principles ==
+
= General principles =
Grid'5000 is a scientific instrument supporting experiment-driven research in all areas of computer science, including high performance computing, distributed computing, networking and big data. The use of Grid'5000 should lead to results or contribute to education in those research areas.  
+
Grid'5000 is a scientific instrument supporting experiment-driven research in all areas of computer science, with a focus on distributed computing, high performance computing, big data and networking. Its use should lead to results or contribute to education in this area. Access policy is detailed on [[Grid5000:Get_an_account|that page]].
  
 
This charter defines rules to allow the shared use of this infrastructure by different communities of users, with different needs.
 
This charter defines rules to allow the shared use of this infrastructure by different communities of users, with different needs.
  
If your intended usage does not fit within the detailed rules presented below, you request a special permission from the executive committee (resp-sites_gis_g5k@inria.fr). Such exceptions are granted on a regular basis, as can be seen on [[Grid5000:SpecialUsage| the page listing those]].
+
If your intended usage does not fit within the detailed rules presented below, you can request a special permission from the executive committee (resp-sites_gis_g5k@inria.fr). Such exceptions are granted on a regular basis, as can be seen on [[Grid5000:SpecialUsage| the page listing those]].
  
== Resource usages rules ==
+
= Acknowledging Grid'5000 usage in publications =
=== Glossary ===
+
'''Grid'5000 must be acknowledged in all publications''' presenting results or contents obtained or derived from the usage of Grid'5000. '''All those publications must be added to the [https://hal.archives-ouvertes.fr/GRID5000 Grid'5000 collection on the HAL Open Archive].''' This can be achieved by adding your publication to HAL (possibly without the full text), and specifying "GRID5000" in the ''collaboration'' field. The '''official acknowledgement''' to use in your publication is the following:
To request resources on the platform, you can submit '''jobs''' (tasks) using two different modes: submissions and reservations.
 
* '''Submission''': you submit a job and let the scheduler decide when to run it.
 
* '''Reservation''': you submit a job for a specific date and time in the future.
 
 
 
The different sites participating in Grid'5000 do not have clusters of the same size. Therefore, you should take into account job size when you plan an experiment.
 
* '''Experiment''': An experiment is typically composed of one or more jobs running on Grid'5000's resources.
 
* '''Job size''': the size of a job is defined by the cpu time usable by the job: (nb nodes) * (nb cores) * (job walltime). A 2 hours job using 32 dual-processor dual core nodes has a size of 256 cpu.h.
 
 
 
=== Rules ===
 
# You should not be submitting jobs or making reservations if your '''experiment''' is not '''described''' in your '''[https://api.grid5000.fr/stable/reports/_admin/index.html User report]'''.
 
# Large scale jobs must be executed during nights or week-ends (generally, using reservations to reserve resources in advance). Daytime is dedicated to smaller scale experiments, and preparatory work for large scale experiments. Specifically:
 
## Between 09:00 and 19:00 (local time of the cluster) during working days (monday to friday), you should not use more than the equivalent of 2 hours on all the cores of the cluster during a given day (e.g. on a 64 bi-processor (dual core) cluster, you should not use more than 2*2**2*64 = 512h between 09:00 and 19:00 CEST).
 
## It is generally considered rude to have jobs that cross the 09:00 and 19:00 boundaries during week days (to extend an overnight reservation, for example).
 
## You should not have job that last more than 14h outside week-end.
 
## You are not allowed to have more than 2 reservations in advance.
 
# You must '''mention Grid'5000 in all publications''' presenting results or contents obtained or derived from the usage of Grid'5000 and you must either specify Grid'5000 in the ''collaboration'' field if you upload a reference to a [http://hal.archives-ouvertes.fr/ HAL] frontend or update your '''[https://api.grid5000.fr/stable/reports/_admin/index.html User report]''' with a reference to your publication. The '''official acknowledgement''' to use in your publication is the following:
 
 
 
<blockquote>
 
 
<blockquote>
 
<blockquote>
 
Experiments presented in this paper were carried out using the Grid'5000
 
Experiments presented in this paper were carried out using the Grid'5000
Line 36: Line 18:
 
other organizations (see https://www.grid5000.fr).
 
other organizations (see https://www.grid5000.fr).
 
</blockquote>
 
</blockquote>
</blockquote>
 
  
=== Specific rules for open access users ===
+
= Resources reservation =
# Open Access users should not to use OAR's "Advance reservations" more than 24 hours in advance
+
Experiments performed on Grid'5000 typically require several resources reservations (or ''tasks'', or ''jobs'').
 +
Resources can be reserved using three different ''queues'' (''default'', ''production'', ''besteffort''), with different usage policies described below. Unless specified otherwise, jobs are submitted in the ''default'' queue. It is possible to reserve resources ''as soon as possible'' (''submissions'', typically for small-scale reservations) or using ''advance reservations'' (for larger-scale experiments, during nights and week-ends).
 +
 
 +
Notes:
 +
* On the technical level, resources reservations are handled by the OAR resource manager. When using the command line interface, the ''queue'' is selected using the <code>-q</code> switch (e.g.: <code>oarsub -q besteffort -I</code>).
 +
* The usage of the testbed is actively monitored by the Grid'5000 staff. In case of usage not following the above rules, your account will be locked. [https://intranet.grid5000.fr/report_abuse/ This form] can be used to report a Grid'5000 usage that does not meet those rules and is preventing you to access the resources you need for your work. You can also contact the Grid'5000 staff directly (support-staff@lists.grid5000.fr).
 +
 
 +
== Rules for the ''default'' queue ==
 +
'''Daytime is dedicated to smaller scale experiments''', and preparatory work for large scale experiments. '''Large scale jobs must be executed during nights or week-ends''' (generally, using advance reservations). Specifically:
 +
# Between 09:00 and 19:00 (Europe/Paris timezone) during working days (Monday to Friday, excluding public holidays in France), you should not use more than the equivalent of 2 hours on all the cores of the cluster during a given day (e.g. on a 64 bi-processor (quad core) cluster, you should not use more than (2 hours)*(2 CPU)*(4 cores)*(64 nodes)= 1024 core.hours).
 +
# Your jobs must not cross the 09:00 and 19:00 boundaries during week days (to extend an overnight reservation, for example). (This also means that you must not have job that last more than 14 hours outside week-ends.)
 +
# You are not allowed to have more than 2 reservations in advance. ''Open Access'' users must not make ''advance reservations'' more than 24 hours in advance. (those two rules are enforced by the resources reservation system).
 +
 
 +
== Rules for the ''production'' queue ==
 +
The ''production'' queue provides access to a different and smaller set of resources (only located in the Nancy site for time being), with a policy that is more suited to long-running, non-interactive jobs. See [[Nancy:Production|this page]] for more information.
  
== Monitoring ==
+
Access to the ''production'' queue is '''restricted to members of organizations that are directly supporting Grid'5000'''. As of 2016-03-01, those are:
Platform usage is actively monitored by the Grid'5000 staff. In case of usage not following the above rules, your account will be locked. The account of users whose user report is insufficiently filled with regard to their resource usage might also be locked.
+
* members of the following laboratories: CReSTIC (Reims), I3S (Sophia Antipolis), IRISA (Rennes), IRIT (Toulouse), LIFL (Lille), LIG (Grenoble), LIP (Lyon), LORIA (Nancy), CSC (Luxembourg)
The monitoring automatically detects usage not matching those rules, with some limitations:
+
* members of the following Inria research centers: Grenoble - Rhône-Alpes, Lille - Nord Europe, Nancy - Grand Est, Rennes - Bretagne Atlantique, Sophia Antipolis - Méditerranée
* resources are managed at the site level, but the charter rules are expressed at the cluster level
 
* current versions of OAR have no concept of charter when scheduling submissions
 
* monitoring tools automatically remove DEAD nodes from their calculations of cluster size
 
It is possible that Grid'5000 usage is flagged as not following the charter as a result of events that are urelated to users. This, as well as authorized exceptions, explains why the technical team will not act pro-actively. If incorrect usage is detrimental to you, please mail support-staff@lists.grid5000.fr to start investigations.
 
  
== Mailing Lists ==
+
== Rules for the ''besteffort'' queue ==
As a Grid'5000 user you are automatically subscribed to the Grid'5000 users' mailing lists. The traffic is not very high, so please keep an eye on those emails as they may contain important information (see [[Mailing lists]] for more information).
+
The ''besteffort'' queue provides a way to submit low-priority, interruptible jobs. Access to the ''besteffort'' queue is not restricted at this point. If you are planning to use the ''besteffort'' queue for large scale experiments, you should contact the Grid'5000 staff beforehand.
  
== Report an Abusive Usage ==
+
= Mailing lists =
[https://intranet.grid5000.fr/report_abuse/ This form] may be used to report a Grid'5000 usage that is not conform to the Grid'5000 charter and that is preventing you to access resources you need for your work. It will send an email to the offending user and to his managers, asking them to terminate jobs that do not fit within the charter. It will also warn Grid'5000 staff who are instructed to kill these jobs if it is not done by the user. Don't forget to check ongoing [[Grid5000:SpecialUsage|special permissions]].
+
As a Grid'5000 user you are automatically subscribed to the Grid'5000 users' mailing lists. The traffic is not very high, so please keep an eye on those emails as they may contain important information (see [[Mailing lists]] for more information). More than 500 users are subscribed to those lists, so please be careful before asking questions on the lists.

Revision as of 13:54, 6 June 2016


General principles

Grid'5000 is a scientific instrument supporting experiment-driven research in all areas of computer science, with a focus on distributed computing, high performance computing, big data and networking. Its use should lead to results or contribute to education in this area. Access policy is detailed on that page.

This charter defines rules to allow the shared use of this infrastructure by different communities of users, with different needs.

If your intended usage does not fit within the detailed rules presented below, you can request a special permission from the executive committee (resp-sites_gis_g5k@inria.fr). Such exceptions are granted on a regular basis, as can be seen on the page listing those.

Acknowledging Grid'5000 usage in publications

Grid'5000 must be acknowledged in all publications presenting results or contents obtained or derived from the usage of Grid'5000. All those publications must be added to the Grid'5000 collection on the HAL Open Archive. This can be achieved by adding your publication to HAL (possibly without the full text), and specifying "GRID5000" in the collaboration field. The official acknowledgement to use in your publication is the following:

Experiments presented in this paper were carried out using the Grid'5000 testbed, supported by a scientific interest group hosted by Inria and including CNRS, RENATER and several Universities as well as other organizations (see https://www.grid5000.fr).

Resources reservation

Experiments performed on Grid'5000 typically require several resources reservations (or tasks, or jobs). Resources can be reserved using three different queues (default, production, besteffort), with different usage policies described below. Unless specified otherwise, jobs are submitted in the default queue. It is possible to reserve resources as soon as possible (submissions, typically for small-scale reservations) or using advance reservations (for larger-scale experiments, during nights and week-ends).

Notes:

  • On the technical level, resources reservations are handled by the OAR resource manager. When using the command line interface, the queue is selected using the -q switch (e.g.: oarsub -q besteffort -I).
  • The usage of the testbed is actively monitored by the Grid'5000 staff. In case of usage not following the above rules, your account will be locked. This form can be used to report a Grid'5000 usage that does not meet those rules and is preventing you to access the resources you need for your work. You can also contact the Grid'5000 staff directly (support-staff@lists.grid5000.fr).

Rules for the default queue

Daytime is dedicated to smaller scale experiments, and preparatory work for large scale experiments. Large scale jobs must be executed during nights or week-ends (generally, using advance reservations). Specifically:

  1. Between 09:00 and 19:00 (Europe/Paris timezone) during working days (Monday to Friday, excluding public holidays in France), you should not use more than the equivalent of 2 hours on all the cores of the cluster during a given day (e.g. on a 64 bi-processor (quad core) cluster, you should not use more than (2 hours)*(2 CPU)*(4 cores)*(64 nodes)= 1024 core.hours).
  2. Your jobs must not cross the 09:00 and 19:00 boundaries during week days (to extend an overnight reservation, for example). (This also means that you must not have job that last more than 14 hours outside week-ends.)
  3. You are not allowed to have more than 2 reservations in advance. Open Access users must not make advance reservations more than 24 hours in advance. (those two rules are enforced by the resources reservation system).

Rules for the production queue

The production queue provides access to a different and smaller set of resources (only located in the Nancy site for time being), with a policy that is more suited to long-running, non-interactive jobs. See this page for more information.

Access to the production queue is restricted to members of organizations that are directly supporting Grid'5000. As of 2016-03-01, those are:

  • members of the following laboratories: CReSTIC (Reims), I3S (Sophia Antipolis), IRISA (Rennes), IRIT (Toulouse), LIFL (Lille), LIG (Grenoble), LIP (Lyon), LORIA (Nancy), CSC (Luxembourg)
  • members of the following Inria research centers: Grenoble - Rhône-Alpes, Lille - Nord Europe, Nancy - Grand Est, Rennes - Bretagne Atlantique, Sophia Antipolis - Méditerranée

Rules for the besteffort queue

The besteffort queue provides a way to submit low-priority, interruptible jobs. Access to the besteffort queue is not restricted at this point. If you are planning to use the besteffort queue for large scale experiments, you should contact the Grid'5000 staff beforehand.

Mailing lists

As a Grid'5000 user you are automatically subscribed to the Grid'5000 users' mailing lists. The traffic is not very high, so please keep an eye on those emails as they may contain important information (see Mailing lists for more information). More than 500 users are subscribed to those lists, so please be careful before asking questions on the lists.