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

Improve the fio package #124

Open
2 of 3 tasks
safl opened this issue Dec 12, 2024 · 2 comments
Open
2 of 3 tasks

Improve the fio package #124

safl opened this issue Dec 12, 2024 · 2 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@safl
Copy link
Collaborator

safl commented Dec 12, 2024

  • Add the cijoe fio package to package testing / verfication
  • Add example (config and workflow) showing how to run / use the fio wrapper
    • Consider simplifying it dramatically, it is currently very convoluted
    • Note: it must exercise the different ways that fio engines are handled e.g. builtin / external / etc.
  • Update documentation for the fio package
@safl safl added the enhancement New feature or request label Dec 12, 2024
@safl safl changed the title The Improve the fio package Dec 12, 2024
@safl safl added this to the v1.0.0 milestone Dec 12, 2024
@NaddiNadja
Copy link
Contributor

@safl as far as I can see, there are example workflows and configs for the fio package, added the same day as this issue was opened. Are these okay now that the fio package has been trimmed down or do we need to modify them?

Additionally, does the documentation need to cover more?

@safl
Copy link
Collaborator Author

safl commented Feb 6, 2025

@safl as far as I can see, there are example workflows and configs for the fio package, added the same day as this issue was opened. Are these okay now that the fio package has been trimmed down or do we need to modify them?

Additionally, does the documentation need to cover more?

If the example workflows and configs cover all scripts and modules, they are sufficient. Otherwise, additional content is needed. In general, coverage should include all scripts and modules, making the setup self-contained.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants