|Fedora Test Days|
What to test?
This page is for testing HekaFS (Features/HekaFS).
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Development - Jeff Darcy (jdarcy), Kaleb KEITHLEY (kkeithley), Edward Shishken
- Quality Assurance - ???
Prerequisite for Test Day
- Several machines, physical or virtual, for servers
- Sufficient disk space on the servers to use as back-end storage
- One or more machines, physical or virtual, for client(s)
- An updated Fedora 16 beta
How to test?
Update your machine
If you're running Fedora 16, make sure you have all the current updates for it installed, using the update manager.
Get latest glusterfs and hekafs packages
The latest versions are:
Use the following command to install all server nodes:
yum -y install glusterfs glusterfs-server glusterfs-fuse hekafs
On the client, user the following command to install:
yum -y install glusterfs glusterfs-fuse hekafs
See HekaFS simple howto for an overview of setting up of a simple four node HekaFS cluster.
If using guest VMs, add any additional storage devices as necessary.
Start the glusterd and hekafsd daemons on each server node with the following commands:
service glusterd start service hekafsd start
Follow each of these test cases:
- QA:Testcase_HekaFS - simple
If you have problems with any of the tests, report a bug to Bugzilla usually for the component hekafs. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you. Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one. For each test case, use the result template to enter your result, as shown in the example result line.
HekaFS test cases
|User||test 1||test 2||test 3||References|