Perl 6 - the future is here, just unevenly distributed

IRC log for #gluster-dev, 2014-01-13

| Channels | #gluster-dev index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:58 yinyin joined #gluster-dev
01:11 hagarth joined #gluster-dev
01:50 yinyin joined #gluster-dev
02:03 mohankumar joined #gluster-dev
02:10 mohankumar joined #gluster-dev
02:23 kshlm joined #gluster-dev
02:32 badone joined #gluster-dev
02:37 bala joined #gluster-dev
02:41 kanagaraj joined #gluster-dev
02:57 bala joined #gluster-dev
03:11 bharata-rao joined #gluster-dev
03:26 aravindavk joined #gluster-dev
03:37 shubhendu joined #gluster-dev
03:50 itisravi joined #gluster-dev
03:55 ababu joined #gluster-dev
04:06 raghu joined #gluster-dev
04:18 yinyin joined #gluster-dev
04:27 kdhananjay joined #gluster-dev
04:33 ppai joined #gluster-dev
04:35 pk joined #gluster-dev
04:54 ndarshan joined #gluster-dev
05:03 pk left #gluster-dev
05:04 shyam joined #gluster-dev
05:36 pk joined #gluster-dev
05:48 lalatenduM joined #gluster-dev
06:06 hagarth joined #gluster-dev
06:55 hagarth joined #gluster-dev
07:53 hagarth joined #gluster-dev
08:15 Maxence joined #gluster-dev
08:42 spandit joined #gluster-dev
08:50 raghu joined #gluster-dev
08:56 shubhendu joined #gluster-dev
09:02 kanagaraj joined #gluster-dev
09:37 kanagaraj joined #gluster-dev
10:24 raghu joined #gluster-dev
10:29 shubhendu joined #gluster-dev
10:31 shubhendu joined #gluster-dev
10:33 ndevos hagarth: not sure if I put you on CC on my nightly test-packages email: http://www.gluster.org/pipermail/gluster-infra/2014-January/000043.html
10:34 hagarth ndevos: have seen that email.. will chime in on the thread
10:35 ndevos hagarth: okay, thanks!
10:39 pk ndevos: what is this mail alias?
10:39 pk ndevos: what happens in there?
10:40 ndevos pk: gluster-infra@gluster.org, and it is pretty quiet in there... but hagarth had an AI to write there about nightly test-packages
10:42 pk ndevos: hmm...
10:49 pk hagarth: ping
10:49 hagarth pk: pong
10:50 pk hagarth: remember the 3.4 issue we debugged with one of the guys on Thursday night?
10:50 hagarth pk: yes
10:52 pk hagarth: I sent the patch upstream....http://review.gluster.org/6691
10:52 hagarth pk: cool, we can merge that in
10:53 pk we wanted to provide him with a build....
10:54 pk hagarth: submitting it for regression...
10:54 hagarth pk: yeah, please go ahead
10:55 pk hagarth: who provides builds? you or kaleb?
10:56 hagarth pk: I can trigger a build
10:57 pk hagarth: I will update the bug then...
10:59 hagarth pk: ok
11:07 spandit joined #gluster-dev
11:20 pk hagarth: ping
11:21 pk hagarth: What is the procedure for community to say some bug is very important to be fixed? How do they escalate it?
11:24 bala joined #gluster-dev
11:25 hagarth pk: mailing list + bugzilla updates
11:26 pk hagarth: How do we track them?
11:27 hagarth pk: backport wishlist is being used for 3.4
11:27 hagarth pk: for 3.5, there is a tracker bug
11:27 pk hagarth: Hmm...
11:28 pk hagarth: The following bug is an annoying bug 847821. I wonder how to make sure people look into this bug...
11:28 glusterbot Bug https://bugzilla.redhat.com:443/show_bug.cgi?id=847821 low, medium, ---, rabhat, ASSIGNED , After disabling NFS the message "0-transport: disconnecting now" keeps appearing in the logs
11:29 hagarth pk: I have a patch for his
11:29 hagarth s/his/this/
11:29 pk hagarth: nice nice... post it please, I will review
11:29 edward2 joined #gluster-dev
11:29 pk hagarth: I would still like to know what the procedure is for people to look into these issue, if there is no such thing we should come up with such a procedure...
11:30 ndevos pk: is setting priority/severity in the bug not sufficient?
11:31 hagarth pk: it has a -1, i just need to find some time to clean it up and send it again - http://review.gluster.org/6293
11:31 hagarth pk: do you have any ideas to evolve a process for this?
11:32 pk hagarth: thinking
11:32 pk hagarth: Goal is for these things to end up in action items for the next sprint for the respective devs
11:34 pk hagarth: Is there a document for debugging using gluster volume profile?
11:34 hagarth pk: regular bug triages should also help
11:34 hagarth pk: our admin guide talks about volume profile and how it can be used
11:35 hagarth but I doubt if the content is good enough for debugging
11:36 hagarth pk: usually if something is broken badly i.e. in need of attention, we hear it from the community.
11:37 pk hagarth: See the problem I always find in helping users is... following up
11:37 pk hagarth: Some users are not responsive...
11:38 pk hagarth: I generally need to keep poking to get what I need to go further with debugging
11:38 hagarth pk: if users are not responsive, it becomes a hard case to address. It usually helps if we pay attention to a bug as soon as it is logged.
11:38 pk hagarth: Once you find root cause we can add it to sprint... otherwise it will be a problem
11:40 pk hagarth: I think we should come up with documents with things that need to be attached to bug when a bug is filed. Most of the times it is the lack of info that needs to be gathered by asking them...
11:41 pk hagarth: We should tackle this problem again after this document is made and submitted in gluster-users/gluster-devel
11:41 pk hagarth: I think sateesaran was working on something similar. Let me check with him and see how it is coming along...
11:41 hagarth pk: absolutely, that will help quite a bit. sosreport could be a good tool to start with.
11:42 pk hagarth: I thought sos-reports are not available on community releases?
11:42 lalatenduM hagarth, there is already a bug for Coverity issues on master https://bugzilla.redhat.com/show_bug.cgi?id=789278
11:42 glusterbot Bug 789278: high, medium, ---, rabhat, ON_DEV , Coverity static analysis bug
11:43 hagarth pk: https://github.com/sosreport/sosreport/blob/master/sos/plugins/gluster.py
11:43 hagarth lalatenduM: cool, do you want to circulate that bug id on devel?
11:44 lalatenduM hagarth, sure, I think it should be assigned to you as you are looking after this
11:44 hagarth for distros that don't have sosreport, we could look at having a tgz of /var/log/glusterfs
11:44 pk hagarth: yeah
11:44 pk hagarth: Why not develop cli to do these things?
11:44 hagarth lalatenduM: yeah, please do or feel free to assign it to yourself
11:44 lalatenduM hagarth, cool
11:45 hagarth pk: we could do that too
11:46 hagarth will bbiab, later everyone
11:46 pk hagarth: cool. I will first gather the document with info that needs to be added to the bug
11:46 hagarth pk: sure
11:47 pk ok I am logging off
11:47 pk hagarth: cya
11:47 hagarth would like some review on this patch  - http://review.gluster.org/#/c/6633/
11:47 kshlm joined #gluster-dev
12:12 kkeithley joined #gluster-dev
12:13 itisravi joined #gluster-dev
12:45 bfoster joined #gluster-dev
12:53 hagarth joined #gluster-dev
13:43 primechuck joined #gluster-dev
13:59 ira joined #gluster-dev
14:24 ababu joined #gluster-dev
14:49 jobewan joined #gluster-dev
15:06 jclift joined #gluster-dev
15:49 _Bryan_ joined #gluster-dev
15:54 Technicool joined #gluster-dev
16:07 lpabon joined #gluster-dev
16:09 johnmark ndevos: ping
16:10 johnmark ndevos: cloudstack peeps are asking about you
16:13 ndevos johnmark: hey!
16:16 johnmark ndevos: howdy :)
16:18 ndevos johnmark: testing cloudstack is quite time consuming... but the patches on the forge seem to work for me
16:18 ndevos most of the time
16:19 ndevos but, I'm a CloudStack noob, and have very little clue about what I'm doing
16:31 johnmark ndevos: ah, there was a review of your patches, and they were waiting for your response
16:39 kanagaraj joined #gluster-dev
16:41 ndevos johnmark: I hope to be able to post updated (and more complete) patches soon
16:41 johnmark ndevos: thanks :)
16:41 johnmark ndevos: can you send a note to cloudstack-dev? they're targeting the 4.4 release
16:41 ndevos johnmark: if you know anyone who would like to test, that would help though :)
16:41 johnmark ndevos: ok, thanks
16:44 ndevos johnmark: I'll try to get to that tomorrow
17:15 bala joined #gluster-dev
17:23 bala1 joined #gluster-dev
18:03 badone joined #gluster-dev
18:25 badone joined #gluster-dev
18:47 ilbot3 joined #gluster-dev
18:47 topic for #gluster-dev is now Gluster Development Channel - http://gluster.org | For general chat go to #gluster | Patches - http://review.gluster.org/ | Channel Logs - https://botbot.me/freenode/gluster-dev/ & http://irclog.perlgeek.de/gluster-dev/
19:22 jclift Hmmm, Gluster.org blog search is broken.
19:22 jclift eg: http://www.gluster.org/blog/page/3/  Then type a search term in and hit enter -> 404 Page not found
21:01 jclift left #gluster-dev

| Channels | #gluster-dev index | Today | | Search | Google Search | Plain-Text | summary