search

cloud-bulldozer / benchmark-operator

The Chuck Norris of cloud benchmarks
Apache License 2.0
282 stars 127 forks source link

Use uperf pod antiAffinity rules #781

Closed rsevilla87 closed 2 years ago

rsevilla87 commented 2 years ago

Use podAntiaffinity rules to place uperf client pods in different worker nodes where the servers are running on

Use podAffinity rules to place all client and server pods in the same node, useful when running more than one pair All client pods will be scheduled in the same node and servers in another

Signed-off-by: Raul Sevilla rsevilla@redhat.com

codecov-commenter commented 2 years ago

Codecov Report

Merging #781 (5cf3aa3) into master (94005cd) will not change coverage. The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #781   +/-   ##
=======================================
  Coverage   53.47%   53.47%           
=======================================
  Files           8        8           
  Lines         331      331           
=======================================
  Hits          177      177           
  Misses        154      154
Flag Coverage Δ
gha 53.47% <ø> (ø)
python-3.9 53.47% <ø> (ø)
unit 53.47% <ø> (ø)

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

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update 18bb2d1...5cf3aa3. Read the comment docs.

stale[bot] commented 2 years ago

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.