- We don’t need ceph-extra for trusty
- Enable multiverse repo for access to libapache2-mod-fastcgi
- Update cache before attempting to install packages to register
multiverse repo and only refresh cache once an hour to avoid delays in
the playbook
- Add wildcard to disabling default site as on Ubuntu it is 000_default
by…default
While running big boxes with 72 disks it's easy to get out of PID for
all the threads needed by Ceph. Increasing the default value removes
this limitation.
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.
In ceph-common you load {{ ansible_managed }} at the top of the main
config file - this will trigger handlers on that file whenever an
Ansible run is made.
I'd suggest replacing it with a vanilla text comment 'managed by
Ansible' to warn
admins but avoid unnecessary cluster bounces.
fixes: #125
Signed-off-by: Sébastien Han <sebastien.han@enovance.com>
The ceph.conf.j2 template currently always uses the current host facts
to get the IP address of each host in the mon loop. This is not the
expected behavior. This patch uses the correct facts to get the IP.
Recovery and/or re-balancing decrease performance, adding more options
might help tweaking this behavior.
Signed-off-by: Sébastien Han <sebastien.han@enovance.com>
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>
Matthew Rees
Leseb
Cornelius Keller
Matthew Rees
Gauvain Pocentek
Leonid Laboshin
jjoos