Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Auto Approving Allocation Requests Requirements Gathering #949

Open
2 tasks
knikolla opened this issue Feb 26, 2025 · 2 comments
Open
2 tasks

Auto Approving Allocation Requests Requirements Gathering #949

knikolla opened this issue Feb 26, 2025 · 2 comments
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@knikolla
Copy link

knikolla commented Feb 26, 2025

Motivation

Currently, NERC admins have to approve every allocation request and increase in quotas for those allocation requests.

As we grow, and our resources are no longer as limited that they require an admin to hand-count things, we can automate the process of automatically approving "some" things.

For example

  • A PI that is in good standing and already has several resource allocations that we have been billing them for a while, and is requesting a new allocation that does not involve any GPU resources may not require manual approval.
  • A PI wants to decrease their quota values in their resource allocation. (I am going to implement this anyway, try stopping me)

Completion Criteria

Decision Flowchart is written and has received approval on what qualifies a new allocation request or allocation change request for auto approval.
This may be based on characteristics of the request, the user, etc.

Description

  • First pass
  • Approval

Completion dates

Desired - 2024-03-31
Required - TBD

@joachimweyl joachimweyl changed the title Gather requirements on deciding policy and process for auto approving allocation requests Auto Approving Allocation Requests Requirements Gathering Feb 26, 2025
@joachimweyl joachimweyl added the documentation Improvements or additions to documentation label Feb 26, 2025
@joachimweyl
Copy link
Contributor

@syockel ^

@knikolla
Copy link
Author

Just brainstorming something I thought about.

One use case that this enables is the possibility of trial resource allocations. For example auto approving a PI's very first resource allocation request with an initial expiration time of 1 month.

In the billing code, we're applying a new PI credit for new PIs in their first 2 months. This often leads to new PIs having charges of $0 while they get started. We could auto approve allocations whose quota is guaranteed to keep PIs below the margin of being charged.

This allows someone to really quickly start using the NERC for the first time and we could easily move the resource allocation's expiration time once we've reached out to the PI and confirmed their continued usage and ability to be charged.

@msdisme ^^

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

4 participants