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
First draft of firefly-giant-x suite #135
Conversation
Signed-off-by: Yuri Weinstein <yuri.weinstein@inktank.com>
log-whitelist: | ||
- scrub mismatch | ||
- ScrubResult | ||
roles: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be good to have more OSDs ( 15 maybe ) to test the LRC erasure code plugin which needs at least 8 of them.
@dachary do you think it should be specific to this suite? |
@yuriw I think it should be for all suites for which we want to run a lrc workload, meaning all suites including giant I suppose |
It's fine to add lots of OSDs, but it will get slow because they will stop being mapped to actual disks (and will live on / instead). I don't think we should do that for the generic tests. Instead, we should make a EC specific collection of tests for these cases that need lots of OSDs ... |
@liewegas "a EC specific collection of tests" you mean add special suites for this? |
or a subdir with just the lrc stuff. Not sure where best to slot it in for upgrade, but for the rados suite, i think we need a rados/ec/ collection. |
This suite should be added at later time when we have cleaned up giant branch and have other suites in "green" state per chat with Sage. |
First draft of firefly-giant-x suite
looks fine to me |
1 similar comment
looks fine to me |
@tmuthamizhan looks merged to me, thx! |
@liewegas pls review and merge
Signed-off-by: Yuri Weinstein yuri.weinstein@inktank.com