This document discusses tools for testing a cluster environment and executing tests. It describes using tools like pdsh and Ansible to configure an 8 node cluster with 4 servers and 4 clients by running commands across nodes to check IP settings and time. It also recommends using screen to keep long running tests active in SSH sessions and log output to files.

1. Tools for testing
Vikentsi Lapa for MLUG 2013

2. Testing process
Analysis,
Planning,
Test Cases
Development
Environment
Setup
Test
Execution
Test Cycle
Closure

3. Cluster environment setup
●
8 nodes
–
–
●
4 servers
4 clients
Simple tasks
–
–
Get IP settings from all nodes
–
●
Check time on all cluster nodes
Copy /etc/multipath.conf only to server nodes
How to complete this tasks?

4. Environment setup
Use /dev/fast_fingers
for node in client-1 client-2 …
do
echo $node
ssh $node date
done
Use some tool

5. Environment Setup
●
pdsh
–
–
●
pdsh -a date
pdsh -w server-[1-4] uptime
dshbak
–
●
pdsh -a ip addr | dshbak
pdcp
–
pdcp -a /etc/hosts /etc/
–
pdcp -a -x client-[1-8] /etc/multipath.conf /etc/

6. Environment Setup
●
Ansible = Puppet, Chef, but
●
but has differences
–
minimal infrastructure
●
–
requires only Python and SSH access to node
2 modes
●
●
command line mode similar to pdsh
playbooks
–
keeps configuration in YAML files
–
extensible
●
modules (any language), plugins

7. Test Execution
●
screen
–
keep long running test active in SSH session
–
store information about bugcreate log file
●
●
test is started, test is finished ctrl-alt-H
log file name can be changed
–
–
●
: logfile tc78_%c_%D_%M
create console “screenshot” to file
similar tools
–
tmux, script, nohup

8. Summary
●
Cluster tools
–
for environment configuration
●
●
–
pdsh https://code.google.com/p/pdsh/
Ansible http://www.ansibleworks.com/
for test execution
●
screen or tmux, script