Re: [Gluster-devel] [Gluster-users] Our plan to get bugs fixed quicker, and features implemented sooner
adding the "correct" gluster-devel to this. On 8/21/2014 10:55 PM, Joe Julian wrote: There have been times that I, as a user and a front-line supporter, have marked a bug with the urgency that I think it deserves - based on my own knowledge as well as feedback from other users - only to have that urgency lowered to normal because a developer who doesn't experience the urgency we do as users, deemed it so. Granted, there have also been many occasions where I didn't set the urgency and my bug has been treated as if it was a message from beyond the natural realm, for which I am truly grateful. When I set the urgency, I try to consider more than just my own current needs (though often they're truly quite urgent) and look at potential for data loss, likelihood to encounter the bug during normal operations, and feedback from other users who have (usually) encountered the same bug. To have all that forethought discarded is disheartening. For that reason, I never set the urgency of any of my bugs any more. I would be willing to participate in triage, but I would expect the same rigidness in changing an urgency as there is in getting a change accepted. The developer who wants to change the urgency should be expected to argue his case, not simply change it. On 8/21/2014 12:12 AM, Lalatendu Mohanty wrote: I hope the subject line have increased your curiosity to go through the email :). As a community, we are looking for contributors for GlusterFS bug triage and hopefully this mail will give you enough motivation for it. As mentioned in the subject , bug triage will help to get bugs fixed quicker, and features implemented sooner. If you are not sure what bug triage means, please refer the gluster wiki page [1] for bug triage. Here are few questions and answers to help you if this is something you should do. * Q: Why we need to do bug triage? * A: It reduces the time between reporting a bug and the availability of a fix enormously. o Because many developers have bad response times for new bugs that are not pointed out to them. When well triaged bugs get assigned to right developers, the response time improves. o Also developers work mainly on writing bug fixes and implementing new features. Which in turn results in to spending (too little) time on bug triaging. * Q: I am just a GlusterFS user. Why bug triage will help me? * A: It will increase your understanding of GlusterFS, current issues in GlusterFS, increase the interaction between developers, community and triager. It will also help filing better bugs too. The better the bug report, the easier it is for a developer to write a fix. * Q: Do you run GlusterFS in production? * A: If your answer is yes, then bug triage is the right platform for you to raise the importance of bugs. Bug triage will also help you know existing issues in the version of GlusterFS you are using, help you to know existing issues in a new feature. So you will be in a better position to decide if a feature is production ready or not. * Q: I want to contribute to GlusterFS. Will bug triage help? * A: Yes, it is an awesome place to start. You will get to know about all the components in GlusterFS along with issues in each of them. This knowledge will help you to do better testing, development (bug fixing) etc. Also you will interact with developers while triaging bugs. You can use these interactions to ask more detailed questions. * Q: How can I triage bugs of GlusterFS? * A: The wiki page [1] is the right place start. We are starting up a bi-weekly/weekly triage meeting in #gluster-meeting on Freenode. There would be another mail with details about the meeting. You can join the meeting and interact with other triagers. Please don't hesitate to hit the reply button if you have any question on this. We would love to hear your suggestions/feed back :). [1] http://www.gluster.org/community/documentation/index.php/Bug_triage Thanks, On behalf of the bug triage team #gluster-dev, #gluster on Freenode ___ Gluster-users mailing list gluster-us...@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-users ___ Gluster-users mailing list gluster-us...@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-users ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] patches missing in git even after gerrit says they are merged
I believe Vijay/Avati can do that. On Fri, Aug 22, 2014 at 11:57 AM, Krishnan Parthasarathi < kpart...@redhat.com> wrote: > Humble, > > Who will be mergeing these patches into the repo? > > ~KP > > - Original Message - > > Below patches were in status of 'submitted , merge pending' when gerrit > went > > wrong yesterday. > > > > http://review.gluster.org/#/c/8459/ > > http://review.gluster.org/#/c/8466/ > > http://review.gluster.org/#/c/8507/ > > > > Possibly we have to merge those in repo again. > > > > --Humble > > > > > > On Fri, Aug 22, 2014 at 10:12 AM, Sachin Pandit < span...@redhat.com > > wrote: > > > > > > Hi, > > > > In gerrit, the status of http://review.gluster.org/#/c/8507/ is merged. > > But I dont see the changes in git as Pranith mentioned. > > > > ~ Sachin. > > > > - Original Message - > > From: "Pranith Kumar Karampuri" < pkara...@redhat.com > > > To: "Vijay Bellur" < vbel...@redhat.com > > > Cc: "Gluster Devel" < gluster-devel@gluster.org > > > Sent: Thursday, August 21, 2014 10:05:42 PM > > Subject: [Gluster-devel] patches missing in git even after gerrit says > they > > are merged > > > > hi Vijay, > > http://review.gluster.org/#/c/8466/ is one such candidate. CCed > > gluster-devel so that others can also verify that their patches are in. > > > > Pranith > > ___ > > Gluster-devel mailing list > > Gluster-devel@gluster.org > > http://supercolony.gluster.org/mailman/listinfo/gluster-devel > > ___ > > Gluster-devel mailing list > > Gluster-devel@gluster.org > > http://supercolony.gluster.org/mailman/listinfo/gluster-devel > > > > > > ___ > > Gluster-devel mailing list > > Gluster-devel@gluster.org > > http://supercolony.gluster.org/mailman/listinfo/gluster-devel > > > ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] patches missing in git even after gerrit says they are merged
Humble, Who will be mergeing these patches into the repo? ~KP - Original Message - > Below patches were in status of 'submitted , merge pending' when gerrit went > wrong yesterday. > > http://review.gluster.org/#/c/8459/ > http://review.gluster.org/#/c/8466/ > http://review.gluster.org/#/c/8507/ > > Possibly we have to merge those in repo again. > > --Humble > > > On Fri, Aug 22, 2014 at 10:12 AM, Sachin Pandit < span...@redhat.com > wrote: > > > Hi, > > In gerrit, the status of http://review.gluster.org/#/c/8507/ is merged. > But I dont see the changes in git as Pranith mentioned. > > ~ Sachin. > > - Original Message - > From: "Pranith Kumar Karampuri" < pkara...@redhat.com > > To: "Vijay Bellur" < vbel...@redhat.com > > Cc: "Gluster Devel" < gluster-devel@gluster.org > > Sent: Thursday, August 21, 2014 10:05:42 PM > Subject: [Gluster-devel] patches missing in git even after gerrit says they > are merged > > hi Vijay, > http://review.gluster.org/#/c/8466/ is one such candidate. CCed > gluster-devel so that others can also verify that their patches are in. > > Pranith > ___ > Gluster-devel mailing list > Gluster-devel@gluster.org > http://supercolony.gluster.org/mailman/listinfo/gluster-devel > ___ > Gluster-devel mailing list > Gluster-devel@gluster.org > http://supercolony.gluster.org/mailman/listinfo/gluster-devel > > > ___ > Gluster-devel mailing list > Gluster-devel@gluster.org > http://supercolony.gluster.org/mailman/listinfo/gluster-devel > ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] patches missing in git even after gerrit says they are merged
Below patches were in status of 'submitted , merge pending' when gerrit went wrong yesterday. http://review.gluster.org/#/c/8459/ http://review.gluster.org/#/c/8466/ http://review.gluster.org/#/c/8507/ Possibly we have to merge those in repo again. --Humble On Fri, Aug 22, 2014 at 10:12 AM, Sachin Pandit wrote: > Hi, > > In gerrit, the status of http://review.gluster.org/#/c/8507/ is merged. > But I dont see the changes in git as Pranith mentioned. > > ~ Sachin. > > - Original Message - > From: "Pranith Kumar Karampuri" > To: "Vijay Bellur" > Cc: "Gluster Devel" > Sent: Thursday, August 21, 2014 10:05:42 PM > Subject: [Gluster-devel] patches missing in git even after gerrit says > they are merged > > hi Vijay, > http://review.gluster.org/#/c/8466/ is one such candidate. CCed > gluster-devel so that others can also verify that their patches are in. > > Pranith > ___ > Gluster-devel mailing list > Gluster-devel@gluster.org > http://supercolony.gluster.org/mailman/listinfo/gluster-devel > ___ > Gluster-devel mailing list > Gluster-devel@gluster.org > http://supercolony.gluster.org/mailman/listinfo/gluster-devel > ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] patches missing in git even after gerrit says they are merged
Hi, In gerrit, the status of http://review.gluster.org/#/c/8507/ is merged. But I dont see the changes in git as Pranith mentioned. ~ Sachin. - Original Message - From: "Pranith Kumar Karampuri" To: "Vijay Bellur" Cc: "Gluster Devel" Sent: Thursday, August 21, 2014 10:05:42 PM Subject: [Gluster-devel] patches missing in git even after gerrit says they are merged hi Vijay, http://review.gluster.org/#/c/8466/ is one such candidate. CCed gluster-devel so that others can also verify that their patches are in. Pranith ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] FALLOC_FL_COLLAPSE_RANGE?
On 08/22/2014 06:27 AM, Justin Clift wrote: Just noticed this: http://article.gmane.org/gmane.comp.file-systems.xfs.general/60475 Is it something of interest to us? I have been meaning to explore adding both FALLOC_FL_COLLAPSE_RANGE and FALLOC_FL_ZERO_RANGE flags to fallocate() in glusterfs but never got around to it. Don't know if the feature is beneficial per se (see comments in http://lwn.net/Articles/589260/ ), but since it has been merged in the 3.15 kernel, I guess it's going to be around forever. Let me take this up. Apparently more flags (FALLOC_FL_INSERT_RANGE and IOC_MOV_DATA) are in the works for fallocate(). Ravi + Justin -- GlusterFS - http://www.gluster.org An open source, distributed file system scaling to several petabytes, and handling thousands of clients. My personal twitter: twitter.com/realjustinclift ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
[Gluster-devel] FALLOC_FL_COLLAPSE_RANGE?
Just noticed this: http://article.gmane.org/gmane.comp.file-systems.xfs.general/60475 Is it something of interest to us? + Justin -- GlusterFS - http://www.gluster.org An open source, distributed file system scaling to several petabytes, and handling thousands of clients. My personal twitter: twitter.com/realjustinclift ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] patches missing in git even after gerrit says they are merged
On 21/08/2014, at 5:35 PM, Pranith Kumar Karampuri wrote: > hi Vijay, > http://review.gluster.org/#/c/8466/ is one such candidate. CCed > gluster-devel so that others can also verify that their patches are in. It's likely some after effect of the "git gc" being run as wrong user earlier on review.gerrit.org. (partially resolved by chown of /review/review.gluster.org/git) Misc and I aren't familiar enough with Gerrit to know how to get this "missing merged patches" problem fixed though. Hoping Vijay, Avati, [someone] knows how to fix this. :) + Justin -- GlusterFS - http://www.gluster.org An open source, distributed file system scaling to several petabytes, and handling thousands of clients. My personal twitter: twitter.com/realjustinclift ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
[Gluster-devel] patches missing in git even after gerrit says they are merged
hi Vijay, http://review.gluster.org/#/c/8466/ is one such candidate. CCed gluster-devel so that others can also verify that their patches are in. Pranith ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Change in glusterfs[master]: Regression test portability: mktemp
Le jeudi 21 août 2014 à 16:37 +0100, Justin Clift a écrit : > On 21/08/2014, at 2:40 PM, Justin Clift wrote: > > On 21/08/2014, at 1:07 AM, Harshavardhana wrote: > >> On Wed, Aug 20, 2014 at 2:49 PM, Justin Clift wrote: > >>> Any ideas? > >> > >> Avati just fixed it > >> > >> We had to run 'git gc' directly on the gerrit server - gerrit gc > >> failed (could be a gerrit bug). > > > > Avati, did you make a backup of the /review/ directory before doing this? > > > > It looks like the "git gc" command was run as root instead of review user, > > so the permissions of the git dirs under /review/ have gone weird, and > > Gerrit looks to have done bad things to itself from there (eg internal > > Gerrit corruption) > > > > Misc is trying to resolve it atm, but a backup of /review/ dir would > > be a good thing to have atm. :) > > Doing a chown of the /review/ directory seems to have fixed the problem. > > I've made a tarball of the /review/ directory after it, and am rsync-ing > it from that box to my personal Linode one as a extra backup step. > > The review.gluster.org server seems to have a severe bandwidth problem > though, limiting connections to ~30kb/s. (my rsync will take up 12kb/s > of that for the next ~8 hours) > > This will make backups fun. ;) We just need to make backup of the gerrit db, no need for the git repo since they are already mirrored to 2 locations with enough bandwidth. -- Michael Scherer Open Source and Standards, Sysadmin signature.asc Description: This is a digitally signed message part ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Change in glusterfs[master]: Regression test portability: mktemp
On 21/08/2014, at 2:40 PM, Justin Clift wrote: > On 21/08/2014, at 1:07 AM, Harshavardhana wrote: >> On Wed, Aug 20, 2014 at 2:49 PM, Justin Clift wrote: >>> Any ideas? >> >> Avati just fixed it >> >> We had to run 'git gc' directly on the gerrit server - gerrit gc >> failed (could be a gerrit bug). > > Avati, did you make a backup of the /review/ directory before doing this? > > It looks like the "git gc" command was run as root instead of review user, > so the permissions of the git dirs under /review/ have gone weird, and > Gerrit looks to have done bad things to itself from there (eg internal > Gerrit corruption) > > Misc is trying to resolve it atm, but a backup of /review/ dir would > be a good thing to have atm. :) Doing a chown of the /review/ directory seems to have fixed the problem. I've made a tarball of the /review/ directory after it, and am rsync-ing it from that box to my personal Linode one as a extra backup step. The review.gluster.org server seems to have a severe bandwidth problem though, limiting connections to ~30kb/s. (my rsync will take up 12kb/s of that for the next ~8 hours) This will make backups fun. ;) + Justin -- GlusterFS - http://www.gluster.org An open source, distributed file system scaling to several petabytes, and handling thousands of clients. My personal twitter: twitter.com/realjustinclift ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Question about file copy through libgfapi
Hi John, Thanks for your quick answer. Do you mean that my question can be summarized in "can we do server-only operations?"? Yes, I think so. Please let me know as soon as you receive any answer or provide me a link where I can follow directly this case. Thanks in advance and best regards, *Giacomo Fazio* IT Engineer Tel. +41 91 910 7690 E-mail: giacomo.fa...@wcpmediaservices.com | Web: www.wcpmediaservices.com Europe Office: Via Zurigo 35, 6900 Lugano, Switzerland USA Office: 7083 Hollywood Boulevard Los Angeles, CA 90028 On Thu, Aug 21, 2014 at 5:04 PM, John Mark Walker wrote: > Thanks, Giacomo. I'm sending this to the gluster-devel list - it's an > interesting question. Basically, can we do server-only operations? > > -JM > > > -- > > Hello, > > I am currently using GlusterFS version 3.5 with two bricks. What I > currently do is mounting the whole storage in some Linux clients (RedHat) > through fuse.glusterfs that (I think) uses NFS in the background. > What I would like to do is copying a file from a directory to another one > in the storage in the quickest way. Using a "cp file1 file2" from my RedHat > client is not the best option because the data flows from the storage to my > RedHat client through the network and then back to the storage. I would > like instead to avoid this waste of time and copy the file directly from > the 1st directory to the 2nd one. So, in a nutshell, I would like to have > file1 -> file2 , instead of file1 -> RedHatclient -> file2 > Do you think is it possible, for example using libgfapi? Any example to > show me? > Thank you in advance and best regards, > > *Giacomo Fazio* > IT Engineer > > Tel. +41 91 910 7690 > E-mail: giacomo.fa...@wcpmediaservices.com | Web: > www.wcpmediaservices.com > > Europe Office: Via Zurigo 35, 6900 Lugano, Switzerland > USA Office: 7083 Hollywood Boulevard Los Angeles, CA 90028 > > > ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Question about file copy through libgfapi
Thanks, Giacomo. I'm sending this to the gluster-devel list - it's an interesting question. Basically, can we do server-only operations? -JM - Original Message - > Hello, > I am currently using GlusterFS version 3.5 with two bricks. What I currently > do is mounting the whole storage in some Linux clients (RedHat) through > fuse.glusterfs that (I think) uses NFS in the background. > What I would like to do is copying a file from a directory to another one in > the storage in the quickest way. Using a "cp file1 file2" from my RedHat > client is not the best option because the data flows from the storage to my > RedHat client through the network and then back to the storage. I would like > instead to avoid this waste of time and copy the file directly from the 1st > directory to the 2nd one. So, in a nutshell, I would like to have file1 -> > file2 , instead of file1 -> RedHatclient -> file2 > Do you think is it possible, for example using libgfapi? Any example to show > me? > Thank you in advance and best regards, > Giacomo Fazio > IT Engineer > Tel. +41 91 910 7690 > E-mail: giacomo.fa...@wcpmediaservices.com | Web: www.wcpmediaservices.com > Europe Office: Via Zurigo 35, 6900 Lugano, Switzerland > USA Office: 7083 Hollywood Boulevard Los Angeles, CA 90028 ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] About file descriptor leak in glusterfsd daemon after network failure
Yes, that is another copy. We are testing and reviewing the patch codes, will try some other scenarios at the same time. The result will inform out when solution confirmed. Thanks again for your reply. Jaden Liang > 在 2014年8月21日，17:00，Niels de Vos 写道： > > It seems that this email was sent twice? Just in case you missed my > response to the other one, here it is: > - > http://supercolony.gluster.org/pipermail/gluster-devel/2014-August/041972.html > > Niels > >> On Wed, Aug 20, 2014 at 07:13:21PM +0800, Jaden Liang wrote: >> Hi gluster-devel team, >> >> We are running a 2 replica volume in 2 servers. One of our service daemon >> open a file with 'flock' in the volume. We can see every glusterfsd daemon >> open the replica files in its own server(in /proc/pid/fd). When we pull off >> the cable of one server about 10 minutes then re-plug in. We found that the >> glusterfsd open a 'NEW' file descriptor while still holding the old one >> which is opened in the first file access. >> >> Then we stop our service daemon, but the glusterfsd(the re-plug cable one) >> only closes the new fd, leave the old fd open, we think that may be a fd >> leak issue. And we restart our service daemon. It flocked the same file, >> and get a flock failure. The errno is Resource Temporary Unavailable. >> >> However, this situation is not replay every time but often come out. We are >> still looking into the source code of glusterfsd, but it is not a easy job. >> So we want to look for some help in here. Here are our questions: >> >> 1. Has this issue been solved? Or is it a known issue? >> 2. Does anyone know the file descriptor maintenance logic in >> glusterfsd(server-side)? When the fd will be closed or held? >> >> Thank you very much. >> >> -- >> Best regards, >> Jaden Liang > >> ___ >> Gluster-devel mailing list >> Gluster-devel@gluster.org >> http://supercolony.gluster.org/mailman/listinfo/gluster-devel ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Change in glusterfs[master]: Regression test portability: mktemp
On 21/08/2014, at 1:07 AM, Harshavardhana wrote: > On Wed, Aug 20, 2014 at 2:49 PM, Justin Clift wrote: >> Any ideas? >> >> > > Avati just fixed it > > We had to run 'git gc' directly on the gerrit server - gerrit gc > failed (could be a gerrit bug). Avati, did you make a backup of the /review/ directory before doing this? It looks like the "git gc" command was run as root instead of review user, so the permissions of the git dirs under /review/ have gone weird, and Gerrit looks to have done bad things to itself from there (eg internal Gerrit corruption) Misc is trying to resolve it atm, but a backup of /review/ dir would be a good thing to have atm. :) + Justin -- GlusterFS - http://www.gluster.org An open source, distributed file system scaling to several petabytes, and handling thousands of clients. My personal twitter: twitter.com/realjustinclift ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] About file descriptor leak in glusterfsd daemon after network failure
It seems that this email was sent twice? Just in case you missed my response to the other one, here it is: - http://supercolony.gluster.org/pipermail/gluster-devel/2014-August/041972.html Niels On Wed, Aug 20, 2014 at 07:13:21PM +0800, Jaden Liang wrote: > Hi gluster-devel team, > > We are running a 2 replica volume in 2 servers. One of our service daemon > open a file with 'flock' in the volume. We can see every glusterfsd daemon > open the replica files in its own server(in /proc/pid/fd). When we pull off > the cable of one server about 10 minutes then re-plug in. We found that the > glusterfsd open a 'NEW' file descriptor while still holding the old one > which is opened in the first file access. > > Then we stop our service daemon, but the glusterfsd(the re-plug cable one) > only closes the new fd, leave the old fd open, we think that may be a fd > leak issue. And we restart our service daemon. It flocked the same file, > and get a flock failure. The errno is Resource Temporary Unavailable. > > However, this situation is not replay every time but often come out. We are > still looking into the source code of glusterfsd, but it is not a easy job. > So we want to look for some help in here. Here are our questions: > > 1. Has this issue been solved? Or is it a known issue? > 2. Does anyone know the file descriptor maintenance logic in > glusterfsd(server-side)? When the fd will be closed or held? > > Thank you very much. > > -- > Best regards, > Jaden Liang > ___ > Gluster-devel mailing list > Gluster-devel@gluster.org > http://supercolony.gluster.org/mailman/listinfo/gluster-devel ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] update-link-count-parent POSIX xlator parameter
On 21/08/2014, at 6:04 AM, Prashanth Pai wrote: > Hi, > > I recently came across this when I was looking for various ways to convert > GFID to Path[1]. > I have tested "build-pgfid" option for basic sanity. It's documented in the > commit msg of change[2]. Found one small issue[3]. There could be others. > Users should be aware that these xattrs generated only for newly created > dirs/files and are not built for already existing dirs/files. > > [1]: > https://github.com/prashanthpai/sof-object-listing/blob/master/changelog/gfid-to-path.md > [2]: http://review.gluster.org/5951 > [3]: http://review.gluster.org/8352 Ahhh, this should be useful for GlusterFlow, assuming I ever get around to working on that again. ;) + Justin -- GlusterFS - http://www.gluster.org An open source, distributed file system scaling to several petabytes, and handling thousands of clients. My personal twitter: twitter.com/realjustinclift ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] [Gluster-users] Our plan to get bugs fixed quicker, and features implemented sooner
CC new gluster-devel@gluster.org mailing list. Pranith On 08/21/2014 12:42 PM, Lalatendu Mohanty wrote: I hope the subject line have increased your curiosity to go through the email :). As a community, we are looking for contributors for GlusterFS bug triage and hopefully this mail will give you enough motivation for it. As mentioned in the subject , bug triage will help to get bugs fixed quicker, and features implemented sooner. If you are not sure what bug triage means, please refer the gluster wiki page [1] for bug triage. Here are few questions and answers to help you if this is something you should do. * Q: Why we need to do bug triage? * A: It reduces the time between reporting a bug and the availability of a fix enormously. o Because many developers have bad response times for new bugs that are not pointed out to them. When well triaged bugs get assigned to right developers, the response time improves. o Also developers work mainly on writing bug fixes and implementing new features. Which in turn results in to spending (too little) time on bug triaging. * Q: I am just a GlusterFS user. Why bug triage will help me? * A: It will increase your understanding of GlusterFS, current issues in GlusterFS, increase the interaction between developers, community and triager. It will also help filing better bugs too. The better the bug report, the easier it is for a developer to write a fix. * Q: Do you run GlusterFS in production? * A: If your answer is yes, then bug triage is the right platform for you to raise the importance of bugs. Bug triage will also help you know existing issues in the version of GlusterFS you are using, help you to know existing issues in a new feature. So you will be in a better position to decide if a feature is production ready or not. * Q: I want to contribute to GlusterFS. Will bug triage help? * A: Yes, it is an awesome place to start. You will get to know about all the components in GlusterFS along with issues in each of them. This knowledge will help you to do better testing, development (bug fixing) etc. Also you will interact with developers while triaging bugs. You can use these interactions to ask more detailed questions. * Q: How can I triage bugs of GlusterFS? * A: The wiki page [1] is the right place start. We are starting up a bi-weekly/weekly triage meeting in #gluster-meeting on Freenode. There would be another mail with details about the meeting. You can join the meeting and interact with other triagers. Please don't hesitate to hit the reply button if you have any question on this. We would love to hear your suggestions/feed back :). [1] http://www.gluster.org/community/documentation/index.php/Bug_triage Thanks, On behalf of the bug triage team #gluster-dev, #gluster on Freenode ___ Gluster-users mailing list gluster-us...@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-users ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
