-
Notifications
You must be signed in to change notification settings - Fork 7
feat!: overhaul slurmdbd charm API #22
feat!: overhaul slurmdbd charm API #22
Conversation
82854f1
to
1e863d8
Compare
1e863d8
to
43b9ca7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a few comments. We'll need to fix unit tests before we merge. Seems to just be some mismatch between expected status messages as they've changed with the updated methods.
43b9ca7
to
6a73d4c
Compare
Thanks, @NucciTheBoss! I've addressed your comments and suggestions and resolved all but the type-check conversation. I'll move these changes forward into the slurmctld-operator next. Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a few more suggested changes. After this I think we're good to merge. I'll just want to check against the other operators since the integration tests are relying upon incompatible charms in Charmhub currently
It still needs tests fixed and commenting for type |
Okay, this is looking real good now! For the unit tests, seems like we just need to mock the outputs of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couple comments on the ops manager. I noticed some bugs in the __init__
method that will cause the slurmdbd operator to fail to deploy 😅
e3d6ddf
to
cb000c8
Compare
These changes improve the slurmdbd charm in a number of ways. 1) remove slurm-ops-manager 2) remove unused code 3) emit relation data to the charm via events 4) remove dependency on slurmctld 5) general code cleanup 6) consolidate yaml files into charmcraft.yaml 7) add type tests 8) rename interface slurmdbd -> slurmctld 9) update readme Address feedback from PR review. * add package managers for each package, slurmdbd and munge * address docstring issues * move constants to constants.py * address test failure * pin requirements * install funtions handle failure cases * upgrade to checkout action v4
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm happy with how this pull request has shaped up! I'm ready to merge it 🚢
Only one small nit, but I can commit that to the batch. Just removing .mypy_cache/
from .gitignore since we now using pyright instead.
We can further refine the charm in future pull requests as we stabilize the new API. I'd like to see how we can use a dedicated charm library to reduce code duplication for managing Slurm. Thank you for this work @jamesbeedy 🚀
Swapped mypy for pyright
Please reference the Slurm Charms Change Summary Document for an in-depth explanation of these changes.
Note: Unit tests have been mangled and are not currently passing, although the charm is working as expected. Need to spend a few minutes going through and fix the broken unit tests.
Related:
git describe ... > version
#5