From Fedora Project Wiki

Revision as of 13:27, 14 June 2013 by Peter (talk | contribs) (Added missing category)

Fedora Test Days
}}}
HekaFS

Date 2011-10-20
Time all day

Website HekaFS page
IRC #fedora-test-day (webirc)
Mailing list test


Note.png
Can't make the date?
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.

What to test?

This page is for testing HekaFS (Features/HekaFS).

Who's available

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:

glusterfs-3.2.4-1.fc16
hekafs-0.7-15.fc16

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 four node HekaFS cluster and HekaFS clients. Remember to open the necessary ports in the cluster nodes firewalls.

If using guest VMs, add any additional storage devices to your VM as necessary. The tests are written assuming that the storage devices are /dev/sda, /dev/sdb, etc, and mounted at /bricks/sda, /bricks/sdb, etc., respectively.

Start the glusterd and hekafsd daemons on each server node with the following commands:

 service glusterd start
 service hekafsd start

Testing

Note.png
Assumptions in the test cases
The test cases are written with assumptions about the IP addresses of the various nodes and the block devices used for storage. If you use different IP addresses and/or have different storage it will be necessary to change some of the commands to match your setup.
Note.png
Run the tests in order
Test 2 continues where test 1 left off, and test 3 continues where test 2 left off.


Follow each of these test cases:

  1. QA:Testcase_HekaFS - default (distributed)
  2. QA:Testcase_HekaFS_replicated - replicated
  3. QA:Testcase_HekaFS_striped - striped
Note.png
Report SELinux denials against HekaFS
If you encounter some SELinux (AVC) denials during testing, please report them against the hekafs package, not selinux package. Thanks.

Test Results

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
Sample User
Pass pass
Warning warn
[1]
Fail fail
[2]
  1. Test pass, but also encountered RHBZ #54321
  2. RHBZ #12345
Kaleb
Pass pass
Pass pass
Pass pass