Difference between revisions of "Grid5000:UsagePolicy"
|Line 49:||Line 49:|
== Mailing Lists ==
== 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).
As a Grid'5000 user you are automatically subscribed to the Grid'5000 usersmailing 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).
Revision as of 08:58, 15 March 2007
You are a Grid'5000 citizen
The Grid'5000 platform is intended to support research in all areas of computer science related to large scale distributed processing and networking. You should use Grid'5000 in the perspective of large scale experiments (at least 3 sites and 1000 CPUs).
You may generate useful results for other communities, as long as the community of computer science researchers learns something from your experiments.
It is a shared tool, used by many people with different and varying needs. The administrators pursue the following objectives, the main one being the first of this list:
- 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.
- 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 in general.
You can use the platform with two different modes: submissions and reservations.
- Submission: you submit an experiment when you let the scheduler decide when to run it.
- Reservation: when you make a reservation, you gain usage of the platform at the time you explicitly specified. You will then need to launch your experiment interactively.
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 clusters.
- Job size: the size of a job is defined by the cpu time usable by the job: (nb nodes) * (nb procs) * (job walltime). A 2 hours job using 32 bi-processor nodes has a size of 128h.
Good usage rules (All users)
- Please try to plan large scale experiments during night-time or week-ends.
- 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 developing or preparing an experiment. Between 09:00 and 18:00 (CEST) during the other days, you should not use more than the equivalent of 2 hours on all the processors of the cluster during a given day (e.g. on a 64 bi-processor cluster, you should not use more than 2*2*64 = 256h between 09:00 and 18:00 CEST).
- If you plan to use machines on a Tuesday for anything else than a large scale experiment, please wait after 13:00 (CEST) on the preceding Monday to make your reservation.
- You should not have more than 2 reservations in advance, because it kills down resource usage. Please optimize and submit jobs instead.
- You should not be submitting jobs or making reservations if your experiment is not described in your User report.
- You must mention Grid'5000 in all publications presenting results or contents obtained or derived from the usage of Grid'5000 and you must update your User report. The official acknowledgment to use in your publication must be the following:
Acknowledgment: Experiments presented in this paper were carried out using the Grid'5000 experimental testbed, an initiative from the French Ministry of Research through the ACI GRID incentive action, INRIA, CNRS and RENATER and other contributing partners (see https:// www.grid5000.fr)
Good usage rules (Local users)
Some sites have opened user accounts on a local branch of LDAP. Users on these local branches only have access to the local cluster. In addition to the above rules, they should:
- not have more than 1 reservation in advance;
- prefer submissions (let oar decide when to run the job) to reservations (specifying a time when the job should run) as much as possible;
- limit the size of their jobs to reasonable proportions such as those locally defined by the local site they have access to (e.g. in Rennes, this would be around 1280h).
Platform usage is actively monitored by Grid'5000 staff. In case of unconform use, your account will be locked. Unconform use includes users whose user report is unsufficiently filled with regard to their resource usage.
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).