oar

Group Name

OAR

Home Page URL

Description

OAR is a Resource Management System (RMS) for high performance computing clusters. It is based upon an original design that emphasizes on low software complexity by using high level components. The global architecture is built upon the scripting languages Perl and Ruby, a relational database engine Mysql/Postgresql and a parallel/scalable remote execution tool for clusters TakTuk (http://taktuk.gforge.inria.fr/).

OAR is used as the base of other sub-projects like CiGri (http://cigri.imag.fr) and ComputeMode (http://comutemode.imag.fr). CiGri is a simple computing grid for parametric applications grabbing idle cpus. It is plugged on OAR for grid scientific experiments. Moreover, OAR is the RMS of the French -experimental grid platform Grid5000 (http://www.grid5000.fr).

OAR projects' objective is to prove that it is possible today to build a complex system for resource management using such tools without sacrificing efficiency and scalability.

Why is your group applying to participate? What do you hope to gain by participating?

OAR project is an open source Resource Management System (RMS) which aims on one hand to provide a production RMS and on the other hand a tool for research on the specific aspects around resource management and scheduling. The project becomes bigger and the extension needs are increasing. Therefore, one of the application reasons is to attract more contributors who will have the opportunity to work in a High Performance Computing (HPC) research project. Furthermore our goal is to spread the word for Open Source development and research upon the field of HPC.

What is the main public mailing list for your group?

oar-devel@lists.gforge.inria.fr

Where is the main IRC channel for your group?

No IRC channel

What criteria do you use to select the members of your group? Please be as specific as possible.

Members are selected depending their experience with the code and their motivation to devote time on the mentoring process.

Olivier Richard is the project founder and leader he is an Assistant Professor of computer science. Joseph Emeras, Bruno Bzeznik and Romain Cavagna are the current main project developers. Yiannis Georgiou is a PHD student responsible for the research aspects of the project. Guillaume Huard is an Assistant Professor of computing science and founder of TakTuk project. Gregory Mounie is an Assistant Professor of computing science and Derrick Kondo is a Researcher.

Has your group participated previously? If so, please summarize your involvement and any past successes and failures.

OAR project has applied and participated on GSoC 2008 for the first time. Our organization received 13 interesting proposals from 12 students. We were finally allocated 2 slots and we turned out to have two very successful projects (http://oar.imag.fr/works/gsoc/2008/index.html). The code developed on the first one has been already integrated on the stable version. The work of the second project has been used as the basis for an article accepted for publication on an international workshop. OAR sent one group member to the 2008 mentor summit. OAR participated again in 2009 and this time, 4 slots where allocated. Amongst these 4 slots, 3 of them where successful and one failed. The 3 successful projects where quickly integrated and are in production. The kameleon project, initiated during gsoc 2009 is now a keystone for several other tools.

If your organization participated in past GSoCs, please let us know the ratio of students passing to students allocated, e.g. 2006: 3/6 for 3 out of 6 students passed in 2006.

2008: 2/2

2009: 3/4

If your group has not previously participated, have you applied in the past? If so, for what sort of participation?

Not applicable

What license does your organization use?

GNU GENERAL PUBLIC LICENSE

What is the URL to the ideas list of your organization?

What is the main development mailing list for your group?

oar-devel@lists.gforge.inria.fr : developer's list

oar-gsoc@lists.gforge.inria.fr : gsoc dedicated list (for applying, asking questions to mentors, communicating between students and mentors)

What is the application template you would like contributors to your organization to use.

    Name
    Email: your google email
    Background: technical and programming experience and skills. Who are you? What makes you the best person to work on this project?
    Why you are interested in the project, and what do you anticipate to gain from it.
    Programs or projects you have previously authored or contributed to, in particular those available as open-source, including, if applicable, any past Summer of Code involvement.
    Project Title
    Synopsis: a short description.
    Benefits to OAR.
    Deliverables: quantifiable results and goals.
    Project Details: a more detailed description.
    Project Schedule: how long will the project take? When can you begin work?

What is your plan for dealing with disappearing mentors?

The possibility is very limited for something like this to happen because all mentors work full time on the same laboratory. We will continue the strategy adopted last years to provide 2 mentors per student. In the worst case of a disappearing contributor, one of the backup mentors will immediately take its place.

What is your plan for dealing with disappearing students?

We will try to minimize this risk through a thorough student selection, upon each specific project. During the program, meetings will be planned, to provide a detailed guidance to the student and follow its progress. For the unexpected happening we will use a backup replacement student list, to complete the work.

What steps will you take to encourage contributors to interact with your community before, during, and after the program?

One of our organizations bigger user and partner is the Grid5000 (http://www.grid5000.fr) experimental grid platform. There is a constant interaction with this community.

During the program the student will have an SVN, wiki and mailing list account. Distant or even face-to-face meetings will be organized once a week between the student and its mentor. Furthermore, as an OAR contributor, students will get the opportunity to have a Grid5000 account, use Grid5000 infrastructure and interact with the Grid5000 community.

What will you do to ensure that your accepted contributors stick with the project after the program concludes?

OAR project has always been working with students and it is the organization willingness to keep students as contributors, after their studies. Students that presented a good work and positively interacted within the community may get the funds to continue their work in the project.

Please select your backup group administrator.

Yannis: gohnwej

wiki/old/gsoc_2009_application_questions_and_further.txt · Last modified: 2013/07/10 22:55 by 127.0.0.1
Recent changes RSS feed GNU Free Documentation License 1.3 Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki