Grid5000:UsagePolicy

From Grid5000
Revision as of 11:58, 24 May 2006 by Pneyron (talk | contribs) (Good usage rules (All users))

Jump to: navigation, search

How to be a good Grid'5000 citizen ?

Principles

The Grid'5000 platform is intended to support research in all areas of computer science related to grid computing. It is not intended to support research projects that need computing ressources.

It is a shared tool, used by many people with different and varying needs.

The main objective of the administrators is to make the tool available to experiments involving a significant number of nodes (in the 1000's). To make this possible, reservation fragmentation must be avoided as much as possible as using a complete cluster in only one site can prevent reservations with a significant number of nodes.

A second objective is to keep the platform available for the development of experiments during the day. Therefore, reservations using all the nodes available on one site during work hours (in France) should be avoided.

Platform availability is still greatly dependant on the administrators solving day to day issues. Therefore, the third objective is to allow for experiments to run while administrators are available.

The last objective is to use the machines as much as possible, as long as this usage doesn't interfere with the first three objectives.

Good usage rules (All users)

  1. Tuesday is the only day where you should feel authorized to use all the machines of a cluster during work hours. On the other days, please leave a few nodes for people developping or preparing an experiment.
  2. If you want to use machines on a tuesday, please do not reserve them before 13:00pm on the preceeding monday if is not a big scale experiment.
  3. You should probably not have more than 2 reservations in advance, because it kills good ressource usage. Please submit jobs instead
  4. You should not be submitting jobs or making reservations if your experiment is not described in your User report

Good usage rules (Local users)

Some sites have openned accounts on a local branch of ldap. Users on these branches only have access to the local cluster. In addition to the above rules, they should

  1. Not have more than one reservation in advance
  2. Prefer submissions (let oar decide when to run the job) to reservations (specifying a time when the job should run) as much as possible
  3. Limit the size of their jobs to reasonnable proportions such as those locally defined by the local site they have access to. The size of a job can by defined by the product of the number of machines by the time the cluster is used (eg. In Rennes, this would be arround 640h).