-
Notifications
You must be signed in to change notification settings - Fork 0
meeting Jul 7 2022
- date & time: Thu 2 June 2022 - 14:00 CET (12:00 UTC)
- (every first Thursday of the month)
- venue: (online, see mail for meeting link, or ask in Slack)
- agenda:
- Quick introduction by new people
- EESSI-related meetings in last month
- Progress update per EESSI layer (incl. bot for software layer)
- 2021.12 version of pilot repository (+ next pilot version?)
- AWS/Azure sponsorship update + OCRE funding opportunity
- Google Summer-of-Code project: Gentoo Prefix on RISC-V
- Past & upcoming events
- Q&A
(by Bob & Kenneth)
None
Request for giving an EESSI update talk at the CernVM workshop, as a follow-up to the presentation at the CernVM workshop 2021.
It would be nice to have an EESSI community meeting in the same week as the CernVM workshop; see last slide.
Bob gave talks on EESSI at Dutch universities, by invitation of Dell. They all seemed interested in EESSI, but some need specific tools, and they all want to know when it's ready.
- should consider S3-backed Stratum-1
- cheaper (?) than using regular storage
- scalability "for free" thanks to S3 caching with AWS CloudFront
- maybe also more resilient when S1's backed by S3 and backed by regular fileystem are combined
- raises the question of how these S1's are represented in GeoAPI?
- should AWS S3 be picked when client is in AWS network? (similar for Azure)
Alternative way of getting information about security vulnerabilities could be to get subscribed to the security "queue" in the Gentoo bug tracker. Guilherme will ask if this is possible and can act as a liaison.
-
We need people to try out the scripts from PR 172.
- mostly tried on Debian for now, also need to try other OSs
-
The status with respect to testing is still more or less the same: we have some open PRs for GROMACS and TensorFlow tests.
-
AWS is using ReFrame as well, and in the last meething with them they suggested to have a separate project where we collaborate (with AWS, Spack, ...?) on writing (ReFrame) tests and making these available.
-
Thomas made lots of progress on the bot, and more NESSI colleagues are looking into making improvements now as well.
-
There are two options with regards to building on different clusters: either there's one coordinating bot that sends tasks to different bots, or there can be multiple instances of the same bot running on different clusters.
-
Caspar will ask Thomas if it already makes sense to add another step to the bot workflow for testing the built software.
-
Software licenses
- can use licensee tool used by GitHub
- for open source software we also need to provide source tarballs via same mechanism
- For an alpha release we would need:
- new Stratum 0 (properly set up, with yubikeys etc)
- name of the repository (software.eessi.io?)
- adhere to licenses (see above)
- working version of a bot with minimal functionality to add software
It's a competitive call, the decision will probably follow in September.
We need something to start with, and work out procedures like elections etc. For the latter, the advisory committee can help as well.