-
Notifications
You must be signed in to change notification settings - Fork 6
Home
Welcome to the ContainerHackathon wiki!
This page contains material for the Container Hackathon for Modellers of the ESiWACE2 project, held from Dec. 3 to Dec. 5, 2019, in Lugano, Switzerland. Until today, we have received applications from 17 people representing 7 different codes.
The agenda has been planned in order to help the teams port their native codes into containers. For this reason, a dedicated mentor will be working together with each of the teams. The expected milestones are as follows:
- After the first day, a sane build environment is working and a Hello World type of container exists.
- By the end of the second day, the code should be containerized and the test case selected by the team should be passing.
- The third day is reserved for launching the containers at scale on Piz Daint (a reservation of 160 GPU nodes will be available) and preparing the final report.
For teams that are lagging behind, the third day will give them the opportunitity of catching up with the second milestone and finish the hackathon with a working version of their code in a container.
Each team will deliver a short report about their experiences while containerizing the codes. These reports will be used as the basis for the ESiWACE2 deliverable of this task. Additionally, this Git repository can be used to host non-licensed material that can be posted for everyone's benefit (e.g., Dockerfiles, step-by-step instructions, reports, etc.)
The teams are expected to do deliver a final report after the hackathon.
Please note that a report has to be delivered by each team before the end of the hackathon.
Here is a breakdown of the report with more details:
- A single paragraph abstract with the application description.
- A short overview of the application (without mathematics!)
- Break down of the containerization approach:
- Explain the starting point (e.g., CPU-code compiled with XXX compiler, GPU access using CUDA, etc)
- Shortly describe the test case that verifies the code is functioning correctly
- Steps you made porting the code to a Docker container (e.g., which components ported)
- OPTIONAL Performance profile of the code running natively and from a container, e.g., speedup graph.
- A final conclusion including:
- Short feedback about your experiences
- Obstacles you encountered, and how you solved them
- Lessons that you would like to share with other teams, e.g., suggestions on how to improve the process, better documentation, etc.
Last but not least, any general comments about this Container Hackathon for Modellers will be really useful for the organizers.
TBD
TBD