yosun

Now we are lack of using internal wiki page to solve problem. One of the reason is that we don't know if it contain the solution we need, and it's not convenient to search it manually in wiki page. It's much more slower than using google. In one group, we are most likely facing the same problem during work. So keeping the best solution, which we got from searching engine, in internal wiki is an efficiency way to collect standard workflow.

To say it's a review, it's better to say it's a good way to learn from others. I'll review test scripts in openQA project as much as I can, digest them and learn how to write Perl script more pretty. I'll make some notes for sharing.

Automation tools are our emotional friends. Know each other deeper and improve it, it's a way to be harmonious for our friendship.

We used trinity to make fuzzing test, but it hard to reproduce bugs. I'd like to try to use syzkaller or other fuzzy tools to find a stable process to reproduce fuzzy bugs.

Since sometime we have limited time to file a bug, especially during daily review of testsuites result. Then some bugs are lake of introduction about what the testsuite are tested, it makes developer take more time to debug this issue. I'd like to find a way to add some description in somewhere convenient to use, when file a kernel function bug.

• As a QA, we mostly thinking filesystem xfs in a researcher mind, some user scenes may not touch. Try to use xfs like a curious user in whole week, and touch features as much as possible, then find the feature which is important but don't cover in our daily work.

The result for xfstests in osd seems always red[1], but actually it's only a few test fail in a group(around 1/50). If we want to keep use openQA to handle those test, we need some enhancement for that. Try to enhancement test result to make it shows in a better way. - Make more reasonable group for those test

[motivation]

I plan to summary exist knowledge in filesystem part during hackweek. And learn some more feature about btrfs/xfs/ext4. The motivation is to speed up test result review in the future.

Project Description

I'm totally new in k8s, when I hear Rancher's product in all-hands I couldn't image what's that is. I'd like to take some time to learn some basic knowledge about k8s and Rancher's products.

Background

A dashboard for testing and analysis xfstests results just initial this year. It has a lot of performance issues to fix, and it also needed to add more features to get usable. Also bootstrap looks very easy to use, plan to learn some frontend knowledge for fun.

Project Description

Project Description

As shown in the kdevops frontpage in GitHub, "kdevops provides a framework for automation for optimal Linux kernel development and testing". It currently supports fstests, blktests, pynfs, selftests and so on.

Description

Recently, I became interested in NFS and want to learn more about it by reading related RFC files. However, there seem to be quite a lot of them. The goal is to glance at them and get a basic feel for the differences between each version.