Conversation
roles/perf/README.md
Outdated
| @@ -0,0 +1,40 @@ | |||
| network_perf | |||
There was a problem hiding this comment.
Also update the README.md with this role description?
There was a problem hiding this comment.
Is the role called network_perf?
There was a problem hiding this comment.
It is called perf. Earlier I had named it network_perf, since we do lot of other tests I renamed the role to perf. This is a typo, I will fix it.
roles/perf/README.md
Outdated
| network_perf | ||
| ========= | ||
|
|
||
| Gathers the network performance on the nodes |
There was a problem hiding this comment.
is this role only gathering the network performance? How about the cpu, memory and disk stats?
There was a problem hiding this comment.
No, it is not just the network performance, but disk and other performance tests are run as well. I will update the description.
|
|
||
| netperf3 | ||
|
|
||
| Example Playbook |
There was a problem hiding this comment.
provide a more detailed example?
Isn't the gluster volume on which the tests need to be run needed as an input?
There was a problem hiding this comment.
Yes. We need it, actually we check the mandatory variables in the role:
assert:
that:
- "{{item}} is defined"
fail_msg: "FAIL: variable {{item}} not set"
success_msg: "PASS: variable {{item}} is defined."
run_once: true
delegate_to: localhost
with_items:
- gluster_maintenance_volname
- gluster_maintenance_mountpoint
- gluster_maintenance_client
| | gluster_maintenance_net_nodes | Yes | | UNDEF | List of nodes on which to collect the network performance numbers. | | ||
| | gluster_maintenance_net_single | No | | First node in the list | Collect the perf numbers from all nodes to one lead host | | ||
| | gluster_maintenance_net_ping_duration | No | | 10 | Ping counter | | ||
| | gluster_maintenance_net_iperf_duration | No | | 30 | iperf timer; time in seconds to transmit for | |
There was a problem hiding this comment.
Yes, I will add them. I remember documenting all the variables, I will check and add.
| ------------ | ||
|
|
||
| gluster-ansible | ||
| netperf3 |
There was a problem hiding this comment.
Any other pre-requisites needed? VM to be created?
There was a problem hiding this comment.
Yes. But conventionally only the package requirements are listed here. This is more like dependency list.
There was a problem hiding this comment.
This is a specific test to customers who are storing VM data on GlusterFS. I have added NOTES file which contains the comments from a bug.
| with_items: | ||
| - gluster_maintenance_volname | ||
| - gluster_maintenance_mountpoint | ||
| - gluster_maintenance_client |
There was a problem hiding this comment.
what's the difference between gluster_maintenance_client and gluster_maintenance_vm ?
There was a problem hiding this comment.
gluster_maintenance client is the GlusterFS client. And vm is the virtual machine stored on GlusterFS.
| tags: | ||
| - vmservicestart | ||
|
|
||
| - name: Run fio tests |
There was a problem hiding this comment.
Assumes fio is installed? Should there be a step to install fio if not present?
There was a problem hiding this comment.
Yes. I'm not sure if fio comes as part of rhel/rhgs subscription. But we can add them.
|
@sac the fio tests seem to be run twice on the VM. |
sac
left a comment
There was a problem hiding this comment.
I have fixed this. I think I lost the earlier changes. I had run this role successfully a few times.
No description provided.