v3.25.1

A patch release, released to mybrc.brc.berkeley.edu on December 22nd, 2025.

Patches

• Updated how the amount of TBs associated with a Faculty Storage Allocation request is rendered in the list view and in the request hub:
  • The column name is now "Amount (TB)", not "Requested Amount (TB)".
  • The approved amount is rendered, if it is set. Otherwise, the requested amount is rendered.

v3.25.0

A minor release, released to mybrc.brc.berkeley.edu on December 15th, 2025.

New Features

• Added API endpoints for exposing users associated with a project, rooted at /api/projects/<pk>/users/.

Enhancements

• Updated the /api/projects/ API endpoint to:
  • Allow projects to be filtered by status and allowance type.
  • Return projects sorted by ID.

v4.3.0

A minor release, released to mylrc.lbl.gov on December 15th, 2025.

New Features

• Added API endpoints for exposing users associated with a project, rooted at /api/projects/<pk>/users/.

Enhancements

• Updated the /api/projects/ API endpoint to:
  • Allow projects to be filtered by status and allowance type.
  • Return projects sorted by ID.

Patches

• Updated the Ansible playbook to conditionally install and configure OpenDKIM.

v4.2.1

A patch release, released to mylrc.lbl.gov on November 19th, 2025.

Patches

• Updated how service units are rendered in the user interface:
  • Standalone cluster projects now show "Unlimited" instead of 100 million.
  • Condo projects now show "Unlimited" instead of 100 million.
  • (MyLRC only) Recharge projects now show "Usage-based" instead of 100 million.
  • The "Service Units" gauge on the Allocation Detail view now only appears when there is a non-zero, finite amount of service units allocated.

v3.24.2

A patch release, released to mybrc.brc.berkeley.edu on November 19th, 2025.

Patches

• Updated how service units are rendered in the user interface:
  • Standalone cluster projects now show "Unlimited" instead of 100 million.
  • Condo projects now show "Unlimited" instead of 100 million.
  • (MyLRC only) Recharge projects now show "Usage-based" instead of 100 million.
  • The "Service Units" gauge on the Allocation Detail view now only appears when there is a non-zero, finite amount of service units allocated.
• Fixed a bug causing the Project Detail view to raise an error for standalone cluster projects when the FSA plugin is enabled.

v3.24.1

A patch release, released to mybrc.brc.berkeley.edu on November 11th, 2025.

Patches

• Corrected a bug in which users removed from a project were not also removed from any associated Faculty Storage Allocation.

v4.2.0

A minor release, released to mylrc.lbl.gov on November 6th, 2025.

Enhancements

• Moved "Manage Project" buttons on the Project detail view (e.g., "Update Project Information", "Request a Secure Directory", "Archive Project", etc.) under an "Actions" dropdown.

Patches

• Added a test that ensures that, when a PI User is created as part of a new project request, they are created with is_active.

v3.24.0

A minor release, released to mybrc.brc.berkeley.edu on November 6th, 2025.

New Features

• (MyBRC only) Enabled PIs of FCAs to request a Faculty Storage Allocation (FSA), consisting of 1 - 5 TB of cluster storage per eligible faculty member, tied to their FCA project.
  • On the project detail view for FCAs, PIs and managers may click a "Request Faculty Storage Allocation" button. They select the PI and the amount of storage desired.
  • On the Request Hub, users may view their pending and completed requests.
  • Administrators review and process the requests.
  • Storage may be pooled between the PIs of an FCA. There is currently no support for un-pooling.
  • There are API endpoints for automating storage provisioning.
  • Initially, this functionality is only available to a whitelist of faculty members as part of a pilot program.

Enhancements

• Moved "Manage Project" buttons on the Project detail view (e.g., "Update Project Information", "Request a Secure Directory", "Archive Project", etc.) under an "Actions" dropdown.

Patches

• Added a test that ensures that, when a PI User is created as part of a new project request, they are created with is_active.

v4.1.1

A patch release, released to mylrc.lbl.gov on September 12th, 2025.

Patches

• Upgraded Django to 5.2.6 to address CVE-2025-57833.

v4.1.0

A minor release, released to mylrc.lbl.gov on September 8th, 2025.

Enhancements

• Added a command for sending an email to PIs and managers of currently-active yearly computing allowance projects (FCAs on MyLRC, PCAs on MyBRC), notifying them that renewals for the next allowance year are available.
• (MyLRC only) Updated the views for requesting computing allowance renewals to (a) ask for an updated LBL Project ID if the project's current one is invalid and the selected PI is already a PI of the project, and (b) update the PID for the project and associated users to the provided one.