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

Document pricing for bare metal machines in NERC user guides #1272

Open
3 tasks done
msdisme opened this issue Mar 13, 2024 · 13 comments · May be fixed by nerc-project/nerc-docs#235
Open
3 tasks done

Document pricing for bare metal machines in NERC user guides #1272

msdisme opened this issue Mar 13, 2024 · 13 comments · May be fixed by nerc-project/nerc-docs#235
Assignees

Comments

@msdisme
Copy link

msdisme commented Mar 13, 2024

Motivation

We require pricing for bare metal machines so that we can start to include bare metal in our offerings.

Completion Criteria

A pricing guide for bare metal.

Description

Pricing

H100 - $24.16
A100SXM - $8.312
FC830 - $3.97
FC430 - $0.75

Old Hardware Pricing (if we ever move it to BM)

A100 - $7.212
V100 - $1.214
K80 - $1.852

Bare Metal

Name vGPU vCPU RAM (GiB) Current Price
H100 GPU 4 256 1,536 $24.16
A100sxm4 GPU 4 128 1,024 $8.312
FC830 0 176 2,048 $3.97
FC430 0 40 128 $0.75

BM SU Example:

  • Project with 1 H100, 1 A100SXM4, 2 FC830s, and 3 FC430s:
    • 1 H100 Server, 720hrs (24hr*30days)
    • 1 A100SXM4 Server, 720hrs (24hr*30days)
    • 2 FC830 Servers, 720hrs (24hr*30days)
    • 3 FC430 Servers, 720hrs (24hr*30days)
  • Project Will be charged:
    • 1 H100 SU * 720hrs * $24.16 = $17,395.20
    • 1 A100SXM4 * 720hrs * $8.312 = $5,984.64
    • 2 FC830 SU * 720hrs * $3.97 = $5,716.80
    • 3 FC430 SU * 720hrs * $0.75 = $1,620.00
    • = $30,716.64

Notes

  • Include examples of what it would cost for 3 FC430s, 2 FC830s, 1 A100SXM4 & 1 H100
  • Include what each BM machine includes
  • This should be on a separate page which Heidi may reference but which is not widely promoted
  • The page needs to have disclosures that the prices are introductory and are likely to change
  • The page needs to include a notice that bare metal pricing options are currently a limited offering and a request that interested parties send details on how/why they want to do this so we may consider it for future implementation.

Completion dates

Desired - 2024-04-17
Required - 2024-12-04

@joachimweyl
Copy link
Contributor

This has been updated to remove FC430 with 96 GB of RAM since they will not be leased out as they are currently used by OCT.

@joachimweyl
Copy link
Contributor

@Milstein how can I be helpful in getting the first version ready? RH is already requesting this.

@joachimweyl
Copy link
Contributor

@msdisme are we going to do any old A100 or V100 Bare Metal leasing or are those going to stay in OpenShift & OpenStack?

@msdisme
Copy link
Author

msdisme commented Nov 21, 2024

Not for the examples—and we need to stress them as illustrative. This also needs to get reviewed by @neclinton and @waygil before pushed live. I also added a bullet above—this is not currently generally available. If interested, we would like to hear more about your use case so we may consider it for future implementation.

@Milstein
Copy link

Milstein commented Dec 2, 2024

I will be working on this week if the SU cost is confirmed.

@joachimweyl : can we create a google docs on NERC to track this

@joachimweyl
Copy link
Contributor

@Milstein are you suggesting a google doc so that we can control who has access?

@Milstein
Copy link

Milstein commented Dec 2, 2024

@joachimweyl: just for the content for the NERC documentation pages like we had for other billing info. Or we can re-use the same doc with separate section for BM.

@joachimweyl
Copy link
Contributor

@Milstein I added an example to the description.

@joachimweyl
Copy link
Contributor

@Milstein please let me know when this is done so I can review it.

@joachimweyl
Copy link
Contributor

@Milstein anything I can do to help with this?

@Milstein
Copy link

Milstein commented Jan 8, 2025

@msdisme @joachimweyl : we also might need outline how the reservation for the user request is done and how the user will be able to use the resources?

@joachimweyl
Copy link
Contributor

@Milstein my understanding is that this was a request by RH to get pricing up so that they have a guide for early usage. We are not ready to have other users using this until we have Automated BM billing in place. For now let's just get the pricing up. Later we can provide documentation of how a user would go about doing this.
@msdisme thoughts?

@Milstein Milstein linked a pull request Jan 8, 2025 that will close this issue
@msdisme
Copy link
Author

msdisme commented Jan 8, 2025

@msdisme @joachimweyl : we also might need outline how the reservation for the user request is done and how the user will be able to use the resources?

These details specifics are documented here: https://esi.readthedocs.io/en/latest/ We should probably link to those in the doc. Path is via mghpcc regapp so that we have a way to bill etc.

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.

3 participants