Guillaume Abrioux 87e1f0cc6c osd: support changing default rule even when osd_crush_location isn't defined ... Creating crush rules even with no crush hierarchy configuration is a valid scenario so we shouldn't be bound to the first task result (which configure crush hierarchy) to be able to add new crush rules. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1816989 Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com> (cherry picked from commit 5b0476385c)		2020-03-31 23:14:55 +02:00
..
scenarios	osd: use _devices fact in lvm batch scenario	2020-01-14 15:33:15 +01:00
common.yml	fix calls to `container_exec_cmd` in ceph-osd role	2020-01-27 17:54:39 -05:00
container_options_facts.yml	ceph-osd: set container objectstore env variables	2020-01-20 15:36:11 -05:00
crush_rules.yml	osd: support changing default rule even when osd_crush_location isn't defined	2020-03-31 23:14:55 +02:00
main.yml	ceph-{mon,osd}: move default crush variables	2020-02-17 10:18:56 -05:00
openstack_config.yml	osd: do not change pool size on erasure pool	2020-03-06 16:10:03 +01:00
start_osds.yml	osd: ensure osd ids collected are well restarted	2020-01-13 14:31:03 -05:00
system_tuning.yml	ceph-osd: fix fs.aio-max-nr sysctl condition	2019-11-07 20:31:02 +01:00
systemd.yml	container: isolate systemd tasks	2019-10-01 18:50:51 +02:00