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.

Sign up for GitHub

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

Jump to bottom

Auto-Provisioning Benchmark Hardware #103

Open
stanbrub opened this issue May 11, 2023 · 0 comments
Open

Auto-Provisioning Benchmark Hardware #103

stanbrub opened this issue May 11, 2023 · 0 comments
Assignees
@stanbrub
Labels
enhancement New feature or request

Comments

@stanbrub
Copy link
Collaborator

stanbrub commented May 11, 2023 •
edited

Currently, we manually provision a benchmark server and use it over and over again from the github workflows. This provides consistency between runs. However, there needs to be a way to provision bare metal as needed.

  • Provide a way to provision a new server from a Github workflow with secrets
  • Do we provision a new server each test run? That doesn't sound like apples-to-apples for comparison
  • Do we just have an workflow to do the provisioning without anything more?
  • How do we deal with the IP address of the provisioned server. We currently have a hardcoded DH secret
  • Google Doc For More Details
@stanbrub stanbrub added the enhancement New feature or request label May 11, 2023
@stanbrub stanbrub changed the title Provisioning Benchmark Hardware Auto-Provisioning Benchmark Hardware Nov 10, 2023
@stanbrub stanbrub mentioned this issue Nov 10, 2023
Open
@stanbrub stanbrub mentioned this issue Jul 12, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@stanbrub stanbrub

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@stanbrub