12:01:32 <ndevos> #startmeeting
12:01:32 <zodbot> Meeting started Tue Mar  3 12:01:32 2015 UTC.  The chair is ndevos. Information about MeetBot at http://wiki.debian.org/MeetBot.
12:01:32 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
12:01:42 <ndevos> #info Agenda: https://public.pad.fsfe.org/p/gluster-bug-triage
12:01:48 <ndevos> #topic Roll Call
12:02:01 <ndevos> Hello guys, please raise your hands when you're here!
12:02:08 <lalatenduM> o/
12:02:13 <hchiramm> \o
12:02:36 <ndevos> \o/
12:02:47 <lalatenduM> :)
12:02:57 <ndevos> kkeithley is still travelling, so he wont join
12:03:13 <ndevos> but, firemanxbr is listening in
12:03:47 <ndevos> and atinmu and rafi seem to be online too, maybe they participate today?
12:04:02 * atinmu is here :)
12:04:30 <ndevos> :)
12:04:38 <ndevos> #topic Action Items from last week(s)
12:04:39 <rafi> is here
12:04:46 <ndevos> #info subtopic: hchiramm will get version 3.6.2 in Bugzilla
12:05:16 * ndevos will skip the topics that are known to be not-done, or because hagarth isnt there
12:05:17 <hchiramm> ndevos, its done
12:05:31 <hchiramm> I gave an ack on this in last meeting as well :)
12:05:47 <ndevos> #info version 3.6.2 is in bugzilla, since before the last meeting
12:06:02 <ndevos> hchiramm: oh, sorry, I failed to update the agenda then :-/
12:06:11 <hchiramm> np though :)
12:07:11 <ndevos> #info subtopic: lalatenduM will look into automated coverity runs
12:07:19 <lalatenduM> ndevos, in progress
12:07:29 <lalatenduM> I mean work in progress
12:07:35 <ndevos> lalatenduM: okay, cool - anything that blocks you?
12:07:44 <lalatenduM> ndevos, nope
12:07:47 <ndevos> nice :)
12:08:22 <ndevos> and now, why we are all here for:
12:08:27 <ndevos> #topic Group Triage
12:08:42 <ndevos> there are 14 new bugs that need to be triaged: http://goo.gl/0IqF2q
12:08:50 <lalatenduM> ndevos, I think I had one more action item , no? :)
12:09:12 <ndevos> lalatenduM: you did? my agenda is old, so I just make things up along
12:09:44 <ndevos> lalatenduM: or, was it one of the items I assumed to be "not-done"?
12:09:53 <lalatenduM> ndevos, np
12:09:54 <firemanxbr> hiii :D
12:10:06 <firemanxbr> \o/
12:10:06 <ndevos> #chair lalatenduM
12:10:06 <zodbot> Current chairs: lalatenduM ndevos
12:10:24 <ndevos> lalatenduM: please #topic or #info your action item?
12:11:31 <lalatenduM> #info Using the nightly builds for automation is in progress. The CI system is making some progress. Once it is in place I will start consuming the builds
12:11:50 <lalatenduM> I mean the new CI system
12:12:04 <ndevos> what is the "new CI system"?
12:12:38 <lalatenduM> ndevos, I am working on a new Jenkins based CI system for RHS
12:13:04 <lalatenduM> ndevos, and the st job will be using nightly builds to run automation
12:13:05 <atinmu> lalatenduM, awesome
12:13:08 <firemanxbr> lalatenduM, I can help with this it
12:13:09 <lalatenduM> 1st*
12:13:10 <atinmu> lalatenduM++
12:13:22 <ndevos> lalatenduM: oh, okay, so some internal Red Hat systems will be used for upstream gluster testing?
12:13:29 * hchiramm locks 1196108
12:13:30 <lalatenduM> ndevos, yes
12:13:43 <firemanxbr> in my work I'm using Gerrit 2.10 + Jenkins 1.600 on CentOS 7
12:13:54 * hchiramm locks 1195947
12:14:10 <lalatenduM> firemanxbr, thanks. however it is internal to my work :(
12:14:19 <ndevos> lalatenduM: thats quite cool!
12:14:47 <firemanxbr> lalatenduM, okay, no problem, which can help I am available
12:15:17 <ndevos> lalatenduM: are there any plans to setup nightly testing on community managed hardware (when kkeithley has more servers connected)?
12:15:33 * hchiramm locks 1196949
12:15:54 <lalatenduM> ndevos, I dont have plans for that as of now
12:15:57 * ndevos informs hchiramm that he's ahead of the schedule :)
12:16:21 <ndevos> lalatenduM: okay, it would be cool to keep that in mind, and then get firemanxbr involved in that
12:16:22 * atinmu locks 1197631
12:16:41 * hchiramm : :)
12:17:00 <ndevos> I would like to see automated nightly tests of nfs-ganesha with gluster too, that would be great
12:17:19 <lalatenduM> ndevos, yes , Also another guy from community , I think Kiran is also interested something like this , firemanxbr can help us there
12:17:33 <ndevos> firemanxbr: have you done any jenkins jobs that involve setting up a cluster of multiple machines and clients?
12:17:43 * atinmu locks 1197260
12:18:05 * hchiramm locks 1197260
12:18:09 <hchiramm> ah..
12:18:20 <ndevos> lalatenduM: definitely sounds like a good way to attract more community users :)
12:18:40 <atinmu> hchiramm, u raced me
12:18:44 <atinmu> hchiramm, :)
12:18:48 <hchiramm> sorry for that
12:18:49 <hchiramm> :)
12:18:50 <firemanxbr> ndevos, yep
12:18:51 <hchiramm> atinmu++
12:18:59 <lalatenduM> ndevos, yeah
12:19:04 * atinmu releases 1197260
12:19:18 <lalatenduM> he have a test frame work for this too https://github.com/msvbhat/distaf
12:19:18 <ndevos> firemanxbr: oh, cool!
12:19:21 <firemanxbr> ndevos, I'm my working we using slaves auto provisioning, using ansible
12:19:38 <lalatenduM> firemanxbr, cool
12:19:38 * atinmu locks 1197185
12:19:41 <firemanxbr> ndevos, jenkins + ansible + foreman
12:20:00 <hchiramm> firemanxbr, good set :)
12:20:03 <ndevos> #info lalatenduM is working on nightly automated tests based on https://github.com/msvbhat/distaf
12:20:23 <lalatenduM> ndevos, nope thats not exactly right
12:20:31 <ndevos> #info firemanxbr uses Jenkins for automated cluster testing, using ansible for provisioning
12:20:31 <lalatenduM> ndevos, it is complicated :)
12:20:41 <firemanxbr> ndevos, lalatenduM workflow:> new job => if slave on, no up and running....
12:20:49 <lalatenduM> #info lalatenduM is working on nightly automated tests for upstream
12:21:03 <ndevos> lalatenduM: sure, I simplify things a little :D
12:21:24 <firemanxbr> lalatenduM, great source, congrats....
12:21:50 <lalatenduM> firemanxbr, ?? did not get you
12:22:18 <firemanxbr> lalatenduM, https://github.com/msvbhat/distaf
12:22:29 <lalatenduM> firemanxbr, thats not me :)
12:22:41 <lalatenduM> firemanxbr, this is me https://github.com/LalatenduMohanty
12:22:45 <hchiramm> msvbhat, ^^^
12:22:52 <hchiramm> firemanxbr, msvbhat is the one :)
12:22:57 <lalatenduM> yup
12:23:09 <firemanxbr> lalatenduM, ahh okay, I believe we wish use foreman for base provisioning, after ansible very cool and very simple
12:23:12 <ndevos> msvbhat: maybe you would like to move the distaf repo to github.com/gluster/distaf ?
12:23:30 <lalatenduM> ndevos, yup, i have already suggested msvbhat that
12:23:38 <ndevos> lalatenduM: ah, nice :)
12:23:54 <msvbhat> ndevos: yes, I was supposed to do it last Friday
12:24:19 <lalatenduM> firemanxbr, yes that looks fine (the work flow)
12:24:21 <firemanxbr> in my work's, all machines starting on source's, physical or virtual, we usign foreman for basic provisioning after using ansible.
12:24:21 * atinmu locks 1196223
12:24:24 <ndevos> msvbhat: cool, as long as you're planning that, I'm happy with it :D
12:24:24 <msvbhat> ndevos: I had a talk with JustinClift about the same. And will do it once the half-baked patch in my loacl repo is pushed
12:25:13 <firemanxbr> I talk with JustinClift for few day we have new Gerrit 2.10
12:25:38 <firemanxbr> I'm creating ansible for start on rackspace new vm for new gerrit
12:25:51 <firemanxbr> new version for testing....
12:25:54 <ndevos> firemanxbr: great!
12:26:17 <firemanxbr> in this moment I'm testing rackspace env
12:26:38 <ndevos> firemanxbr: maybe you can mention that in tomorrows meeting? that one is more about general topics
12:27:00 <firemanxbr> ndevos, okay :D
12:27:03 <ndevos> it would be a shame for all the others to miss out on that info
12:27:41 <ndevos> lalatenduM: is that all on your action items?
12:27:46 <lalatenduM> ndevos, yes
12:28:00 <ndevos> ok, lets try this again then
12:28:10 <ndevos> #topic Group Triage (take #2)
12:28:22 * atinmu feels that he is done with triaging
12:28:47 <ndevos> we have 14, no, 8 bugs that we need to triage
12:28:48 <lalatenduM> atinmu, nope we have 8 bugs remaining :)
12:28:50 <ndevos> http://goo.gl/0IqF2q is the list
12:28:55 * lalatenduM 1197631
12:29:23 <atinmu> lalatenduM, I've already done 4 :) So relaxing a bit :D
12:29:30 <ndevos> when you open a bug for triaging, mention it here so that there is an "irc lock" for it
12:29:51 <atinmu> ndevos, I did, din't I ?
12:30:04 <ndevos> atinmu: yes, you did
12:30:08 <lalatenduM> atinmu, I know you can do more :)
12:30:16 <ndevos> atinmu: but we were not at the topic yet :)
12:30:31 <ndevos> atinmu: *now* is the time to start the triaging :P
12:30:36 * ndevos locks 1196584
12:30:46 * lalatenduM locks 1196028
12:31:13 * ndevos locks 1196904
12:32:16 * ndevos locks 1195907
12:33:13 <lalatenduM> ndevos, https://bugzilla.redhat.com/show_bug.cgi?id=1196028
12:33:30 <ndevos> lalatenduM: what about it?
12:33:30 * atinmu locks 1196027
12:33:31 <lalatenduM> I think you should take a look
12:34:36 <ndevos> lalatenduM: ah, yes, I asked Prashanth to report that
12:34:49 <firemanxbr> about 1196027 valgrind in Jenkins get this bug type, my sugestion is running this tests on all sources.
12:35:05 <lalatenduM> ndevos, then I kind of sure you know the root cause too, but the bug does have that part
12:35:34 <ndevos> lalatenduM: I do now know, but I have a suggestion, I'll add that as a comment
12:35:48 <lalatenduM> ndevos, awesome thanks
12:36:51 <lalatenduM> firemanxbr, agree, we dont have Vagrant running for master branch or so
12:38:22 * lalatenduM locks 1196019
12:39:23 <ndevos> lalatenduM: vagrant != valgrind ?
12:39:45 <lalatenduM> ndevos, ahh yes, I mean valgrind
12:39:51 * firemanxbr http://valgrind.org/
12:40:00 <firemanxbr> :]
12:40:10 <ndevos> lalatenduM: but, I guess we would be able to run valgrind on nightly tests?
12:40:26 <firemanxbr> In my work we development firmware for switches: www.datacom.ind.br
12:40:26 <ndevos> lalatenduM: like, one nightly jenkins job with valgrind, one without?
12:40:37 <lalatenduM> ndevos, not with the tests I am planning , it will be difficult
12:40:44 <firemanxbr> we use much job's running valgrind :D
12:40:53 <lalatenduM> ndevos, may be regression tests with Valgrind
12:41:00 <ndevos> lalatenduM: where can I submit feature requests?
12:41:51 <lalatenduM> ndevos, for the tests?
12:41:56 <ndevos> firemanxbr: you get commission when you mention the website often enough?
12:42:25 <ndevos> lalatenduM: yes, like requesting regression tests running with valgrind
12:43:00 <lalatenduM> ndevos, I am not sure where put this request :(
12:43:09 <lalatenduM> may be a mail in gluster-devel
12:43:26 <ndevos> lalatenduM: actually, I was thinking of inspecting the logs after a regression test - like files get bigger, certain entries that are added much more, ...
12:43:57 <lalatenduM> ndevos, right, I think it is good idea
12:44:24 <ndevos> lalatenduM: thanks, but where to note it so that it does not get lost?
12:44:50 <ndevos> hchiramm: as bugzilla component wizzard, do you have a suggestion?
12:44:52 <lalatenduM> ndevos, may be wiki page as todo list
12:45:29 <firemanxbr> ndevos, ehhehehe no :)
12:45:36 <hchiramm> ndevos, yes
12:45:42 <ndevos> lalatenduM: did you read "so that it does not get lost"?
12:45:53 <ndevos> firemanxbr: ;)
12:46:02 * lalatenduM locks 1196161
12:46:09 <hchiramm> ndevos, lets have a component called 'gluster-infra' ?
12:46:16 <hchiramm> ah.. wait
12:46:33 <hchiramm> there is already a component called 'project-infrastructure'
12:46:35 <firemanxbr> ndevos, I wish say a day: I works with open source project :)
12:46:35 <lalatenduM> hchiramm,  do you think https://bugzilla.redhat.com/show_bug.cgi?id=1196161 is a easyfix bug?
12:46:37 * firemanxbr Lol
12:46:38 <lalatenduM> ndevos, ^^
12:46:58 <hchiramm> lalatenduM, checking
12:47:08 <hchiramm> lalatenduM, very tough
12:47:10 <hchiramm> :)
12:47:18 <lalatenduM> hchiramm, :) ok
12:47:21 <ndevos> firemanxbr: you can already! add a job description to your linkedin profile for the "gluster community" company :)
12:47:32 <hchiramm> looks like the propagation of that error is not happening properly
12:47:46 <hchiramm> somewhere its masked
12:47:49 <firemanxbr> ndevos, good idea :D
12:47:51 <hchiramm> mostly in ctypes
12:48:04 <hchiramm> lalatenduM, ^^
12:48:29 <lalatenduM> hchiramm, no idea  abt the issue
12:49:11 <ndevos> firemanxbr: job title can be something like "Infrastructure Contributor/Sysadmin"
12:49:44 <ndevos> lalatenduM: no idea how easy it is... maybe easy for someone that knows the internals of the python bits?
12:49:55 <lalatenduM> ndevos, last bug https://bugzilla.redhat.com/show_bug.cgi?id=1198119 , looks like you are right guy for this
12:50:04 <lalatenduM> ndevos, ack
12:51:05 <firemanxbr> ndevos, :)
12:51:30 <ndevos> lalatenduM: just mark it ASSIGNED, jiffin put his name as assignee ;)
12:52:10 <lalatenduM> ndevos, done
12:52:21 <ndevos> thanks
12:52:39 <ndevos> nice, all bugs have been triaged - THANKS ALL!
12:52:47 <ndevos> #topic Open Floor
12:53:04 <hchiramm> nothing from me
12:53:06 <ndevos> hchiramm, rafi, atinmu, lalatenduM, firemanxbr: anything you'd like to discuss more?
12:53:26 <atinmu> ndevos, nopes, thank u :)
12:53:47 <firemanxbr> for me nothing, only very happy in contribute with great project
12:53:50 <rafi> ndevos: nothing :) thank u
12:53:56 <hchiramm> ndevos++ thanks ..
12:54:02 <firemanxbr> ndevos++
12:54:09 <hchiramm> firemanxbr++ , nice to have u here
12:54:09 <lalatenduM> ndevos++ :)
12:54:27 <ndevos> okay, many thanks for joining and your help today
12:55:01 <ndevos> #info remember that the weekly community meeting is happening tomorrow, same time, same place as this meeting
12:55:17 <ndevos> #endmeeting