[Sheepdog] testing (was Config for dedicated storage network and NIC bonding?)

MORITA Kazutaka morita.kazutaka at lab.ntt.co.jp
Wed Aug 3 15:04:43 CEST 2011

At Wed, 3 Aug 2011 12:18:35 +0100,
Matthew Law wrote:
> On Fri, July 29, 2011 6:36 pm, MORITA Kazutaka wrote:
>  > Thank you.  The test we can use for Sheepdog now is only qemu-iotests.
> > It is a client-side test and it tests only VM's I/Os against Sheepdog
> > volumes.  I think we need a test framework for a server-side code
> > before using production purposes.  I suspect there are some bugs
> > around Sheepdog data recovery and node membership management.  It
> > would be really nice if somebody create a framework to test those
> > things.
> >
> > The other thing we need to do now is to create a recovery tool.  Some
> > users reported that their cluster became in an inconsistent state
> > because of Sheepdog errors or wrong shutdown.  We need something like
> > a fsck for Sheepdog.
> I don't think my skills are up to the challenge of writing an fsck but I
> would like to contribute and I am interested in writing some tests.


> Is there any preference for how to write the tests or a testing framework?
> -CUnit or cmockery for example?

Any testing framework or library is OK to me if it is enough popular.
To be honest, I'm not familiar with testing tools.  I'd like to hear
more opinions about this from other mailing list's members too.



More information about the sheepdog mailing list