From Fedora Project Wiki
(Created page with "{{QA/Test_Case |description=This test case tests the functionality of the HekaFS feature. |actions= # Open web browser to server node1, port 8080 (e.g. http:/...") |
mNo edit summary |
||
(4 intermediate revisions by the same user not shown) | |||
Line 2: | Line 2: | ||
|description=This test case tests the functionality of the [[Features/HekaFS|HekaFS]] feature. | |description=This test case tests the functionality of the [[Features/HekaFS|HekaFS]] feature. | ||
|actions= | |actions= | ||
Run your web browser of choice: | |||
# Open web browser to server node1, port 8080 (e.g. http://192.168.122.21:8080) | # Open web browser to server node1, port 8080 (e.g. http://192.168.122.21:8080) | ||
In the web browser, add servers to the cluster: | |||
# Click on the Manage Servers link | # Click on the Manage Servers link | ||
# Notice that server node 1 is listed as a Cluster Node | # Notice that server node 1 (192.168.122.21) is already listed as a Cluster Node | ||
# Add one or more additional nodes: | # Add one or more additional nodes: | ||
## Enter 192.168.122.22 and press the Add button | ## Enter 192.168.122.22 and press the Add button | ||
Line 11: | Line 17: | ||
## repeat for additional server nodes | ## repeat for additional server nodes | ||
# Press the Done button | # Press the Done button | ||
Provision a volume in the cluster: | |||
# Click on the Manage Volumes link | # Click on the Manage Volumes link | ||
# Check the check-boxes for /bricks/sda on all server nodes | # Check the check-boxes for /bricks/sda on all server nodes | ||
Line 20: | Line 29: | ||
# Notice that the check-boxes for bricks/sda are insensitive (grayed out) | # Notice that the check-boxes for bricks/sda are insensitive (grayed out) | ||
# Press the Done button | # Press the Done button | ||
Create a tenant for the volume: | |||
# Click on the Manage Tenants link | # Click on the Manage Tenants link | ||
# Enter yoyodyne, bigboote, 10000, 10999, 10000, 10999 in the Name, Password, UID Range Low, UID Range High, GID Range Low, and GID Range High fields. | # Enter yoyodyne, bigboote, 10000, 10999, 10000, 10999 in the Name, Password, UID Range Low, UID Range High, GID Range Low, and GID Range High fields. | ||
Line 25: | Line 37: | ||
# Notice that yoyodyne is successfully added | # Notice that yoyodyne is successfully added | ||
# Click on the Back to tenant configuration link | # Click on the Back to tenant configuration link | ||
Enable the volume for the tenant: | |||
# Click on the yoyodyne volumes link | |||
# Click the Enabled check-box for testsda | |||
# Press the Update button | |||
# Notice that the volume is successfully enabled for the tenant | |||
# Click the Back to tenant configuration link | |||
# Press the Done button | # Press the Done button | ||
Start the volume: | |||
# Click on the Manage Volumes link | # Click on the Manage Volumes link | ||
# Click on the testsda start link | # Click on the testsda start link | ||
# Notice that testsda is successfully started | # Notice that testsda is successfully started | ||
In a shell on the client, mount the volume: | |||
# enter `mkdir /mnt/testsda` | |||
# enter `hfs_mount 192.168.122.21 yoyodyne bigboote /mnt/testsda` | |||
# enter `df` or `mount` | |||
# Notice that /mnt/testsda was successfully mounted | |||
Work-around for BZ 747112. In a shell on each server node, fix directory permissions: | |||
# enter `chmod 01777 /bricks/sda/yoyodyne` | |||
In a shell on the client, initiate I/O: | |||
# Perform I/O on the mounted volume, e.g. touch, cp, rm, ln, ln -s, mkdir, rmdir, ls, etc. | |||
|results= | |results= | ||
# | # files and directories are variously created, deleted, etc. | ||
}} | }} |
Latest revision as of 12:03, 20 October 2011
Description
This test case tests the functionality of the HekaFS feature.
How to test
Run your web browser of choice:
- Open web browser to server node1, port 8080 (e.g. http://192.168.122.21:8080)
In the web browser, add servers to the cluster:
- Click on the Manage Servers link
- Notice that server node 1 (192.168.122.21) is already listed as a Cluster Node
- Add one or more additional nodes:
- Enter 192.168.122.22 and press the Add button
- Notice that 192.168.122.22 is successfully added
- Click on the Back to cluster configuration link
- repeat for additional server nodes
- Press the Done button
Provision a volume in the cluster:
- Click on the Manage Volumes link
- Check the check-boxes for /bricks/sda on all server nodes
- Leave the Replica or Stripe count box empty.
- Enter testsda in the Volume ID box
- Press the Provision button
- Notice that the volume has been successfully provisioned
- Click the Back to volume configuration link
- Notice that the check-boxes for bricks/sda are insensitive (grayed out)
- Press the Done button
Create a tenant for the volume:
- Click on the Manage Tenants link
- Enter yoyodyne, bigboote, 10000, 10999, 10000, 10999 in the Name, Password, UID Range Low, UID Range High, GID Range Low, and GID Range High fields.
- Press the Add button
- Notice that yoyodyne is successfully added
- Click on the Back to tenant configuration link
Enable the volume for the tenant:
- Click on the yoyodyne volumes link
- Click the Enabled check-box for testsda
- Press the Update button
- Notice that the volume is successfully enabled for the tenant
- Click the Back to tenant configuration link
- Press the Done button
Start the volume:
- Click on the Manage Volumes link
- Click on the testsda start link
- Notice that testsda is successfully started
In a shell on the client, mount the volume:
- enter
mkdir /mnt/testsda
- enter
hfs_mount 192.168.122.21 yoyodyne bigboote /mnt/testsda
- enter
df
ormount
- Notice that /mnt/testsda was successfully mounted
Work-around for BZ 747112. In a shell on each server node, fix directory permissions:
- enter
chmod 01777 /bricks/sda/yoyodyne
In a shell on the client, initiate I/O:
- Perform I/O on the mounted volume, e.g. touch, cp, rm, ln, ln -s, mkdir, rmdir, ls, etc.
Expected Results
- files and directories are variously created, deleted, etc.