Perl 6 - the future is here, just unevenly distributed

IRC log for #gluster-dev, 2014-06-26

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

All times shown according to UTC.

Time Nick Message
00:03 bala joined #gluster-dev
00:10 vpshastry joined #gluster-dev
00:20 lpabon joined #gluster-dev
00:42 bala joined #gluster-dev
00:42 awheeler joined #gluster-dev
00:53 baojg joined #gluster-dev
01:01 baojg_ joined #gluster-dev
01:40 vpshastry joined #gluster-dev
01:59 kdhananjay joined #gluster-dev
02:45 baojg joined #gluster-dev
02:58 bharata-rao joined #gluster-dev
03:19 vpshastry joined #gluster-dev
03:37 atinmu joined #gluster-dev
03:50 baojg joined #gluster-dev
04:03 shubhendu__ joined #gluster-dev
04:08 baojg joined #gluster-dev
04:08 baojg joined #gluster-dev
04:10 itisravi joined #gluster-dev
04:19 ndarshan joined #gluster-dev
04:20 lalatenduM joined #gluster-dev
04:32 * JustinClift hopes this rackspace-regression-2GB-triggeredv3 job gets the right CR's to communicate results back for
04:33 JustinClift If so, I think we'll be able to get auto-triggered regression tests running
04:42 vpshastry joined #gluster-dev
04:58 vimal joined #gluster-dev
04:58 skoduri joined #gluster-dev
05:04 kdhananjay joined #gluster-dev
05:06 awheeler joined #gluster-dev
05:10 ppai joined #gluster-dev
05:25 aravindavk joined #gluster-dev
05:28 kanagaraj joined #gluster-dev
05:28 ppai joined #gluster-dev
05:40 hagarth joined #gluster-dev
05:48 bala1 joined #gluster-dev
05:48 kshlm joined #gluster-dev
05:48 nishanth joined #gluster-dev
05:53 aravindavk joined #gluster-dev
06:33 JustinClift k, now it's time to get some sleep :)
06:36 baojg joined #gluster-dev
06:45 aravindavk joined #gluster-dev
06:55 hchiramm_ joined #gluster-dev
07:05 ndarshan joined #gluster-dev
07:06 awheeler joined #gluster-dev
07:08 kdhananjay joined #gluster-dev
07:17 hchiramm_ joined #gluster-dev
08:42 ppai hi all, what do you guys think about moving from rfc.sh to git-review (based on rfc.sh) : https://pypi.python.org/pypi/git-review
08:42 glusterbot Title: git-review 1.23 : Python Package Index (at pypi.python.org)
08:55 ndevos ppai: does it automatically pick a topic for the change when posting?
08:56 ndevos ppai: I've used git-review for wireshark patches, and I think I have to pick a topic myself - it does not follow the current bug-# topic convention we use now
08:57 ppai http://www.mediawiki.org/wiki/Gerrit/git-review tells me that it does figure out topic
08:57 glusterbot Title: Gerrit/git-review - MediaWiki (at www.mediawiki.org)
08:57 ppai "What happens when you submit a change" section in that wiki
08:58 ndevos ppai: hmm, okay
08:59 ndevos ppai: can we include a check like http://review.gluster.org/8181 before submitting the change?
08:59 glusterbot Title: Gerrit Code Review (at review.gluster.org)
08:59 ppai ndevos, not sure about that though
09:00 ndevos well, maybe that should be a local git-hook, but I've never looked at how that works
09:00 ppai "git-review has a custom hook mechanism to run a script before certain actions. This is done in the same spirit as the classic hooks in git."
09:00 ppai from the wiki
09:00 ppai it's here: https://pypi.python.org/pypi/git-review
09:00 ndevos ppai: if such a check can get included, either by git-review or a git-hook, I dont have any objections against moving to git-review
09:00 glusterbot Title: git-review 1.23 : Python Package Index (at pypi.python.org)
09:01 ndevos ppai: standardizing on tools that are used in other projects is a good thing, imho
09:01 ndevos oh, and there is a fedora/epel package for it too already :)
09:02 ppai ndevos, it's used in swift, and earlier in gluster-swift
09:02 ppai pip install git-review :)
09:02 ndevos ppai: I think oVirt and OpenStack use it too
09:02 ppai Openstack does :)
09:02 hchiramm_ ndevos, yep ..
09:03 ndevos I don't like pip too much, it does not provide updates through the normal yum repositories
09:03 hchiramm_ ndevos, ppai rfc does rebase automatically right which git review dont ?
09:03 ppai true, pip packages are usually updated often
09:03 * hchiramm_ have an illusion there..
09:04 ppai I think it does a rebase
09:04 ndevos hchiramm_: if it does, one more +1 for git-review, I dont like unneeded rebases when reviewing newer versions of patches
09:04 hchiramm_ ppai, I doubt :)
09:05 hchiramm_ if my ovirt patch memories are not bad :)
09:05 ppai It has a -R option (as stated in man page) - "Do not automatically perform a rebase before submitting the change to Gerrit."
09:06 hchiramm_ may be by default its on
09:06 ppai yes it is!
09:06 ppai It's configurable in .gitreview file
09:06 ppai by setting "defaultrebase=0"
09:06 hchiramm_ oh..ok..
09:07 hchiramm_ I was doing manually with vdsm patches
09:07 hchiramm_ :)
09:27 itisravi_ joined #gluster-dev
09:29 krishnan_p joined #gluster-dev
09:37 kshlm ppai, avati has just one concern with git review.
09:37 kshlm I doesn't have a way to ask the users to enter a bug id for the topic, like rfc.sh does.
09:37 kshlm That is needed for our bugzilla integration.
09:50 shubhendu__ joined #gluster-dev
09:59 itisravi joined #gluster-dev
10:02 kdhananjay joined #gluster-dev
10:04 kaushal_ joined #gluster-dev
10:06 baojg joined #gluster-dev
10:15 atinmu joined #gluster-dev
10:30 deepakcs joined #gluster-dev
10:32 kkeithley1 joined #gluster-dev
10:32 ppai kshlm,
10:32 ppai if your commit summary contains a bug number like bug 12345, the topic will be bug/12345
10:32 glusterbot Bug https://bugzilla.redhat.com:443/show_bug.cgi?id=12345 medium, medium, ---, bero, CLOSED RAWHIDE, ps-to-printer.fpi
10:32 ppai otherwise, the tag will be the name of your local branch
10:33 ppai you can set the topic manually with -t
10:33 shubhendu joined #gluster-dev
10:39 hagarth joined #gluster-dev
10:52 lalatenduM joined #gluster-dev
10:56 kaushal_ joined #gluster-dev
11:07 atinmu joined #gluster-dev
11:09 hchiramm_ lalatenduM, went through the meeting chat log.. started the build process .. and one scratch build is ready..
11:09 hchiramm_ :)
11:10 lalatenduM hchiramm_, awesome :)
11:10 hchiramm_ :)
11:10 lalatenduM @hchiramm_++
11:10 glusterbot lalatenduM: hchiramm_'s karma is now 1
11:10 hchiramm_ now have to trigger it against rest 5 targets..
11:10 hchiramm_ then the process follows..
11:11 lalatenduM cool
11:13 lalatenduM hchiramm_, let me know how can I help
11:14 hchiramm_ sure..
11:15 hchiramm_ first I will complete the scratch build
11:15 spandit joined #gluster-dev
11:27 hchiramm__ joined #gluster-dev
11:37 kdhananjay joined #gluster-dev
11:41 edward1 joined #gluster-dev
12:03 baojg joined #gluster-dev
12:05 baojg_ joined #gluster-dev
12:05 baojg_ joined #gluster-dev
12:18 ppai joined #gluster-dev
12:34 tdasilva joined #gluster-dev
12:47 dlambrig_ joined #gluster-dev
12:56 baojg joined #gluster-dev
12:59 shyam joined #gluster-dev
13:05 awheeler joined #gluster-dev
13:46 vpshastry joined #gluster-dev
13:48 hagarth joined #gluster-dev
13:53 dlambrig_ left #gluster-dev
14:02 ws2k3 joined #gluster-dev
14:03 ws2k3 does gluster already support multi master replication? i see that in 3.4 and 3.5 there where plans to add it but i'm unable to find any info regarding this
14:06 kkeithley_ it does not
14:06 ws2k3 ah okay is this feature still in development/are there plans to add it in the future
14:17 kkeithley_ The plans are still there. It's a matter of priorities and resources
14:18 ndevos kkeithley_: not sure if you have seen bug 1113543 , I've put it on needinfo? from anyone, but you'd be one of the preferred responders :)
14:18 glusterbot Bug https://bugzilla.redhat.com:443/show_bug.cgi?id=1113543 high, unspecified, ---, rwheeler, NEW , Spec %post server does not wait for the old glusterd to exit
14:19 kkeithley_ ndevos: I'll take a look
14:19 ndevos thanks!
14:23 skoduri joined #gluster-dev
14:23 jobewan joined #gluster-dev
14:28 lalatenduM ws2k3, check https://github.com/gluster/glusterfs/tree/release-3.5/doc/features/geo-replication
14:28 glusterbot Title: glusterfs/doc/features/geo-replication at release-3.5 · gluster/glusterfs · GitHub (at github.com)
14:29 wushudoin joined #gluster-dev
14:34 kkeithley_ but he wants multi-master...
14:36 shubhendu joined #gluster-dev
14:38 ws2k3 with multi-master i mean i have locations in 2 different datacenters if i would glusterfs replication that i can write files on cluster a and that files will be sycned to cluster b en files written in cluster b will be synced back to cluster a
14:45 lalatenduM ws2k3, I dont have much knowledge on geo-rep, so will defer it to msvbhat
14:58 deepakcs joined #gluster-dev
15:05 ndevos ws2k3: multi-master is not available yet, but you could setup two volumes, one with the master in site-a, and one with the master in site-b
15:05 ndevos depending on use-case, some people have been able to use that solution
15:07 hchiramm_ kkeithley++ lalatenduM++
15:08 lalatenduM hchiramm_, you did everything :)
15:09 hchiramm_ how-ever :) .. I am happy that, u people are always there :)
15:11 lalatenduM hchiramm_, :)
15:11 hchiramm_ :)
15:11 hchiramm_ @ teamwork++
15:11 glusterbot hchiramm_: teamwork's karma is now 2
15:14 bala1 joined #gluster-dev
15:29 lpabon joined #gluster-dev
15:30 kshlm joined #gluster-dev
15:32 kkeithley_ ndevos: wrt 1113543, which is the primary concern, that the new glusterd was started too soon? That we need a cleaner solution for starting glusterd with the *.upgrade=on option? Or both?
15:33 ndevos kkeithley_: that glusterd was started too soon was the main issue, the options should have been already set when 3.5 (or earlier) was installed
15:34 ndevos kkeithley_: the options are important for *some* upgrades, I'm not sure if we should carry them in all future .spec files
15:34 ndevos kkeithley_: so, a cleaner way would be nice, but that is secondary
15:37 kkeithley_ so, is something like a sleep between the killall glusterd and starting the new one too much of a hack? Or get the pid out of /run/glusterd.pid and wait for it to disappear from pgrep? Or wait for /run/glusterd.pid to disappear?
15:41 ndevos kkeithley_: what about 'killall --wait ...'?
15:41 kkeithley_ probably nothing ;-)
15:44 MacWinner joined #gluster-dev
15:45 kkeithley_ seems like a no-brainer actually.
15:48 lpabon joined #gluster-dev
15:48 ndevos kkeithley_: I'll be back tomorrow and can send a patch then, if you have not done so yet :)
15:48 * ndevos leaves the office
15:53 lpabon joined #gluster-dev
16:01 kdhananjay joined #gluster-dev
16:03 wushudoin left #gluster-dev
16:06 kanagaraj joined #gluster-dev
16:23 lpabon_test joined #gluster-dev
16:50 skoduri joined #gluster-dev
16:54 shyam joined #gluster-dev
17:05 JoeJulian kkeithley: get the pid out of /run/glusterd.pid and wait, but have a timeout.
17:06 JoeJulian ndevos:
17:06 lpabon joined #gluster-dev
17:46 pranithk joined #gluster-dev
17:46 pranithk JustinClift: ping
17:50 pranithk left #gluster-dev
18:00 vpshastry joined #gluster-dev
18:15 MacWinner joined #gluster-dev
18:47 MacWinner joined #gluster-dev
18:47 shyam joined #gluster-dev
18:47 kanagaraj joined #gluster-dev
18:47 ws2k3 joined #gluster-dev
18:47 hagarth joined #gluster-dev
18:47 edward1 joined #gluster-dev
18:47 hchiramm__ joined #gluster-dev
18:47 kkeithley_ joined #gluster-dev
18:47 swebb joined #gluster-dev
18:47 systemonkey joined #gluster-dev
18:47 rturk|afk joined #gluster-dev
18:47 foster joined #gluster-dev
18:47 dachary joined #gluster-dev
18:47 bfoster joined #gluster-dev
18:47 rturk-away joined #gluster-dev
18:47 xavih joined #gluster-dev
18:47 JustinClift joined #gluster-dev
18:47 msvbhat joined #gluster-dev
18:47 lkoranda joined #gluster-dev
18:48 JustinClift joined #gluster-dev
18:48 msvbhat joined #gluster-dev
18:49 msvbhat joined #gluster-dev
18:49 JustinClift joined #gluster-dev
18:51 suliba_ joined #gluster-dev
18:57 purpleidea joined #gluster-dev
18:57 purpleidea joined #gluster-dev
19:00 tdasilva joined #gluster-dev
19:02 JoeJulian Damn... missed pranithk... I've been meaning to pick his brain...
19:15 jobewan joined #gluster-dev
19:19 lpabon joined #gluster-dev
19:19 awheeler joined #gluster-dev
19:19 [o__o] joined #gluster-dev
19:19 tg2 joined #gluster-dev
19:19 kkeithley joined #gluster-dev
19:45 MacWinner joined #gluster-dev
20:24 shyam left #gluster-dev
20:32 ndevos joined #gluster-dev
20:32 ndevos joined #gluster-dev
20:56 primechuck joined #gluster-dev
20:56 hagarth joined #gluster-dev
20:56 primechuck left #gluster-dev
21:40 primechuck joined #gluster-dev
21:40 primechuck left #gluster-dev
21:44 awheeler joined #gluster-dev
21:49 kshlm joined #gluster-dev

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