Update coldfront-plugin-cloud to 0.12.0#196
Merged
jtriley merged 1 commit intonerc-project:mainfrom Mar 9, 2026
Merged
Conversation
jtriley
approved these changes
Mar 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The migration steps largely involve testing the new dynamic quotas feature (nerc-project/coldfront-plugin-cloud#287):
validate_allocationsbefore updating to the newest release and keep log messages. This is not part of the migration itself, but we'll use the log messages to later check if migration was sucessful. After migration is complete, we do not expectvalidate_allocationsto display any new warnings/errorscoldfront register_cloud_attributesregister_default_quotas.py. Keep log messages. This should be the only command needed complete migration, as it will register quotas that are already in use in our Openshift and Openstack resources. The steps below are checks to make sure the migration was successful.validate_allocations.pyagain. No new quota-related warnings should pop-upAvailable Quota Resources, which contains a long json string. This JSON string should list all quotas for that resourcemodelmesh-enabledlabel defined in their namespace (More details in Removesmodelmesh-enabledlabel coldfront-plugin-cloud#291)add_quota_to_resourceby running the command, then repeat the steps to create a new allocation, checking new allocations has the new quota attribute on Coldfront UI, and on cluster-sideremove_quota_from_resourceby running the command. Prior allocations should still visibly show the removed quota on Coldfront UI and cluster-side, but new allocations will not. Making any change to the quota attributes of prior allocations will remove the deleted quota from the cluster-side, but will still be visible on Coldfront UI.