[Gluster-devel] Glupy bugs: found the solution?

Thiago da Silva thiago at redhat.com
Wed Feb 12 16:31:46 UTC 2014


Thanks for the link, I will make sure to incorporate those changes to
the new code. It will also server as a good starting point for a new
functions.

On Wed, 2014-02-12 at 06:53 +0000, Justin Clift wrote:
> On 11/02/2014, at 7:47 PM, Thiago da Silva wrote:
> > Hi Justin, 
> > 
> > I have started the work, but it is not yet complete. We currently have
> > the same functions that was part of the example code. I think this is
> > good enough so that the existing Python libgfapi can be removed from
> > Gluster 3.5 dev tree. This way I can also start working to create a
> > separate rpm, which gluster-swift would depend on once we make the move
> > away from fuse.
> > 
> > I have separated the tests to their own files and we have both unit and
> > functional tests running automatically on Jenkins
> > (http://build.gluster.org).
> > 
> > I'm currently working with Ben England to run some tests with his
> > smallfile.py project (https://github.com/bengland2/smallfile)
> > 
> > I don't think it is ready yet for real world usage, but we are moving
> > towards that...
> 
> No worries.  :)
> 
> As a thought, some of the code here maybe a useful addition:
> 
>   http://review.gluster.org/#/c/6158/3/api/examples/gfapi.py
>   http://review.gluster.org/#/c/6158/
> 
> I'd started adding docstrings, functions, and fixing one or two bugs
> in Gluster code base a while ago, but then went on holiday.
> 
> It might apply cleanly to your gfapi.py, though I haven't written
> any unit tests for it (yet).
> 
> Guess I should look at making a pull request with the code... :)
> 
> + Justin
> 
> 
> > Thiago
> 
> --
> Open Source and Standards @ Red Hat
> 
> twitter.com/realjustinclift
> 






More information about the Gluster-devel mailing list