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

[testing-on-gke part 0.1] Add original fio/dlio load-testing code from gcs-fuse-csi-driver #2247

Conversation

gargnitingoogle
Copy link
Collaborator

@gargnitingoogle gargnitingoogle commented Jul 31, 2024

Description

This adds relevant files from fio/, dio/ and utils/ directories from https://github.com/GoogleCloudPlatform/gcs-fuse-csi-driver/tree/main/examples for planned fio/dlio testing in gcsfuse on gke.
These contain resources needed to create GKE pods for fio/dlio testing for gcsfuse mounts.

This is a first in a series of PRs. The later PRs will focus on the following

  1. Adding an end-2-end script to use the above resources and scripts to run the fio/dlio tests, and according changes in these scripts themselves.
  2. Adding parameters in the e2e script to control various configurable properties such as cluster/node configurations, gcsfuse mount options, workload configurations, monitoring/debugging controls etc.

This is followed up in #2284 .

Link to the issue in case of a bug fix.

NA

Testing details

  1. Manual - yes, tested manually, am able to use these pod resources and scripts in testing.
  2. Unit tests - NA
  3. Integration tests - NA

Copy link

codecov bot commented Jul 31, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 72.20%. Comparing base (7005fb0) to head (d1dfaac).
Report is 9 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #2247      +/-   ##
==========================================
+ Coverage   71.47%   72.20%   +0.73%     
==========================================
  Files         106      106              
  Lines       11505    12294     +789     
==========================================
+ Hits         8223     8877     +654     
- Misses       2937     3048     +111     
- Partials      345      369      +24     
Flag Coverage Δ
unittests 72.20% <ø> (+0.73%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@gargnitingoogle gargnitingoogle marked this pull request as ready for review July 31, 2024 11:03
@gargnitingoogle gargnitingoogle requested a review from a team as a code owner July 31, 2024 11:03
@kislaykishore kislaykishore requested review from a team and kislaykishore and removed request for a team July 31, 2024 11:03
@gargnitingoogle gargnitingoogle force-pushed the garnitin/add-gke-load-testing/add-origin-csi-driver-code/v1 branch 2 times, most recently from 8ef223d to b2edd59 Compare August 2, 2024 04:41
@gargnitingoogle gargnitingoogle changed the title Add original fio/dlio load-testing code from gcs-fuse-csi-driver [testing-on-gke part 0] Add original fio/dlio load-testing code from gcs-fuse-csi-driver Aug 2, 2024
@gargnitingoogle gargnitingoogle changed the title [testing-on-gke part 0] Add original fio/dlio load-testing code from gcs-fuse-csi-driver [testing-on-gke part 0.1] Add original fio/dlio load-testing code from gcs-fuse-csi-driver Aug 5, 2024
@gargnitingoogle gargnitingoogle force-pushed the garnitin/add-gke-load-testing/add-origin-csi-driver-code/v1 branch 2 times, most recently from 26b4eb2 to c0be808 Compare August 6, 2024 10:30
@gargnitingoogle gargnitingoogle force-pushed the garnitin/add-gke-load-testing/add-origin-csi-driver-code/v1 branch from d1dfaac to e84c668 Compare August 7, 2024 11:29
@gargnitingoogle gargnitingoogle merged commit f7085fb into master Aug 8, 2024
11 checks passed
@gargnitingoogle gargnitingoogle deleted the garnitin/add-gke-load-testing/add-origin-csi-driver-code/v1 branch August 8, 2024 09:04
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 this pull request may close these issues.

2 participants