v3.9.0

A minor release, released to mybrc.brc.berkeley.edu on February 22nd, 2024 and mylrc.lbl.gov on April 5th, 2024.

New Features

• (MyBRC only) Enabled users to download and upload MOU files for various request types:
  • Request types
    • New project requests for Instructional and Recharge allowances
    • Requests to purchase additional service units for Recharge allowances
    • Requests to create secure directories
  • PIs and requesters will be notified via email when an MOU is ready for signing. They will be directed to the website to download it, sign it, and then re-upload it.
  • Administrators may modify user responses used to generate MOUs and also have the ability to upload an MOU on a user's behalf.

Enhancements

• (MyBRC only) Updated request forms:
  • When requesting to create a secure directory, the user must provide a department.
  • When requesting an ICA, the user must provide the name and department of the course, as well as the name of a point of contact for the course.

v3.8.0

A minor release, released to mylrc.lbl.gov on February 13th, 2024.

Enhancements

• (MyLRC only) Added configuration for a new cluster named "hep".

v3.7.0

A minor release, released to mybrc.brc.berkeley.edu on February 6th, 2024.

Enhancements

• (MyBRC only) Added configuration for a new cluster named "sierra".

v3.6.3

A bug fix release, released to mybrc.brc.berkeley.edu and mylrc.lbl.gov on January 24th, 2024.

Enhancements

• Added a command correct_user_service_units that ensures that all project users of active projects have the same number of service units as the project itself.

Bug Fixes

• Corrected a bug in the processing logic for granting cluster access under a project that caused some database objects for tracking service units for a user to not be created in some cases.
• (MyLRC only) Updated the UI and CLI for listing billing IDs to exclude entries for users who have been denied access to or removed from a project.

v3.6.2

A bug fix release, released to mybrc.brc.berkeley.edu and mylrc.lbl.gov on December 14th, 2023.

Enhancements

• Updated the Ansible playbook to optionally configure a cron job to back up rotated application logs.

v3.6.1

A bug fix release, released to mybrc.brc.berkeley.edu and mylrc.lbl.gov on November 10th, 2023.

Enhancements

• Updated the Ansible playbook to configure logrotate to rotate application logs.

Bug Fixes

• (MyBRC only) Corrected a bug causing secure directory names to appear incorrectly.

v3.6.0

A minor release, released to mybrc.brc.berkeley.edu and mylrc.lbl.gov on September 27th, 2023.

New Features

• (MyLRC only) Added admin-accessible views for creating new billing IDs and updating billing IDs used by projects and users. Linked to these views from the existing admin-accessible view for searching for and listing billing IDs.

Enhancements

• Clarified that non-requester PIs of new project requests can request access separately after the request is processed.

v3.5.0

A minor release, released to mylrc.lbl.gov on August 29th, 2023.

New Features

• (MyLRC only) Added an admin-accessible view for searching for and listing usages of billing IDs.

Enhancements

• Allowed Service Units values allocated to individual computing allowances to differ per allowance period to support an increase for PCAs on MyLRC for the 2023 - 2024 fiscal year.
• Added Django admin pages for models that did not previously have them.

Bug Fixes

• Updated the Django admin page for users to prevent multiple email addresses from being selected as a user's primary one, and to run necessary handling when the primary changes.

v3.4.5

A patch release, released to mylrc.lbl.gov on August 15th, 2023.

Enhancements

• Updated the command for managing billing IDs to enable administrators to list billing IDs used by users and projects, or all usages of a particular billing ID.
• Updated the command for merging two user accounts to handle additional MyLRC-specific fields.

v3.4.4

A patch release, released to mybrc.brc.berkeley.edu on August 2nd, 2023.

Enhancements

• Added a command for merging two user accounts belonging to the same person into one.