-
Notifications
You must be signed in to change notification settings - Fork 56
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
Added functionality for creating and processing archive file #279
Added functionality for creating and processing archive file #279
Conversation
@acalhounRH can you make it so the archive file location and possibly name can be set? |
e5fa327
to
c0de90f
Compare
Sure thing I used the --archive-file=<path to file/filename> and the user can provide a full path to file, it will default to cwd and user_cluster_uuid.archive. @dry923 python3.7 ~/git/benchmark-wrapper/snafu/run_snafu.py --tool sysbench -f /home/acalhoun/sysbench_results/example_cpu_test.conf --create-archive --archive-file ./alc-test.archive |
2269dc3
to
cddbad3
Compare
220fb5f
to
d576e60
Compare
/rerun all |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor nit, but can we add a test to archive then check if the archive is present?
No testing within benchmark-wrapper, would this request be a follow on activity for benchmark-operator? |
@acalhounRH can you update the Readme for this as well? |
bah-humbug... |
Results for SNAFU CI Test
|
1352fe4
to
228e43d
Compare
7322051
to
d7d70d3
Compare
d28a13a
to
1ef1f69
Compare
Results for SNAFU CI Test
|
baddeb6
to
5ea73e9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM pending the last CI passing.
Results for SNAFU CI Test
|
README.md
Outdated
Note: SNAFU does not depend upon Kubernetes, so you can use run_snafu.py on a bare-metal or VM cluster without relying | ||
on Kubernetes to start/stop pods. So if you need your benchmark to collect data for both Kubernetes and non-Kubernetes | ||
environments, develop in SNAFU and then write benchmark-operator benchmark to integrate with Kubernetes. | ||
** Why Should I use Benchmark-wrapper? ** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you expect some formatting like h2 with this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was expecting Bold
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah, i don't think it worked.
2095b8e
to
ff296a9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
!!! Couldn't read commit file !!! |
Description
added functionality to create and re-index a archive file for benchmark-wrapper
when creating an archive we would just include --create-archive on any run and it will drop a
user_clustername_uuid.archive
file in the cwdfor example
python3.7 ~/git/benchmark-wrapper/snafu/run_snafu.py --tool sysbench -f /home/acalhoun/sysbench_results/example_cpu_test.conf --create-archive
when indexing from an archive we would do,
run_snafu --tool archive --archive-file <file>
. run_snafu will go straight to processing and indexing the listed ES friendly documents in the archive.For example
python3.7 ~/git/benchmark-wrapper/snafu/run_snafu.py --tool archive --archive-file myuser_mycluster_1b88311d-1230-409a-9ffa-94e6f9aa4754.archive -v
@jtaleric @dry923
Fixes