This project strives to create a reproducable setup with which to test different OwnCloud and Nextcloud versions next to one another using Apache JMeter.
The test does the following:
- Start off with a clean database
- Create a number of users, usernames are gebruiker1, gebruiker2, etcetera (gebruiker is Dutch for user)
- Password is equal to username
- Perform a number of searches for users at specified intervals during user creation
- Do a number of uploads of specific size for each user
- gebruiker1 shares a number of files with gebruiker2
- Propfinds are done for gebruiker2 with different number of shares
Note: I run linux exclusively; the documentation is written from that perspective. Some tweaking may be required for OSX or Windows, and installing the tools may be more complex.
After cloning the project, you need to copy two .dist files, and edit them to your needs:
- vars/main.yml.dist -> vars/main.yml
- data/xcloud-performance.properties.dist -> data/xcloud-performance.properties
To make sure the downloading of sources works without problems, it is possible to create your own mirror; downloading from the vendors gave me some trouble at times. You can enter the location of sources in vars/main.yml. The defaults point to the vendors sites.
Install Ansible, Vagrant and VirtualBox. Known to work with these versions:
- Ansible 2.7.6
- Vagrant 2.0.2
- VirtualBox 5.2.4
Note: You need the guest additions, you can install these with
vagrant plugin install vagrant-vbguest
- Make a clone of this project
- Enter the project directory
- Copy and edit the .dist files (see above)
- Execute
vagrant up - Have some tea
- Execute
vagrant sshto log into the VM - You can browse to the different installations on http://localhost:8080/*vendor*-*version*, i.e. http://localhost:8080/owncloud-10.0.9
- Current Owncloud versions are 8.2.11, 9.1.8, 10.0.3, 10.0.9 and 10.0.10
- Current Nextcloud versions are 10.0.6, 11.0.4, 12.0.2, 13.0.5, 14.0.6 and 15.0.2
- Log on to the webinterface with admin/admin
- Send changes to the VM with
vagrant provision
To run the tests:
- Log into the VM with
vagrant ssh sudo /opt/apache-jmeter-*/run.sh *vendor* *version*to test a specific versionsudo /opt/apache-jmeter-*/all.shto test all versions
The tests run on a clean database, so all data is written by the test. You can also do an extra run with additional data applied. To do so, put a sql file in roles/jmeter/files/dumps, named vendor-version-extra.sql.
By passing a command line option, all queries are logged and written to the output directory:
sudo /opt/apache-jmeter-*/all.sh log-mysql
or
sudo /opt/apache-jmeter-*/run.sh *vendor* *version* log-mysql
When a test has run, a HTML report is written to vagrant-dir/data/jmeter/vendor-version/html (JMeter writes it to the shared folder)
The data of the optional second run are in vagrant-dir/data/jmeter/vendor-version/html-extra
It's easiest if you log into the vagrant VM using X forwarding.
Start jmeter: /opt/apache-jmeter-*/bin/jmeter.sh
Open the file /vagrant/data/xcloud-performance.jmx. Now you can run the tests in the GUI. Changes can be committed to git on the Vagrant host.
You can use vagrant provision, or you can also run the playbook directly with ansible-playbook provision.yml, which is handy if you want to run certain tags only.
It is advisable to first set up the project in a working state. In this example we will add OwnCloud 10.1.0.
Add the new version to:
- vars/main.yml (use a random instanceid)
Now do a vagrant provision. This will lead to an error.
- In a browser, navigate to the environment, http://localhost:8080/owncloud-10.1.0/
- Create an admin account with password 'admin'
- Configure the database, databasename, user and password similar to the other installations, in this case owncloud-1010
- Finish setup
- Do not log into ownCloud yet!
- Log in using
vagrant ssh - Copy config.php of the new installation to the Vagrant host:
sudo cp /var/www/html/owncloud-10.1.0/config/config.php /vagrant/roles/xcloud/templates/owncloud/config-10.1.0.j2
Remove the first two and the last line, so you are left with just the contents of the $CONFIG array. See the other version as an example. - Dump the database to the vagrant host:
mysqldump -u root owncloud-1010 | bzip2 > /vagrant/roles/jmeter/files/dumps/owncloud-1010.sql.bz2 - Copy the instanceid from config.php to vars/main.yml
- Optional: Copy the contents of 'appdata_instanceid' naar xcloud/files/data/vendor_version (see for instance nextcloud-12.0.2)
- Add the new files to git.
- Still in the vagrant VM:
sudo rm -rf /var/www/html/owncloud-10.1.0mysqladmin -f -u root drop owncloud-1010- Log off
vagrant provision
This should now run without errors.
Navigate to http://localhost:8080/owncloud-10.0.9/ and log in with 'admin/admin'.
This is a work in progress, but you can now add apps. To do so, specify the app in the 'apps' dict as in vars/main.yml.dist
You can then tell each version of the cloud software which apps to use, again see vars/main.yml.dist
As you can see from the examples in the dist file, there are 2 ways to add the app: 'archive' or 'git'.
If you add the 'composer' variable, a 'make all' will be done in the app directory.
If the app requires configuration, place a snippet in templates/includes/[appname].j2
See files_primary_s3 as an example.
In addition, you can enable/disable bundled app with the 'enable' and 'disable' lists.
You can run Jmeter in gui mode to debug or change the tests. You will need a vagrant host that does X forwarding! How to set that up is beyond the scope of this document.
- Log into the VM with
vagrant ssh - execute
/opt/apache-jmeter-*/bin/jmeter & - Open the jmx file in /vagrant/data
- In the 'User Defined Variables' section, you need to enter the default vendor and version you want to test against
- The other settings are read from the xcloud-performance.properties files
- You're now good to go!
- Expand JMeter tests
- ...
- Downloading the JMeter zip file fails sometimes. A workaround is to download it manually on the VM and place it in /opt.