openshift / openshift/network-tools
Regarding use-case of the tools
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 34
- Forks
- 63
- PR merge metrics
- No merged PRs in 30d
Description
I have noted the Gathering logs is not in the scope of these scripts and are better suited on the openshift/must-gather image quote from the README and have questions about when to / when to not use this repo for tools.
I can see that there are a number of scripts that perform tests on the current state of the network, similar to sanity checks or unit-tests on the network. I do not see tools that collect information for further debug, such as collecting PCAPs or running / collecting iPerf output.
Is this the appropriate place for writing these kinds of tools or is it intended for this repo to contain only smoke-tests and pass/fail tests on the network?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the README's scope statement and the existing network-test scripts, then compare them with the proposed PCAP and iPerf collection use cases. Done would require a maintainer decision and documented scope before implementation can be defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100