-
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
Adding log generator script and container file #254
Conversation
Can one of the admins verify this patch? |
I like the idea of having this part of snafu/benchmark-wrapper, here are some more ideas for this work -
|
7742a7c
to
5cd571c
Compare
6d7fb4f
to
89b943d
Compare
@chaitanyaenr @jtaleric @rsevilla87 out of draft and good to review please. |
self._wait_for_pods(my_redis,channel) | ||
|
||
timestamp = time.strftime("%Y-%m-%dT%H:%M:%S") | ||
start_time = time.time() |
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.
Maybe it's better to use datetime.datetime.now() ?, I'm suggesting this because this way you can subtract dates natively (w/o converting them to epoch)
start_time = datetime.datetime.now()
message_count = self._run_log_test()
end_time = datetime.datetime.now()
elapsed_time = (end_time - start_time).total_seconds()
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.
@rsevilla87 fair point. It functionally works out the same though in terms of the end result. I'll play around with it after the demo today since I don't want to break it prior :-D
/rerun all |
@dry923 I wonder if we should execute all pod synchronization from here rather than benchmark-operator. Looking at other more complex cases like uperf I think we should standardize the place where we perform this kind of operations. |
Results for SNAFU CI Test
|
@rsevilla87 updated the operator PR to include managing the syncing of the pods (see: https://github.com/dry923/ripsaw/blob/da1b75beafd66f0b9265bdaca97118923fc31c8c/roles/log_generator/templates/log_generator.yml#L75). Do you think its worth leaving the code in here as well in case it is used outside the operator? |
openshift and kubernetes version
@rsevilla87 removed code from the wrapper |
Results for SNAFU CI Test
|
5c3d7c6
to
04de932
Compare
/rerun all |
Results for SNAFU CI Test
|
/rerun all |
Results for SNAFU CI Test
|
Results for SNAFU CI Test
|
/rerun all |
Results for SNAFU CI Test
|
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!
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!
Depends-On: 545
Description
Adding a log generator workload that will generate X messages of Y size (in bytes) per second/minute over a duration of Z minutes. If provided it will also check the backed log aggregator to confirm it received the expected number of messages. Supported backends are elasticsearch and AWS cloudwatch.
NOTE: This requires a backend storage to be deployed if we want to create a valid ci test for this.
benchmark-operator PR: cloud-bulldozer/benchmark-operator#545