We use ceph rbd as a volume service for both an Openstack deployment and
a series of Proxmox servers. This ceph deployment started as a Hammer
release and has been upgraded over the years to where it is now running
Quincy. It has been fairly solid over that time, even
through upgrades from filestore to bluestore, and many transparent
hardware replacements/improvements.
One concern we have is that when we have a hypervisor that unexpectedly
dies/crashes, the volumes must always have the object maps rebuilt. If
we don't rebuild the object maps, the VMs will either not boot, or we
will have other side-effects that render the volume unusable. (ie cannot
mount root). Is this to be expected during this type of event or have
I missed a setting during one of the many upgrade on our deployment?
Thankfully the above does not happen regularly, but we would like to
make use of the HA features of proxmox to ensure some VMs are always
available. Requiring the rebuild step limits what can be done
automatically, and how quickly it can be recovered.
Any advice on ceph configuration, or how others may adapt to the
requirements in HA situations would be appreciated.
Cheers,
Gary
--
Gary Molenkamp Science Technology Services
Systems Engineer University of Western Ontario
molen...@uwo.ca http://sts.sci.uwo.ca
(519) 661-2111 x86882 (519) 661-3566
_______________________________________________
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io
