I'm not sure if this is already in place, but if not I think pool quotas should be exposed in the same way as pool size so Libvirt can pick up on them. We currently run several KVM hypervisors backed by Ceph RBD. We have a CRUSH ruleset that defines SSD backed servers for RBD, and high capacity HDD backed servers for RadosGW. Right now when adding our RBD pool via Libvirt it sees the entire cluster's capacity, even though the actual pool capacity is much lower. This means that any deployment tools that look at the available capacity when creating VMs can't be relied upon, and we have to continually track usage manually (we audit it anyway, but that should be in addition to built-in checks). We can currently work around this by manually setting the capacity in the deployment tool, but fixing it at the source seems like a much better option. Obviously capacity can't be automatically estimated from the CRUSH ruleset, but with the recent addition of pool quotas it would be useful to let Libvirt (and other clients) pull the quota size so we could set them as needed. Some changes will need to be made on the Libvirt side as well, but the functionality has to be implemented in Ceph first. I have opened an issue in the tracker for this: http://tracker.ceph.com/issues/10226 If this functionality already exists I'll close the issue and work on things from the Libvirt side. Thank You, Logan Barfield Tranquil Hosting -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
