We want to force the user to only enable the options they need. Thus
they shouldn't have to enable one option and then disable another.
Signed-off-by: leseb <seb@redhat.com>
Now we don't need to activate the services through a variable. If the
role is activated in the inventory, actions will occur automatically.
Fixing the repo creation for red hat storage too.
Signed-off-by: leseb <seb@redhat.com>
* fix the Vagrantfile ruby check
* fix the variable positions
Bring more mandatory variables and try to separate Vagrant vars from the
playbook vars.
Signed-off-by: Sébastien Han <sebastien.han@enovance.com>
The box can be configured thanks to a new var, look at vagrant_variables
and select your box.
Handy to test several distros deployment.
Signed-off-by: Sébastien Han <sebastien.han@enovance.com>
This is really handy when we are testing code since we don't need to
modify the Vagrantfile, which is tracked by git.
The next commit will ignore the vagrant_variables.yml file.
Signed-off-by: Sébastien Han <sebastien.han@enovance.com>
When enabling radosgw virtual machines, we also need to enable the
radosgw variable. Same thing goes with the mds.
Signed-off-by: Sébastien Han <sebastien.han@enovance.com>
The recently added Trusty box was build with a Controller named
"SATAController", we must reuse the same name while adding our devices.
Signed-off-by: Sébastien Han <sebastien.han@enovance.com>
Depending on what we want to test, it might be handy to simply disable
the creation of a specific virtual machine. Now if NRGWS is set to 0
this will disable it.
Signed-off-by: Sébastien Han <sebastien.han@enovance.com>
Mostly cosmetic changes with a few changes to preferred conditional
formatting.
The only linting issues outstanding are lines that are too long and
using snake_case for the filename.
Since 192.168.0.0/24 is very commong and might overlap with some
existing networks on your laptop, using another subnet like '42' is less
bound to happen.
Signed-off-by: Sébastien Han <sebastien.han@enovance.com>
Because of the following bug: http://tracker.ceph.com/issues/8551
If we use a disk file size of 1GB the OSD weight calculation ends up
being 0. Thus no data will be stored on any OSD.
Increasing the disk file size up to 11GB (we save some filesystem
overhead since the calculation is based on df thus 11GB is safer than
10GB). Because we significantly increased the size of the disk files we
now only create 2 devices per OSD host.
Signed-off-by: Sébastien Han <sebastien.han@enovance.com>
* Use a box that supports all providers
* Fix hdd creation so it doesn't call customize more than once
* Introduce method to create vmdks
* Add provider customization for VMware Fusion
Use Vagrant's built-in support for Ansible provisioner. This eliminates the need
for a hosts file, and simplifies the ansible config file.
Renames config from .ansible.cfg to ansible.cfg since Ansible expects the file
to be called ansible.cfg and be adjacent to Vagrantfile when using the Vagrant
provisioner.
We now have 7 virtual machines in the Vagrant sandbox. This takes a lot
of memory. This might be a problem for some laptop and whon't help
testings.
Signed-off-by: Sébastien Han <sebastien.han@enovance.com>
Instead of having 5GB disks now we have 6 disks of 1GB per virtual
machine, which is more than enough for testing.
Signed-off-by: Sébastien Han <sebastien.han@enovance.com>
leseb
Sébastien Han
Yin Jifeng
Matthew Rees
Matthew Rees
Joseph Glanville
Lorin Hochstein