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

Implement the Bare Metal Usage invoice and processor #152

Open
QuanMPhm opened this issue Feb 25, 2025 · 2 comments · May be fixed by #154
Open

Implement the Bare Metal Usage invoice and processor #152

QuanMPhm opened this issue Feb 25, 2025 · 2 comments · May be fixed by #154
Assignees

Comments

@QuanMPhm
Copy link
Contributor

QuanMPhm commented Feb 25, 2025

As part of nerc-project/operations#831, we want to create an invoice that contains our Bare Metal usage. The invoice should have the following columns:

Many of the BM Usage columns will be empty but the ones below will be filled

  • Invoice Month is the previous month in this format "2024-10"
  • Project - Allocation
    • for example, ESI project "Noodles" becomes "Noodels BM Usage" links from
  • Project - Allocation ID becomes "ESI Bare Metal"
  • Manager (PI) comes from the Project Table above
  • Invoice Email is "[email protected]" for now
  • Institution comes from the Project Table above
  • Institution - Specific Code
  • SU Hours (GBhr or SUhr) comes from the summation we did above
  • SU Type
  • Rate comes from Server Types or nerc-rates whichever we decided to hold this info
  • Cost Rate * SU Hours
  • Credit
  • Credit Code
  • Balance Cost-Credit (which is zero so basically just cost again)

A sample table can be found here

@joachimweyl Let me know if any of our requirements change!

@QuanMPhm QuanMPhm self-assigned this Feb 25, 2025
@QuanMPhm
Copy link
Contributor Author

QuanMPhm commented Feb 26, 2025

@knikolla @naved001 As mentioned by @joachimweyl in the details of this invoice:

No BM is not eligible for any credits, that being said they might eventually have their own credits so we should make sure there is a way to enable disable credits for different types of "clusters" in this case we would call this "cluster" BM, but eventually, we might have different credits for ocp-test vs ocp-prod vs some other cluster, does it make sense to track this in a table? something like rates repo?

Currently we're filtering projects eligible for the New-PI credit with this cluttered function, should we plan anything on how to exclude projects in the future?

@QuanMPhm
Copy link
Contributor Author

@naved001 @knikolla Also, for now I will assume that we want to fill in the "unique values" for BM in an invoicing processor (i.e fill in "[email protected]" for Invoice Email) instead of during the invoice gathering phase like in openshift-usage-scripts. If you guys are fine with this decision, will I make a new BM processor

@QuanMPhm QuanMPhm changed the title Implement the Bare Metal Usage invoice Implement the Bare Metal Usage invoice and processor Feb 26, 2025
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 a pull request may close this issue.

1 participant