Getting Involved
The Ubuntu High-Performance Computing (HPC) community meets once a week. The next Ubuntu HPC community is next Wednesday, October 16th, at 17:30 UTC over Jitsi. Want to get involved or just generally interested in our community? Check out the links below!
Be sure to also check out the events calendar to see other upcoming events the Ubuntu HPC community has planned!
Meeting Notes
-
Agenda
- Welcome Dominic!!
- Status
slurm_ops- Adding last patches required for HPC use case
MYSQL_UNIX_PORT- ulimit rules
- Adding last patches required for HPC use case
- slurm-charms PRs in the oven
- Enable prometheus on main
- Use
slurm_opsfor management
- Repository tooling - call for opinions!
- tox
- poetry
- monorepo tooling
- Anything we want to focus for OpenInfra NA Days
- What should I mention about the community?
- Welcome Dominic!!
-
Discussion notes:
-
Feedback on
poetry:- poetry doesn’t seem to handle workspaces well. Building local components doesn’t work right because poetry can’t pull the correct metadata. Pulling via git URL builds the entire repository which is not desirable.
- GitHub - DavidVujic/poetry-multiproject-plugin: A Poetry plugin that makes it simple to share code between projects in monorepos.
- GitHub - gerbenoostra/poetry-plugin-mono-repo-deps: Poetry plugin for mono repos to replace path dependencies with named dependencies
- Solved issue with the local dependency by using a tool called
stickywheel: jobbergate/jobbergate-agent/pyproject.toml at main · omnivector-solutions/jobbergate · GitHub
- Check if poetry + charmcraft has integration with pyproject.toml. Make sure that charmcraft can also properly support poetry.
- How does
uvandpoetrydefer when it comes to workspaces?
- poetry doesn’t seem to handle workspaces well. Building local components doesn’t work right because poetry can’t pull the correct metadata. Pulling via git URL builds the entire repository which is not desirable.
-
Feedback on
tox:- Just document common commands that should be used when creating a new tox.ini file. If there’s any major issues, comment on shared document.
-
Feedback on monorepo tooling:
repository.pygets the job done but we should be cognizant that it might not be tenable as we scale up the amount of monorepos we have. One change needs to be merged several times.- Consider making a small PoC if there’s spare time.
-