From: Jeff Layton <jlayton@redhat.com>
To: David Galloway <dgallowa@redhat.com>
Cc: dev <dev@ceph.io>, Ceph Development <ceph-devel@vger.kernel.org>,
sepia <sepia@ceph.io>
Subject: Re: provisioning clients in teuthology with an extra local filesystem
Date: Tue, 01 Dec 2020 10:24:31 -0500 [thread overview]
Message-ID: <aa38cc3b2ed96fed0dbee443fed564ac8d1a151d.camel@redhat.com> (raw)
In-Reply-To: <ad5a9630-daa0-b379-c7f4-5a9a139cd3a5@redhat.com>
On Tue, 2020-12-01 at 10:22 -0500, David Galloway wrote:
> On 12/1/20 9:55 AM, Jeff Layton wrote:
> > I've been working on a patch series to overhaul the fscache code in the
> > kclient. I also have this (really old) tracker to add fscache testing to
> > teuthology:
> >
> > https://tracker.ceph.com/issues/6373
> >
> > It would be ideal if the clients in such testing had a dedicated
> > filesystem mounted on /var/cache/fscache, so that if it fills up it
> > doesn't take down the rootfs with it. We'll also need to have
> > cachefilesd installed and running in the client hosts.
> >
> > Is it possible to do this in teuthology? How would I approach this?
> >
>
> I think I can make this happen pretty easily in ceph-cm-ansible. What
> I'd need from you is desired filesystem type and size. Once I'm done
> with my end, we'll need to create a cephlab.ansible overrides yaml
> fragment to stick in that suite's qa directory.
>
Ok, cool:
fstype: xfs or ext4 (either is fine)
size: ~50g or so would be ideal, but we can probably get away with less
if necessary
Thanks!
--
Jeff Layton <jlayton@redhat.com>
next prev parent reply other threads:[~2020-12-01 15:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 14:55 provisioning clients in teuthology with an extra local filesystem Jeff Layton
2020-12-01 15:22 ` David Galloway
2020-12-01 15:24 ` Jeff Layton [this message]
2020-12-01 19:23 ` David Galloway
2020-12-01 20:07 ` Jeff Layton
2020-12-01 21:31 ` David Galloway
2020-12-01 21:59 ` Jeff Layton
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=aa38cc3b2ed96fed0dbee443fed564ac8d1a151d.camel@redhat.com \
--to=jlayton@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=dev@ceph.io \
--cc=dgallowa@redhat.com \
--cc=sepia@ceph.io \
/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;
as well as URLs for NNTP newsgroup(s).