On Wed, Sep 7, 2016 at 8:55 PM, Niels de Vos <ndevos@xxxxxxxxxx> wrote:
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@xxxxxxxxxx> 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 Yes, these operations would need to be done while clients access the
> >
> > 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?
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.
Added the cases to the checklist.
Niels
--
Pranith
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
