SAIO Ansible playbook

An Ansible playbook for provisioning a Swift and Swift-on-File all-in-one development environment on Fedora or CentOS(default).

To run:

To provision the VM, run:

1. vagrant up --provider=virtualbox

To run automated tests:

1. vagrant ssh
2. cd /vagrant/source/swift
3. ./.unittests
4. ./.functests

To quickly test installation:

1. swift stat
2. echo 'hello world' > hw
3. swift upload c1 hw
4. swift list

To test installation with Swift-on-File (Note: make sure to have Swift-on-File provisioned):

1. swift post c2 -H 'X-Storage-Policy: swiftonfile'
2. echo 'hello swiftonfile' > hs
3. swift upload c2 hs
4. swift list
5. ls /mnt/swiftonfile

Configuration Options:

You can set a few options to change how the VM is provisioned. In global_vars.yml, you can set if you want Swift-on-File configured or not and what storage policy should be set as the default. In the Vagrantfile, you can choose to provision either a Fedora VM or a CentOS-7 VM.

Gerrit repo setup

In case you would like to use the provisioned VM as your development environment, Ansible can add gerrit as a remote repo to both Swift and Swift-on-File. Checkout the options in global_vars.yml

Running Ansible only:

In case you already have a VM created and just wants to execute the Ansible playbook, run the following command:

1. ansible-playbook site.yml -i "192.168.56.103," --ask-sudo-pass

####Notes:

• Make sure to update to the correct IP address on the command above (it's important to keep the comma ',' at the end) and the username and group variables in global_vars.yml
• If testing on RHEL/CentOS, enable EPEL repository first.

Todo:

• Add gluster volume