Perl 6 - the future is here, just unevenly distributed

IRC log for #gluster-dev, 2014-07-24

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

All times shown according to UTC.

Time Nick Message
03:02 bharata-rao joined #gluster-dev
03:38 atinmu joined #gluster-dev
03:43 kanagaraj joined #gluster-dev
03:44 shubhendu joined #gluster-dev
03:54 itisravi joined #gluster-dev
04:16 awheeler joined #gluster-dev
04:32 anoopcs joined #gluster-dev
04:40 jiffin joined #gluster-dev
04:40 spandit joined #gluster-dev
04:42 Rafi_kc joined #gluster-dev
05:16 nishanth joined #gluster-dev
05:18 ppai joined #gluster-dev
05:32 lalatenduM joined #gluster-dev
05:44 kdhananjay joined #gluster-dev
05:45 aravindavk joined #gluster-dev
05:53 lalatenduM hchiramm, pm
05:53 hchiramm lalatenduM, sure
05:55 hchiramm lalatenduM++
05:55 glusterbot hchiramm: lalatenduM's karma is now 11
06:00 awheeler joined #gluster-dev
06:08 raghu joined #gluster-dev
06:12 vpshastry joined #gluster-dev
07:09 kanagaraj joined #gluster-dev
07:20 aravindavk joined #gluster-dev
07:48 awheeler joined #gluster-dev
07:59 xavih lalatenduM: I've created a clone of bug 789278 to track coverity scan issues for 3.6 branch. The new bug id is 1122834
07:59 glusterbot Bug https://bugzilla.redhat.com​:443/show_bug.cgi?id=789278 high, medium, ---, vbellur, ON_DEV , Issues reported by Coverity static analysis tool
08:07 aravindavk joined #gluster-dev
08:08 deepakcs joined #gluster-dev
08:16 awheeler joined #gluster-dev
08:24 lalatenduM xavih, do u want to keep this as tracker bug for 3.6 coverity issues?
08:25 lalatenduM xavih++ cool, we make it a tracker bug
08:25 glusterbot lalatenduM: xavih's karma is now 4
08:25 lalatenduM s/make/will make/
08:28 xavih lalatenduM: this is what we talked on tuesday, isn't it ? or did I misunderstand ?
08:29 lalatenduM xavih, yup, you are right. I just added a "tracking" keyword, so that ndevos scripts does not close it :) automatically
08:29 xavih lalatenduM: good :)
08:30 xavih lalatenduM: not sure if it should also be set into state ON_DEV, like the other one, but I don't have privileges to do that
08:32 lalatenduM xavih, actually everyone should have all privileges , not sure why bugzilla is access is weird, may be this is something we need to make sure community members are getting all permissions
08:33 lalatenduM xavih, I think we should assign it to the 3.6 branch maintainer
08:33 lalatenduM which is not decided till now
08:33 xavih lalatenduM: the only thing I can do is close it :P
08:33 lalatenduM xavih, :) LOL
08:34 xavih lalatenduM: yes, I think it should be assigned to the maintainer once decided
08:34 lalatenduM xavih, cool
08:48 vpshastry joined #gluster-dev
08:50 shubhendu joined #gluster-dev
08:54 nishanth joined #gluster-dev
09:14 kshlm joined #gluster-dev
09:15 swebb joined #gluster-dev
09:24 shubhendu joined #gluster-dev
09:26 nishanth joined #gluster-dev
09:31 Rafi_kc joined #gluster-dev
09:32 vpshastry joined #gluster-dev
09:38 pranithk joined #gluster-dev
09:45 hchiramm joined #gluster-dev
10:10 hchiramm joined #gluster-dev
10:17 atinmu joined #gluster-dev
11:16 shyam joined #gluster-dev
11:46 ppai joined #gluster-dev
11:57 shubhendu joined #gluster-dev
12:01 hagarth joined #gluster-dev
12:02 hagarth1 joined #gluster-dev
12:07 kdhananjay joined #gluster-dev
12:16 bala joined #gluster-dev
12:30 edward1 joined #gluster-dev
12:39 tdasilva joined #gluster-dev
13:01 awheeler joined #gluster-dev
13:01 shyam joined #gluster-dev
13:09 shyam joined #gluster-dev
13:15 _Bryan_ joined #gluster-dev
13:17 krishnan_p joined #gluster-dev
13:21 kkeithley1 joined #gluster-dev
13:23 bala1 joined #gluster-dev
13:34 tdasilva joined #gluster-dev
13:37 lalatenduM joined #gluster-dev
13:39 lalatenduM kkeithley, I have a question regarding 3.4.5, is it a good time to ask
13:39 kkeithley_ sure
13:40 bala joined #gluster-dev
13:41 kkeithley_ lalatenduM: ^^^
13:48 hchiramm lalatenduM, ^^^
13:48 lalatenduM kkeithley, listening to sayan...give me some minutes :)
13:48 kkeithley_ sure
14:04 shyam joined #gluster-dev
14:05 lalatenduM kkeithley, I compared spec files between spec file in release-3.4 branch vs spec file in 3.4.5beta2 rpm
14:06 lalatenduM kkeithley, there is difference , will pastebin the difference
14:06 lalatenduM kkeithley, http://www.fpaste.org/120487/62107841/
14:07 lalatenduM kkeithley, the changes got introduced in this patch http://review.gluster.org/#/c/6058/3/glusterfs.spec.in
14:07 lalatenduM kkeithley, I checked this on 3.4.4 GA the change is not thr
14:07 lalatenduM but it was in 3.4 branch
14:07 lalatenduM hchiramm, ^
14:09 hchiramm I think when libgfapi python bindings introduced  in glusterfs source , the init.py was taken care..
14:09 hchiramm may be we dropped these entries from glusterfs.spec by that time..
14:10 hchiramm not sure the above assumption is right..
14:14 kkeithley_ hmmm.  I'm not really sure. As long as we're still shipping gfapi I think we need to touch the __init__.py. And we are still shipping gfapi in 3.4, right?
14:15 hchiramm yep, glupy and gfapi need init.py
14:15 * kkeithley_ is trying to keep dist-git glusterfs.spec straight in my mind versus upstream git repo glusterfs.spec.in
14:15 kkeithley_ in all the branches
14:16 lalatenduM kkeithley, hchiramm looks like I should take the change, what say?
14:16 shyam joined #gluster-dev
14:18 hchiramm lalatenduM, definitely no harm afaict
14:19 * hchiramm :  When are we going to stop 3.4 releases ?
14:19 * hchiramm : :)
14:21 lalatenduM hchiramm, thats a interesting question EOL for 3.4? but I am inclined to this till community need it
14:21 lalatenduM s/to/ to do/
14:21 hchiramm I think with the first release of 3.6, we can drop 3.4 . Isnt it ? :)
14:22 lalatenduM kkeithley, waiting for a confirmation from you, should I take the change?
14:22 lalatenduM hchiramm, not sure:)
14:28 anoopcs joined #gluster-dev
14:28 wushudoin joined #gluster-dev
14:38 ndk joined #gluster-dev
14:43 kkeithley_ Yes, I think we'll EOL 3.4 once 3.6 ships. Pretty sure
14:43 kkeithley_ I don't think we can take the __init__.py out of 3.4.
14:44 krishnan_p joined #gluster-dev
14:44 lalatenduM kkeithley, cool,
14:45 deepakcs joined #gluster-dev
14:47 hchiramm kkeithley++ lalatenduM++
14:47 glusterbot hchiramm: kkeithley's karma is now 4
14:47 glusterbot hchiramm: lalatenduM's karma is now 12
15:03 kanagaraj joined #gluster-dev
15:12 jobewan joined #gluster-dev
15:22 sickness anyone already tried the ec xlator? =_)
15:28 JustinClift lalatenduM hchiramm kkeithley_: I think it'd be a bad idea Community wise to drop 3.4 when 3.6 is released.
15:28 JustinClift We're still finding serious bugs in 3.5.
15:28 lalatenduM JustinClift, +1
15:28 lalatenduM JustinClift, I agree
15:29 JustinClift Lets consider dropping 3.4 support when both 3.5 and 3.6 are pretty stable.
15:29 lalatenduM JustinClift, atleast need to see 3.5.2 , how it is working
15:29 lalatenduM on field
15:29 JustinClift ...and by "consider" I mean "consider".  Not lets drop it ;)
15:29 JustinClift lalatenduM: +1
15:30 lpabon this is probably a stupid question, but... the new gluster.org website ( http://gluster.org/community/index.html ) says that the irc channel is on irc.gnu.org .. is that a proxy to freenode or an actual server?
15:30 JustinClift lpabon: It's a cname to the freenode servers
15:30 JustinClift So, ends up here too
15:30 lpabon JustinClift, cool
15:30 * JustinClift got confused by this initially as well ;)
15:32 kkeithley_ I don't disagree. Not in principle anyway. But historically, as a matter of policy, we have not had three branches in active support.
15:33 kkeithley_ IIRC we contemplated doing one more 3.3.x release, but ultimately decided against it because we has just shipped 3.5.0.
15:38 JustinClift kkeithley_: Yeah, it's a decent policy when the software is pretty bug free, and upgrades are fairly safe.
15:38 JustinClift I strongly argue for changing the policy in the short term. ;)
15:39 ndk` joined #gluster-dev
15:42 hchiramm JustinClift, I see it as an opportunity  to ask users to upgrade
15:42 JustinClift hchiramm: It absolutely is
15:42 lalatenduM BTW we are talking abt storage here :)
15:42 hchiramm otherwise they will be sticking with a version for long time and our last releases will take time to stabilize
15:42 JustinClift hchiramm: If the software release they're going _to_ isn't very safe and stable though, all that'll do is generate unhappy users and bad PR
15:43 lalatenduM hchiramm, goeal is create better software :)
15:43 lalatenduM s/goeal/goal/
15:43 kkeithley_ All good points
15:43 hchiramm lalatenduM, the goal will be achieved only when more people are using it ..
15:43 hchiramm :)
15:43 lalatenduM hchiramm, more people will use when it stable enough, it is chicken egg problem
15:43 JustinClift hchiramm: Yes and no.  We can definitely knock off more bugs from things before telling people it's stable
15:44 lalatenduM we need to have a balance
15:44 JustinClift Yep
15:44 kkeithley_ and like I said, I don't disagree, but we need to weigh the amount of work and be cognizant that many of us have a day job too where we have other priorities
15:44 lalatenduM we can't tell user to upgrade if we there is some data loss bugs present in the release
15:45 hchiramm JustinClift, atleast in some versions we have to sacrifice and start making good product from there on.. :)
15:45 JustinClift hchiramm: As an example, one of the places doing significant testing for 3.5 series (which has lead to many of the important fixes for 3.5.1 and .2) is Corvid Tech.  They're not using it in production, but are instead testing it extensively.  With hundreds of nodes at a time.
15:45 lalatenduM kkeithley, I agree with u
15:45 hchiramm kkeithley++ yeah. maintaining 3 branches ( otherthan master) will be really difficult ..
15:45 glusterbot hchiramm: kkeithley's karma is now 5
15:46 JustinClift hchiramm: We'll definitely be asking them to test 3.6 when it's a bit further along.  (no idea if they'll want to, but we'll at least ask)
15:46 hchiramm JustinClift, thats good to hear.. but by the time 3.6 is out we should hve more stable 3.5 version..
15:46 JustinClift kkeithley_: Yeah, I understand what you mean. ;)
15:46 JustinClift hchiramm: Yeah, I'm hoping strongly that's the case.
15:46 kkeithley_ on a separate topic, I've got several static analyses running now. Probably you saw the email on gluster-devel list. Nightly results are posted at http://download.gluster.org/pub/g​luster/glusterfs/static-analysis/
15:47 kkeithley_ people looking for "easy fixes" as a way of participating can probably find something in there
15:48 nishanth joined #gluster-dev
15:48 lalatenduM kkeithley, yup saw the mail
15:48 lalatenduM kkeithley++
15:48 glusterbot lalatenduM: kkeithley's karma is now 6
15:48 JustinClift kkeithley_: Out of curiosity, how long do these take to run?
15:49 hchiramm all_good_points++
15:49 glusterbot hchiramm: all_good_points's karma is now 1
15:49 * JustinClift wonders if it'd be practical to do them automatically on each new Gerrit CR, and somehow extract from that any _new_ things introduced by the CR
15:50 JustinClift Might be a real pita to implement, but just wondering. ;)
15:50 lalatenduM JustinClift, actually with sonar we can do that I guess, that is  hagarth1's idea
15:50 lalatenduM that brings me to a question
15:51 kkeithley_ they vary. coverity runs take about 20-30 minutes.
15:51 kkeithley_ clang --analyze is 15-20 minutes. the others are shorter
15:51 lalatenduM hchiramm, what is the plan to update gerrit version in r.g.o
15:51 JustinClift lalatenduM: Sonar?
15:51 hchiramm lalatenduM, JustinClift found some one to do that :)
15:51 JustinClift Oh, SonarQube?
15:52 kkeithley_ the issue with coverity is that we share one license with all of Red Hat, and we don't want to hog the license
15:52 lalatenduM JustinClift, yeah http://www.sonarqube.org/
15:52 JustinClift ahhh
15:52 JustinClift That's interesting.
15:53 kkeithley_ And there are already other coverity scans of glusterfs running internally.
15:53 lalatenduM JustinClift, sonar does not work with current gerrit , the gerrit version needs to be upgraded
15:53 JustinClift When Louis put the sonar instance online for the java stuff, I got a bit enthused and asked them if they'd sponsor us / grant us a free C/C++ license for Gluster (since their C/C++ stuff isn't free)
15:53 glusterbot JustinClift: C/C's karma is now 1
15:53 glusterbot JustinClift: C/C's karma is now 2
15:54 JustinClift lalatenduM: Interesting
15:54 lalatenduM JustinClift, I think we have a community version
15:54 JustinClift The CEO of SonarQube said they'd happily give us a license for the C/C++ one
15:54 glusterbot JustinClift: C/C's karma is now 3
15:54 JustinClift But Louis wasn't interested in looking after it
15:54 JustinClift So we haven't followed up
15:55 JustinClift lalatenduM: That's interesting about Sonar not working with the current gerrit.
15:55 lalatenduM JustinClift, hmm interesting , it is like bitkeeper giving free license for Linux :)
15:55 JustinClift I'd not yet seen anything with the current Gerrit version (apart from bugs), which are definitely a cause of problems for us
15:55 JustinClift lalatenduM: No argument there
15:55 JustinClift ;)
15:56 lalatenduM :)
15:56 JustinClift AFAIK, there isn't a Community version for the C/C++ plugin/extenstion/whatever
15:56 glusterbot JustinClift: C/C's karma is now 4
15:56 JustinClift (that may have changed tho)
15:56 lalatenduM JustinClift, not what license they are using , let me check
15:56 JustinClift lalatenduM: This might give us the impetus to upgrade Gerrit though
15:56 * JustinClift will ask misc about it
15:57 hchiramm JustinClift++
15:57 glusterbot hchiramm: JustinClift's karma is now 4
15:57 lalatenduM JustinClift, it is LGPLv3 , so I think the code should be available for the customers
15:57 JustinClift lalatenduM: Want me to forward you (and Vijay?) and details for the Sonar license stuff, so either of yourselves can follow up?
15:57 JustinClift lalatenduM: Ahh, interesting
15:57 JustinClift lalatenduM: Good work :)
15:57 JustinClift lalatenduM++
15:57 glusterbot JustinClift: lalatenduM's karma is now 13
15:57 lalatenduM unless they are providing it as separate plugin :)
15:58 JustinClift nfi
15:58 lalatenduM JustinClift, ^
15:58 lalatenduM yeah
15:58 JustinClift I'll forward you the stuff.  You and Vijay can figure it out. :)
15:58 lalatenduM JustinClift, ok cool
15:58 lalatenduM JustinClift, we get the code, we can try compiling it :) hchiramm what say
15:59 lalatenduM s/we get/ if we get/
16:00 hchiramm no objection :) lalatenduM
16:00 hchiramm but if there is an option to upgrade gerrit
16:01 hchiramm lets do that first ...
16:01 lalatenduM hchiramm+1
16:01 JustinClift We'll probably need to try it out in a VM or something first, to see if the upgrade "just works"
16:01 JustinClift I'd be nice to not have to re-install it
16:01 JustinClift (same thought for Jenkins too really)
16:02 hchiramm JustinClift, u got someone to do that  . Isnt it ?
16:02 hchiramm to upgrade gerrit and jenkins ..
16:04 JustinClift hchiramm: We're asking misc (OSAS Team SysAdmin) to do it
16:04 hchiramm cool .. thanks
16:04 JustinClift hchiramm: He's working through the infrastructure, figuring out what's where
16:05 hchiramm oh.. ok ..
16:05 JustinClift hchiramm: He's also started putting stuff (eg slave setup) into Ansible
16:05 hchiramm \o/
16:05 JustinClift I don't think it's even close to ready, but he's making progress
16:05 hchiramm k
16:06 JustinClift kkeithley_ lalatenduM: With the new Static Analysis pages, would either of you have time to add a link to them to the main / front Community Wiki "Development" page ?
16:06 JustinClift Gah.  Email isn't working for me. :/
16:12 _Bryan_ joined #gluster-dev
16:16 kkeithley_ JustinClift: which page is that?
16:17 JustinClift http://www.gluster.org/community/d​ocumentation/index.php/Developers
16:18 lalatenduM kkeithley, I will do that,
16:18 JustinClift Tx
16:18 kkeithley_ lalatenduM: okay
16:18 lalatenduM ok
16:18 JustinClift I'd do it, but I'm in the middle of remote UK atm, with no access to my wiki password
16:19 lalatenduM JustinClift, what abt the page http://www.gluster.org/community/document​ation/index.php/Fixing_Issues_Reported_By​_Tools_For_Static_Code_Analysis#Coverity
16:19 JustinClift lalatenduM: Haven't looked at it yet.  Will take a look in a few minutes
16:19 lalatenduM JustinClift, I think thats the right place
16:19 JustinClift k.
16:20 JustinClift Is that "Fixing Issues Reported ..." page linked to from the main Developers page?
16:20 JustinClift lalatenduM: If not, please add it.
16:20 * JustinClift is just attemping to have stuff somewhat easy to find from one place for new + experienced developers
16:20 lalatenduM JustinClift, it is present in the documentation home page under developers
16:20 JustinClift Cool
16:21 JustinClift lalatenduM: here? http://www.gluster.org/community/d​ocumentation/index.php/Developers
16:21 JustinClift I'm probably being blind, can't see it
16:21 JustinClift Er... which heading is it under? :)
16:22 lalatenduM JustinClift, check http://www.gluster.org/commu​nity/documentation/index.php, under "Developers"
16:23 lalatenduM brb
16:23 JustinClift Ahhh, got it
16:23 JustinClift lalatenduM: Would you be ok to put it on the main Developers page too?
16:23 JustinClift There's no issue in having it linked to from multiple places
16:23 * JustinClift generally loads any page of the wiki, then clicks the "Developers" link on the left hand side
16:24 JustinClift In my head that's the main "Developers" page
16:24 JustinClift (other people likely have their own method) :)
16:27 JustinClift On a side note, I'm slightly worried about our internal version numbering for that gluster field where we report the version of gluster in use, for compatibility purposes
16:30 JustinClift Actually, looking at it again, I think there's nothing to worry about: http://www.gluster.org/community/docu​mentation/index.php/OperatingVersions
16:31 JustinClift For some reason I initially thought we couldn't go past 3.4.9 without hitting the end of the version numbering space for that
16:31 JustinClift Doesn't seem like an issue now I look at it again
16:56 pranithk joined #gluster-dev
16:57 lalatenduM JustinClift, cool I will update the Developers" page, but can't do it today, I am already late for may things today :(
17:00 JustinClift lalatenduM: No worries at all. :)
17:04 pranithk JustinClift: from when to when do you stay online? just curious :-)
17:10 JustinClift pranithk: It's really hard to tell recently
17:11 JustinClift pranithk: Today I had to get up early, get on a train to remote/rural UK
17:11 JustinClift I was able to send email in the morning while waiting at train station
17:11 JustinClift But no connectivity until about 1.5 hours ago
17:12 JustinClift ... and in 15 minutes I go back to the train station, to return to London tonight
17:12 JustinClift So, weird times for the next week or two as house moving gets done
17:17 ndk`` joined #gluster-dev
17:17 tdasilva joined #gluster-dev
17:25 pranithk JustinClift: got it :-)
17:25 pranithk JustinClift: but you still did not answer my question. What are the times?
17:46 shyam joined #gluster-dev
20:01 shyam joined #gluster-dev
20:33 bala joined #gluster-dev
20:55 kkeithley1 joined #gluster-dev
21:57 bala joined #gluster-dev
22:22 awheeler joined #gluster-dev
22:48 cogsu_ joined #gluster-dev
22:50 cogsu_ Hey guys, does anyone know if there is a magic way to get an fop to go to a certain brick from a translator in the client stack?  Basically I need the ability to get the result of a getxattr from each brick in the cluster and compare the values.
23:29 awheeler joined #gluster-dev
23:32 systemonkey joined #gluster-dev
23:43 JustinClift pranithk: So, I can't answer your question because the times are completely unpredictable and unstable atm.
23:43 JustinClift pranithk: For example, I just got home from remote UK about 20 mins ago. ;)
23:45 JustinClift cogsu_: The guys will probably start to arrive in IRC in about 5+ hours.  You might want to ask on gluster-devel if you can't stick around on IRC that long.
23:45 JustinClift (just saying)
23:45 JustinClift cogsu_: Oh, I mean "gluster-devel" the mailing list btw. :)
23:56 hagarth joined #gluster-dev

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