What's a GlusterFest?
GlusterFest is a marathon to perform QA on release candidates before they're unleashed "in the wild."
The next GlusterFest begins:
- Thursday 13th February 2014 at midnight UTC/GMT (4pm Wednesday US Pacific time)
It ends at:
- Wednesday 19th of February 2014 at 23:59 UTC/GMT (3:59pm Wednesday US Pacific time)
For this GlusterFest, we will divide testing into two groups:
- Scale-out performance testing
- Feature testing
Scale-out Performance Testing
For scale-out operations and testing, we need to start by deploying GlusterFS. For the Gluster experienced, you can follow your own recipes, or use James Shubin's Puppet-Gluster module - https://forge.gluster.org/puppet-gluster/
Instructions for easy deploying with vagrant are here: https://ttboj.wordpress.com/2014/01/08/automatically-deploying-glusterfs-with-puppet-gluster-vagrant/
You'll probably want to read the three earlier articles to get comfortable with the process. Once you're comfortable, you'll wonder how you were ever able to get work done without this!
For Glusterfest specifics, read this article: https://ttboj.wordpress.com/2014/01/16/testing-glusterfs-during-glusterfest/
I'd recommend you try out a simple deploy with 3.4 at least once first. Let me know if you have any questions or problems. I'm purpleidea on irc.
Next, read Ben England's Performance_Testing page. Ben walks users through the use of iozone, a popular tool for filesystem benchmarking, and Smallfile, Ben's project for testing metadata intensive workloads, with particular emphasis on GlusterFS and other distributed filesystems.
Every major release has new features which have gone through a modicum of functional testing, but probably not on a great diversity of architectures. Look through the 3.5 feature page and test each feature.
Please join us for all the GlusterFest excitement, including:
- New features in 3.5
- Basic volume life cycle operations
- More advanced operations (adding and removing nodes, changing volume options)
Find a new bug that is confirmed by the Gluster QE team, and we'll send you a free t-shirt! (Please post your contact email and bugzilla #)
How to Get Started
For this upcoming GlusterFest we're using 3.5.0 beta1.
- Use the most up-to-date build or source tarball from http://gluster.org/download/ or the "release-3.5.0" branch in git.
- Step through test procedures (see below) - feel free to add your own to the list.
Post links to your testing results below.
For performance testing, iozone and smallfile output reports, some of which are quite lengthy. You may wish to post the full results on a separate wiki page and then link to it from here (or http://fpaste.org). If you are using an rpm based distribution, we would love to have the output of `sosreport -e infiniband` for your storage nodes. Otherwise, please provide the following with your test results:
- cat /proc/cpuinfo
- Memory size, NUMA yes/no, etc
For feature testing, run all the new features you can and report whether they worked. This can be reported on the grid below.
If you come across a bug, please report it on our bugzilla tracker, making sure to search to see if it has already been reported. Please include a link to your bug in your reports below.
Also, please be sure to send an email to the gluster-devel mailing list and include a link to your bugzilla ticket.
GlusterFS test cases
|User||Iozone link||Smallfile link||Bug reports|
|(my user name)||(iozone reults link)||(smallfile results link)||(bug report link)|
|User||AFR CLI||Expose Vol Capabilities||File Snapshots||gfid Access||Comp/ Decomp||No NFS Restart||Quota Scalability||readdir ahead||Zerofill||Brick Failure Detection||Disk Encrypt||Improved BD Xlator||Bug reports|
|(my user name)||y/n||y/n||y/n||y/n||y/n||y/n||y/n||y/n||y/n||y/n||y/n||y/n||y/n||(all bugzilla links)|