[Gluster-devel] Checklist for gfapi for upstream release

[Niels de Vos]

On Tue, Sep 06, 2016 at 10:32:58PM +0530, Pranith Kumar Karampuri wrote:
> On Mon, Sep 5, 2016 at 8:54 PM, Niels de Vos <ndevos at redhat.com> wrote:
> 
> > On Sat, Sep 03, 2016 at 12:10:41AM +0530, Pranith Kumar Karampuri wrote:
> > > hi,
> > >         I think most of this testing will be covered in nfsv4, smb
> > testing.
> > > But I could be wrong. Could you let me know who will be providing with
> > the
> > > list if you think there are more tests that need to be run?
> > >
> > > I can update it at https://public.pad.fsfe.org/p/
> > > gluster-component-release-checklist
> >
> > I've added this to the etherpad:
> >
> > > test known applications, run their test-suites:
> > >     glusterfs-coreutils (has test suite in repo)
> > >     libgfapi-python (has test suite in repo)
> > >     nfs-ganesha (pynfs and cthon04 tests)
> > >     Samba (test?)
> > >     QEMU (run qemu binary and qemu-img with gluster:// URL,
> > possibly/somehow run Advocado suite)
> >
> 
> I think we should also add add-brick/replace-brick with gfapi? Thoughts?

Yes, these operations would need to be done while clients access the
volume through the applications. These tests are mostly done by the QA
team in Red Hat, and they are planning to provide distaf/Glusto
testcases for this basic Gluster functionality. I really hope those
tests land in our repository soon now.

Niels
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://www.gluster.org/pipermail/gluster-devel/attachments/20160907/48e94143/attachment.sig>