Skip to content

Update coldfront-plugin-cloud to 0.12.0#196

Merged
jtriley merged 1 commit intonerc-project:mainfrom
QuanMPhm:staging-0.12.0
Mar 9, 2026
Merged

Update coldfront-plugin-cloud to 0.12.0#196
jtriley merged 1 commit intonerc-project:mainfrom
QuanMPhm:staging-0.12.0

Conversation

@QuanMPhm
Copy link
Contributor

@QuanMPhm QuanMPhm commented Mar 5, 2026

The migration steps largely involve testing the new dynamic quotas feature (nerc-project/coldfront-plugin-cloud#287):

  • Run validate_allocations before 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 expect validate_allocations to display any new warnings/errors
  • Run coldfront register_cloud_attributes
  • Run register_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.
  • Check log messages to see that quotas have been correctly added to all Openshift and Openstack resources
  • Run validate_allocations.py again. No new quota-related warnings should pop-up
  • Go to admin dashboard, check that all resources now have a new attribute Available Quota Resources, which contains a long json string. This JSON string should list all quotas for that resource
  • This JSON string is visible to users when they inspect the resource on the Coldfront UI (error in hindsight by me, apologies), in case you want this attribute hidden
  • Make an allocation for Openshift and Openstack, with different quantities, and check that quotas are correctly created
  • Check that new Openshift allocations don't have modelmesh-enabled label defined in their namespace (More details in Removes modelmesh-enabled label coldfront-plugin-cloud#291)
  • Test add_quota_to_resource by 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-side
  • Test remove_quota_from_resource by 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.

@jtriley jtriley merged commit df05e2c into nerc-project:main Mar 9, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants