From: Wido den Hollander <wido@42on.com>
To: Logan Barfield <lbarfield@tqhosting.com>, ceph-devel@vger.kernel.org
Subject: Re: Expose pool quota for Libvirt
Date: Fri, 05 Dec 2014 10:05:47 +0100 [thread overview]
Message-ID: <5481756B.6050301@42on.com> (raw)
In-Reply-To: <CACKLxkC0Xy1AShOK=cfo1F+-OJnus74KPWSgWubduhjY0+YVow@mail.gmail.com>
On 12/03/2014 05:39 PM, Logan Barfield wrote:
> 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.
>
Yes, that would be ideal indeed.
> 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.
>
The main problem here is that I currently don't see a way in librados to
fetch this information.
rados_pool_stat_t in librados.h does not expose a quota or anything
similar. So what currently happens is that Libvirt does a cluster stat()
in librados and fetches how large the cluster is.
If librados exposes a way to get the quota from a pool it would be very
simple to fix this in Libvirt.
> I have opened an issue in the tracker for this:
> http://tracker.ceph.com/issues/10226
>
I'll assign this to myself.
> 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@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Wido den Hollander
42on B.V.
Ceph trainer and consultant
Phone: +31 (0)20 700 9902
Skype: contact42on
prev parent reply other threads:[~2014-12-05 9:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 16:39 Expose pool quota for Libvirt Logan Barfield
2014-12-05 9:05 ` Wido den Hollander [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5481756B.6050301@42on.com \
--to=wido@42on.com \
--cc=ceph-devel@vger.kernel.org \
--cc=lbarfield@tqhosting.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox