On 1/10/22 16:47, Gregory Farnum wrote:
On Fri, Dec 24, 2021 at 2:29 PM Thomas Goirand <zigo@xxxxxxxxxx> wrote:
Hi,
Thanks to Adrian Bunk who helped with a few tricks to save on compile
time memory, Ceph Pacific built on all arch, including the most annoying
one, aka mipsel. I'll be uploading it to both Unstable and Bullseye
official backports soonish and start testing.
I'd like to build the functional testing platform, I've heard there's
such a test suite, but I can't remember where I saw it. Any pointer?
Do you mean teuthology? https://github.com/ceph/teuthology
It draws on the test suites defined in
https://github.com/ceph/ceph/tree/master/qa
But there's no "build" for it — it's all python. And actually running
it is a heck of a project! I wouldn't recommend that unless an org has
a significant hardware base they're ready to devote to running the
tests (our lab is ~ we have more than 250 servers in the upstream lab.
-Greg
Thanks for your answer.
I read about teuthology, though I was wondering what kind of setup it
would need, and what would be the best approach to set it up. Does one
simply installs teuthology in a single server, connected to the test
Ceph cluster?
Once teuthology is setup, how does one select what test to run? Simply
using "teuthology <argument>" ?
I've seen teuthology is in Python, and it looks reasonably easy to
package (FYI, it's been 10 years I maintain all of OpenStack in Debian,
nearly alone, so I'm kind of familiar with Python packaging ... :).
How much hardware would be the minimum? I guess I could get a small
cluster up, something like 3 mons and 9 OSDs with recycled hardware.
Would that be enough?
Would it be enough to run Ceph inside VMs in an OpenStack cloud? That's
be a way more convenient than working with real hardware.
Cheers,
Thomas Goirand (zigo)
_______________________________________________
Dev mailing list -- dev@xxxxxxx
To unsubscribe send an email to dev-leave@xxxxxxx
