Skip to content

CNRS logo

ComputeOps (COps) : A DecaLog Master Project's Workgroup

Site still under writing

This website is still under construction and built collaboratively: we need your help to keep contents the most updated as possible.

Abstract

The High Performance Computing (HPC) domain aims to optimise code for use with the latest multicore and parallel technologies, including specific processor instructions. In this computing framework, portability and reproducibility are key concepts. One effective solution to meet these requirements is the use of Linux containers. These "light virtual machines" enable users to encapsulate applications within its environment in processes. Containers have recently been identified as a key solution for providing a multi-infrastructure environment for developers and system administrators. Furthermore, they offer reproducibility due to image building files. Two container solutions are emerging: Docker is used for micro-services and Singularity for computing applications. We hereby present the Com-puteOps project, the aim of which is to investigate the benefits of containers for HPC applications.

doi.org/10.1051/epjconf/201921407004 | HAL

Objectives

  1. Foster collaboration between IN2P3 labs, collaborators and experiments on COps activities
  2. Share/Exchange feedback state-of-the-art knowledge between project members and spread it across IN2P3
  3. Encourage engineers and technicians in computing and infra administration to COps meetups and seminars
  4. Document ongoing DecaLog projects and HEP related tutorials

Coordination

  • Richard Randriatoamanana, Subatech, Nantes/IMT – Group Lead (since 2025)
  • Fabrice Jammes, LPC, Clermont-Ferrand – DecaLog Coordinator

News

All news →

Lab representatives

Each IN2P3 lab involved in the project has a point of contact for ML activities. A good starting point would be to contact them to let them know what you are working on or plan to be working on.

Point of contact in each member labs
Lab City Representative Email
APC Paris Cécile Cavet cecile [dot] cavet [at] apc [dot] in2p3 [dot] fr
CC-IN2P3 Villeurbanne Sébastien Gadrat sebastien [dot] gadrat [at] cc [dot] in2p3 [dot] fr
IPHC Strasbourg Jérôme Pansanel jerome [dot] pansanel [at] iphc [dot] cnrs [dot] fr
IP2I Lyon Denis Pugnere d [dot] pugnere [at] ipni [dot] in2p3 [dot] fr
L2IT Toulouse Sylvain Caillou sylvain [dot] caillou [at] l2it [dot] in2p3 [dot] fr
LPCA Clermont-Ferrand Fabrice Jammes fabrice [dot] jammes [at] clermont [dot] in2p3 [dot] fr
LPNHE Paris Amar Hami amar [dot] hami [at] lpnhe [dot] in2p3 [dot] fr
Subatech Nantes Richard Randriatoamanana randria [at] subatech [dot] in2p3 [dot] fr

Getting started with...

  • Container (docker, apptainer)
  • Container for computing by M. Souchal, talks at (https://souchal.pages.in2p3.fr/container4science/prez.html) and (https://sed-paris.gitlabpages.inria.fr/ai-community/dev_talks/2021-07-13/)
  • Kubernetes
  • Labs Kubernetes by F. Jammes

Mailing list

Used for asking specific questions or sharing information about upcoming events.

Register Write to the list

How to contribute?

This website is built collaboratively: we need your help to keep the publications, projects and events up to date.

Add a project Add a PhD thesis Add a publication

Detailed contribution guide (issues, merge requests)

There are 3 ways you can contribute:

1. Adding new content

  • To contribute a new publication, the preferred method is to update the bibtex file through a merge request (see below in section 3). The entry should look like this

  • To contribute a news item (workshop, school, call, announcement...), add a Markdown file in docs/news/posts/ through a merge request (see section 3), named YYYY-MM-short-title.md. The easiest is to copy an existing post. A post is made of :

    • a header with the date and the categories (Workshop, School, Conference, Community or Call, which sets the colour of the card). Add pin: true to keep a news at the top of the list;
    • a # Title line;
    • a short text shown in the news list, optionally with a preview image displayed on the right (put the image in docs/img/; wide banners are cropped to their top);
    • a <!-- more --> line, followed by an optional longer text only shown on the news page itself.

    If you are not at ease with GitLab, open an issue with the text, date and a link, and we will add it.

2. Reporting an issue or requesting a modification in the website

To report an issue or propose a modification in the pages, you may open an issue with all the needed information to be added to the website (check the current pages to know what you need to provide).

To do so, you will need to connect to the GitLab platform using your eduGAIN credentials.

3. Propose changes yourself

If you want to propose important changes to the pages, please start a discussion first by opening an issue and mention @randriatoamanana.

Smaller changes can be proposed directly through merge requests:

  1. Request to join the project on GitLab (up top, near the project ID).
  2. Create a new branch
  3. Modify the markdown files in the /docs directory or the in2p3cops_publications.bib
  4. Test locally (see Website development)
  5. Open a merge request and assign it to @randriatoamanana

If you include new markdown pages, make sure they are listed in the nav section of the mkdocs.yml file in the root directory.