QA:Testcase HekaFS replicated

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
m (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:/...")
 
m
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)
 +
 +
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 on the yoyodyne volumes link
 
# Click the Enabled check-box for testsda
 
# Click the Enabled check-box for testsda
Line 31: Line 46:
 
# Click the Back to tenant configuration link
 
# 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
 +
 +
Mount the volume on the client:
 +
 
# In a shell on the client,  
 
# In a shell on the client,  
 
## enter `mkdir /mnt/testsda`
 
## enter `mkdir /mnt/testsda`
Line 39: Line 60:
 
## enter `df` or `mount`
 
## enter `df` or `mount`
 
## Notice that /mnt/testsda was successfully mounted
 
## Notice that /mnt/testsda was successfully mounted
 +
 +
Perform I/O on the client:
 +
 
# Perform I/O on the mounted volume, e.g. touch, cp, rm, ln, ln -s, mkdir, rmdir, ls, etc.
 
# 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.
 
# files and directories are variously created, deleted, etc.
 
}}
 
}}

Revision as of 15:25, 18 October 2011

Description

This test case tests the functionality of the HekaFS feature.


How to test

Run your web browser of choice:

  1. Open web browser to server node1, port 8080 (e.g. http://192.168.122.21:8080)

Add servers to the cluster:

  1. Click on the Manage Servers link
  2. Notice that server node 1 (192.168.122.21) is already listed as a Cluster Node
  3. Add one or more additional nodes:
    1. Enter 192.168.122.22 and press the Add button
    2. Notice that 192.168.122.22 is successfully added
    3. Click on the Back to cluster configuration link
    4. repeat for additional server nodes
  4. Press the Done button

Provision a volume in the cluster:

  1. Click on the Manage Volumes link
  2. Check the check-boxes for /bricks/sda on all server nodes
  3. Leave the Replica or Stripe count box empty.
  4. Enter testsda in the Volume ID box
  5. Press the Provision button
  6. Notice that the volume has been successfully provisioned
  7. Click the Back to volume configuration link
  8. Notice that the check-boxes for bricks/sda are insensitive (grayed out)
  9. Press the Done button

Create a tenant for the volume:

  1. Click on the Manage Tenants link
  2. 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.
  3. Press the Add button
  4. Notice that yoyodyne is successfully added
  5. Click on the Back to tenant configuration link

Enable the volume for the tenant:

  1. Click on the yoyodyne volumes link
  2. Click the Enabled check-box for testsda
  3. Press the Update button
  4. Notice that the volume is successfully enabled for the tenant
  5. Click the Back to tenant configuration link
  6. Press the Done button

Start the volume:

  1. Click on the Manage Volumes link
  2. Click on the testsda start link
  3. Notice that testsda is successfully started

Mount the volume on the client:

  1. In a shell on the client,
    1. enter `mkdir /mnt/testsda`
    2. enter `hfs_mount 192.168.122.21 yoyodyne bigboote /mnt/testsda`
    3. enter `df` or `mount`
    4. Notice that /mnt/testsda was successfully mounted

Perform I/O on the client:

  1. Perform I/O on the mounted volume, e.g. touch, cp, rm, ln, ln -s, mkdir, rmdir, ls, etc.

Expected Results

  1. files and directories are variously created, deleted, etc.