Camelia, the Perl 6 bug

IRC log for #gluster-dev, 2013-01-15

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

All times shown according to UTC.

Time Nick Message
01:04 JoeJulian joined #gluster-dev
01:07 JoeJulian joined #gluster-dev
02:27 hagarth joined #gluster-dev
04:07 overclk joined #gluster-dev
04:22 bala1 joined #gluster-dev
04:38 sripathi joined #gluster-dev
04:55 deepakcs joined #gluster-dev
05:06 hagarth joined #gluster-dev
05:09 vpshastry joined #gluster-dev
05:12 bulde joined #gluster-dev
05:31 raghu joined #gluster-dev
05:44 sripathi joined #gluster-dev
05:48 sripathi joined #gluster-dev
05:53 hagarth joined #gluster-dev
06:30 sripathi joined #gluster-dev
08:18 puebele joined #gluster-dev
08:30 sripathi joined #gluster-dev
08:33 sripathi joined #gluster-dev
08:34 deepakcs joined #gluster-dev
08:35 sripathi1 joined #gluster-dev
08:47 hagarth joined #gluster-dev
09:00 bulde1 joined #gluster-dev
09:35 gbrand_ joined #gluster-dev
09:38 gbrand_ joined #gluster-dev
10:02 sripathi joined #gluster-dev
10:03 sripathi1 joined #gluster-dev
10:09 hagarth joined #gluster-dev
10:43 shireesh joined #gluster-dev
10:50 bulde joined #gluster-dev
11:02 sripathi joined #gluster-dev
11:04 shireesh joined #gluster-dev
11:24 sripathi joined #gluster-dev
11:27 bala joined #gluster-dev
11:50 shireesh joined #gluster-dev
11:57 raghu joined #gluster-dev
12:00 jdarcy Yo.  Anybody else awake here?
12:01 * hagarth is
12:01 jdarcy Good morning, Vijay.
12:02 hagarth Good morning, Jeff.
12:03 jdarcy I didn't see a conference number in the 3.4 email, so I guess we're doing it here.
12:03 * bulde too
12:03 * hagarth pokes johnmark
12:03 jdarcy Hi, Amar.  LTNS.
12:03 hagarth yeah, seems like that.
12:04 jdarcy He's probably still asleep.  ;)
12:04 johnmark greetings
12:04 johnmark hagarth: poke
12:04 * jdarcy <- wrong again
12:04 johnmark jdarcy: boo
12:05 johnmark heh
12:05 jdarcy Hi, johnmark.  Mailing list seems quiet.  Did it get switched to moderation mode?
12:05 bulde jdarcy: yep, long time
12:05 johnmark jdarcy: ha! no :)
12:05 johnmark we can do a call if you want.
12:05 johnmark which do you prefer? this or telephone?
12:06 jdarcy This is fine with me.
12:06 johnmark jdarcy: aight
12:06 johnmark bulde: howdy
12:06 johnmark I have a half-written blog post describing 3.4
12:07 johnmark let's keep this short and get a status on where we are
12:07 johnmark hagarth: what are the remaining items to clear for a beta?
12:08 bulde johnmark: me doing good :-) how about you?
12:08 hagarth johnmark: primarily more testing coverage, a couple more enhancements to be accepted - rdma and client op-version being the other
12:08 * bulde would like to see RDMA pushed
12:08 bulde with few more enhancements to glusterd going in
12:09 johnmark bulde: +1. because we get asked about it All. The Time.
12:09 johnmark hagarth: ok
12:09 johnmark hagarth: what, specifically, would you like to see tested?
12:09 jdarcy So we need to get on top of the reviews for those.  Also, we might have another regression problem that will need to be cleared.
12:09 johnmark jvyas: oh right
12:10 johnmark bulde: what kind of glusterd enhancements?
12:10 hagarth johnmark: acl support in nfs, glusterd regressions, eager locking & delayed changelog enhancements in afr
12:10 bulde gluster volume status fixes (posted for review already), and few more log enhancements (posted today)
12:10 hagarth johnmark: other regression tests would be needed too
12:10 johnmark bulde: ok, cool
12:10 johnmark hagarth: ok
12:11 hagarth bulde: volume status just failed a regression run. Do we need it badly or can we delay it for after 3.4?
12:11 jdarcy Bugs targeted for 3.4: https://bugzilla.redhat.com/buglist.cgi?o​rder=Importance&amp;classification=Commun​ity&amp;query_format=advanced&amp;bug_sta​tus=NEW&amp;bug_status=ASSIGNED&amp;targe​t_milestone=3.4.0&amp;product=GlusterFS
12:11 johnmark jdarcy: thanks
12:12 bulde hagarth: would be good to get it tested well, so if it makes to 3.4.0, its better for us
12:12 bulde jdarcy: thats a better tracking option :-) thanks
12:12 hagarth jdarcy: some of these are from pre-3.3 days when we used to have a single bugzilla .. might not be very relevant now
12:12 jdarcy I see mostly HDFS and UFO stuff so far, probably need a sweep to update that list.
12:12 johnmark jdarcy: yeah, most of those are quite old
12:13 * bulde sees that the list has no bugs depending on him or his team
12:13 johnmark bulde: congratulations :)
12:13 hagarth johnmark: it might be interesting to let community nominate blockers
12:13 johnmark hagarth: ok. let's put out our list of testing requests
12:13 johnmark and see what comes back
12:13 johnmark hagarth: is there a description anywhere of what eager locking is?
12:15 hagarth johnmark: nothing much right now, we need to evolve that
12:15 johnmark hagarth: ok
12:15 johnmark hagarth: we had discussed previously possibly doing an 'alpha' release just toget more testing
12:15 jdarcy Should replica 3 be on the 3.4 list?
12:15 raghu joined #gluster-dev
12:16 johnmark after this next round of patches get reviewed and applied, would that be a possibility?
12:16 hagarth jdarcy: yes, it would be good to have that
12:16 johnmark hagarth: ok
12:16 hagarth johnmark: will do
12:16 johnmark hagarth: who can tag the 3.4 branch for release?
12:16 hagarth jdarcy: replica 3 looks ok to me, awaiting Avati's review comments on that as well
12:16 johnmark hagarth: excellent news.
12:16 johnmark we'll have to remember to poke Avati
12:17 hagarth johnmark: I normally do the tagging
12:17 johnmark hagarth: ok
12:17 johnmark hagarth: how long do you think we'll need to apply patches, branch and put out the alpha?
12:18 hagarth johnmark: at least a couple more days.
12:18 johnmark hagarth: ok. just let me know. I'll have the blog post ready to go
12:18 johnmark so it *sounds* like we're en route to having a February release
12:18 * bulde feels 'alpha0' should happen this week, regardless of all the features
12:19 johnmark bulde: ok
12:19 johnmark so if I can help drive testing and writing up descriptions of new features, what else can I do to help?
12:20 hagarth johnmark: testing + documentation + identifying blockers for the release would be great
12:20 johnmark hagarth: excellent
12:20 johnmark aye aye, cap'n
12:20 bulde (and setting right target milestone for the tracking bugs?)
12:21 hagarth bulde: yeah, we need to define the process
12:21 johnmark bulde: ok
12:21 hagarth may be we should wipe target milestone of all bugs that have it as 3.4.0
12:21 johnmark bulde: I can help round those up
12:21 hagarth and start afresh
12:21 jdarcy hagarth: Sounds reasonable to me.  Those look pretty stale.
12:21 johnmark hagarth: it would appear that way
12:21 johnmark hagarth: where's a good place to start?
12:21 bulde and 3.3.0?
12:22 hagarth johnmark: the list that Jeff provided
12:22 johnmark hagarth: ok
12:22 hagarth johnmark: you can also query for all bugs in GlusterFS that have target milestone set and wipe them off
12:22 bulde good we don't have bugs targetted to 3.3.0 in ASSIGNED or NEW state :-)
12:22 jdarcy So we clear what's there, and add the other things we've talked about?
12:22 johnmark hagarth: ah, ok
12:23 johnmark bulde: ha!
12:23 hagarth jdarcy: yes, that seems like a good path to tread
12:23 jdarcy Alternatively, we could create a 3.4 tracker bug and add the stuff we've talked about as dependencies.  I've seen both approaches used on other RH projects.
12:23 johnmark jdarcy: ok
12:24 hagarth jdarcy: yeah, we could do that too
12:24 johnmark jdarcy: yeah, because I konw there's a lot of stuff on bugzilla that needs to be pruned
12:24 hagarth once we converge on the process, we can probably send out a mail on our decision
12:24 johnmark hagarth: ok
12:24 jdarcy I kind of like setting the target milestone a little better because it gives people an actual table with descriptions and assignees etc. instead of just numbers, but I figured I'd put the alternative out there.
12:24 bulde tracker bug looks better for 3.4.0 to start with
12:25 johnmark jdarcy: ok
12:25 johnmark bulde: it sounds easier :)
12:25 jdarcy If somebody else wants to update a tracker bug, I'll propagate that info into milestone assignments.
12:25 bulde yes, after i become supervisor, i look 'easier' == 'better' :-)
12:26 hagarth so what do we converge on - tracker bug or milestones or both?
12:27 johnmark bulde: heh :)
12:27 jdarcy hagarth: Whatever's easiest for you and Amar, I'd say.  Sounds like tracker.
12:27 johnmark jdarcy: ok
12:27 hagarth ok let tracker be it for 3.4
12:27 johnmark so it sounds like when we create the tracker bug, we can add bug IDs to the description
12:27 johnmark to track the other things
12:27 bulde 'depends on'  field in bugzilla
12:28 * jdarcy nods to bulde.
12:28 johnmark bulde: ok
12:28 hagarth ok, who'll log the bug and hit the mailing lists with the tracker?
12:28 jdarcy johnmark: Then you can put the URL in your blog post.
12:28 johnmark jdarcy: excellent
12:28 hagarth ok, i retract my  question :)
12:28 bulde any guesses on which all bugs we are tracking for 3.4.0? should we include already fixed/modified/verified bugs ? or only the open bugs?
12:29 hagarth bulde: only the open bugs
12:29 johnmark hagarth: +1
12:29 sripathi joined #gluster-dev
12:29 johnmark hagarth: including the ones with fixes in review
12:29 bulde any idea on numbers? 5 bugs? 10bugs? 50bugs? (just asking)
12:29 jdarcy "acl support in nfs, glusterd regressions, eager locking & delayed changelog enhancements in afr" + RDMA + replica3
12:29 johnmark bulde: I was wondering same
12:30 jdarcy I can pull together a candidate list and send it to you guys for additions.
12:30 hagarth jdarcy: that sounds good
12:30 johnmark jdarcy: + client-op version + glusterd enhancements
12:31 johnmark er op-client
12:31 bulde jdarcy++
12:32 jdarcy OK, I'll do that after I take out the trash and before my dentist appointment.  Fun day.  ;)
12:32 johnmark jdarcy: woohoo
12:32 hagarth jdarcy: all the best ;)
12:32 johnmark excellent.
12:32 * bulde heads to prepare for the next meeting :-o
12:33 jdarcy Once I have the list I'll create the tracker.
12:33 johnmark anything else? do y'all want to get together again next week?
12:33 johnmark jdarcy: thanks
12:33 jdarcy Next week sounds good.
12:33 raghu joined #gluster-dev
12:33 johnmark excellent
12:33 johnmark thanks guys!
12:34 hagarth thanks johnmark, hopefully we'll have the alpha by our meeting next week
12:34 johnmark I know you're busy, so I'll leave you to your work
12:34 jdarcy :)
12:34 johnmark hagarth: thank you! when it's ready :)
12:34 jdarcy Trash time.  Later, all.
12:34 hagarth later, everyone
12:39 kkeithley1 joined #gluster-dev
12:40 johnmark kkeithley1: hey
12:40 johnmark feb 26 is confirmed and ready to go
12:44 johnmark jdarcy: we should add target release info so that we can get a real graphic here: https://bugzilla.redhat.com/page.cgi?id=brow​se.html&amp;product=GlusterFS&amp;product_ve​rsion=&amp;bug_status=open&amp;tab=roadmap
12:45 kkeithley1 left #gluster-dev
12:46 kkeithley1 joined #gluster-dev
13:06 shireesh joined #gluster-dev
13:29 spn joined #gluster-dev
13:30 bulde joined #gluster-dev
13:56 bulde1 joined #gluster-dev
14:17 hagarth joined #gluster-dev
14:44 sripathi joined #gluster-dev
15:22 hagarth joined #gluster-dev
15:24 shireesh joined #gluster-dev
15:26 jbrooks joined #gluster-dev
15:30 wushudoin joined #gluster-dev
15:38 bala joined #gluster-dev
16:01 spn joined #gluster-dev
16:07 spn joined #gluster-dev
16:33 shireesh joined #gluster-dev
16:39 gbrand_ hello. I'm trying some volume configurations with 2 nodes, each one having a gluster client and server running. Both clients have each one a volume related to my translator, which has as sub volumes two "protocol/client" subvolumes (one subvol pointing to the local node's IP/vol and another pointing to the remote node IP/vol). This works OK, and here comes the problem: when I try to change the local vol at the client side from a "protocol/client" type
16:39 gbrand_ "posix" type the read breaks with -1 (operation not permitted). Since the access is local this would make sense to don't go through the client/server protocol stack, but access directly through posix translator. I don't see why it shouldn't work.
17:22 hagarth joined #gluster-dev
18:35 portante joined #gluster-dev
19:01 kkeithley1 joined #gluster-dev
19:14 kkeithley1 joined #gluster-dev
19:28 gbrand__ joined #gluster-dev
20:15 gbrand_ joined #gluster-dev
21:30 kkeithley2 joined #gluster-dev
21:51 kkeithley2 left #gluster-dev
21:57 copec Does anyone know what I need to get fusermount to ./configure on Ubuntu?
22:03 copec ah
22:03 copec it works with --enable-fusermount
22:55 badone joined #gluster-dev

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