Create Module for All-to-All Network Tests
- Dominant language
- Python
- Stars
- 307
- Forks
- 151
- Avg merge
- 14d 23h
- Merged PRs (30d)
- 1
Description
Use iperf for all-to-all network tests. Base code on somthing vaguely like:
Client to OSD tests:
# !/bin/bash
for i in 8 9 10 11 12 13
do
val=$((62+$i))
pdsh -R ssh -w osd[$i] iperf -s -B 172.27.50.$val &
done
# !/bin/bash
for i in 0 1 2 3 4 5 6 7
do
for val in 70 71 72 73 74 75
do
pdsh -R ssh -w client[$i] iperf -c 172.27.50.$val -f m -t 60 -P 1 > /tmp/iperf_client${i}_to_${val}.out &
done
done
# !/bin/bash
for i in 8 9 10 11 12 13
do
val=$((62+$i))
pdsh -R ssh -w osd[$i] iperf -s -B 172.27.49.$val &
done
# !/bin/bash
for i in 8 9 10 11 12 13
do
for val in 70 71 72 73 74 75
do
pdsh -R ssh -w osd[$i] iperf -c 172.27.49.$val -P 1 -f m -t 60 -P 1 > /tmp/iperf_${i}_to_${val}.out &
done
done
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue provides Bash examples using iperf and pdsh but names no target module, existing entry point, or tests. Start by inspecting the repository's current benchmark modules and test layout, then define how the client-to-OSD and OSD-to-OSD all-to-all runs should be represented; done means the module executes those test combinations and records their output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash, python
- Domain
- networking, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100