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

Add new workload outside of the benchmark-runner tree #384

Open
RobertKrawitz opened this issue Mar 1, 2022 · 4 comments
Open

Add new workload outside of the benchmark-runner tree #384

RobertKrawitz opened this issue Mar 1, 2022 · 4 comments

Comments

@RobertKrawitz
Copy link
Member

Is your feature request related to a problem? Please describe.
I would like to run a workload with the benchmark-runner framework without making any changes to the benchmark-runner tree or mounting anything on top of the tree.

Describe the solution you'd like
Load a python module (from a path that I could specify in environment/command line) that contains all of the resources necessary to run the benchmark, including all templates and code necessary to implement the benchmark.

@ebattat
Copy link
Collaborator

ebattat commented Jun 20, 2022

@RobertKrawitz, can you please specify or give an example for this problem?

@RobertKrawitz
Copy link
Member Author

I don't have a specific use case at the moment, so this isn't high priority. What I envision is that I want to run an existing benchmark using the benchmark-runner framework, but I want to specify that on the command line or environment variable without actually having to make any change to benchmark-runner.

@ebattat
Copy link
Collaborator

ebattat commented Jun 21, 2023

@RobertKrawitz, do you mean to the option to run workloads as clusterbuster ?

@RobertKrawitz
Copy link
Member Author

I mean the ability to run workloads without having to make any changes at all inside the benchmark-runner repository, something like pluggable modules that are dynamically loaded at runtime.

@ebattat ebattat added this to To do in benchmark-runner via automation Jun 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

2 participants