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>
Sébastien Han
Joseph Glanville
Lorin Hochstein