Perl 6 - the future is here, just unevenly distributed

IRC log for #gluster-dev, 2014-04-10

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

All times shown according to UTC.

Time Nick Message
00:37 hchiramm__ joined #gluster-dev
00:42 awheeler joined #gluster-dev
00:43 awheeler joined #gluster-dev
00:52 yinyin_ joined #gluster-dev
00:54 hchiramm__ joined #gluster-dev
01:00 awheeler_ joined #gluster-dev
01:01 awheeler joined #gluster-dev
01:05 awheeler joined #gluster-dev
01:14 bala joined #gluster-dev
01:47 awheeler joined #gluster-dev
01:49 ilbot3 joined #gluster-dev
01:49 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/
01:52 yinyin_ joined #gluster-dev
02:02 Yuan_ joined #gluster-dev
02:33 hagarth joined #gluster-dev
02:56 bharata-rao joined #gluster-dev
03:20 kshlm joined #gluster-dev
03:35 kanagaraj joined #gluster-dev
03:46 itisravi joined #gluster-dev
04:02 ndarshan joined #gluster-dev
04:11 ppai joined #gluster-dev
04:16 yinyin_ joined #gluster-dev
04:18 deepakcs joined #gluster-dev
04:22 atinm joined #gluster-dev
04:25 an joined #gluster-dev
04:32 hagarth joined #gluster-dev
04:34 shubhendu joined #gluster-dev
04:43 spandit joined #gluster-dev
04:51 ppai joined #gluster-dev
04:54 sahina joined #gluster-dev
04:55 kdhananjay joined #gluster-dev
05:10 bharata-rao joined #gluster-dev
05:27 bala1 joined #gluster-dev
05:27 raghu joined #gluster-dev
05:41 bala1 joined #gluster-dev
05:51 lalatenduM joined #gluster-dev
05:54 ppai joined #gluster-dev
06:01 deepakcs joined #gluster-dev
06:02 hchiramm__ joined #gluster-dev
06:27 an joined #gluster-dev
06:31 bharata-rao joined #gluster-dev
07:32 itisravi joined #gluster-dev
07:33 hagarth joined #gluster-dev
07:34 shubhendu joined #gluster-dev
07:45 sac`away joined #gluster-dev
08:16 hagarth joined #gluster-dev
09:32 kdhananjay joined #gluster-dev
09:42 hchiramm__ joined #gluster-dev
10:19 xavih ndevos: ping
10:19 ndevos hi xavih
10:20 xavih ndevos: I'm analyzing some network traffic and I've seen what seems a bug with GlusterFS module
10:20 xavih ndevos: I'm using wireshark from Fedora 20. Not sure if it has the latest version
10:21 xavih ndevos: on OPEN calls, the flags arguments seems to not be converted from network to hardware format
10:21 ndevos xavih: oh, really?
10:21 pk joined #gluster-dev
10:22 xavih ndevos: when I open a file with O_RDWR, wireshark shows "Flags: 0200000000, Unused"
10:22 ndevos xavih: there probably is a newer version of wireshark, but OPEN or decoding of flags has not been changes
10:22 ndevos *changed
10:22 xavih ndevos: while it should be 0000000002, which is O_RDWR
10:22 ndevos xavih: okay, thanks, that should be an easy fix :)
10:23 hagarth joined #gluster-dev
10:23 xavih ndevos: yw :)
10:23 ndevos xavih: when I post a patch for that, I'll mention you in a Reported-by tag :D
10:24 xavih ndevos: where are wireshark bugs tracked ?
10:24 xavih ndevos: if you want I can file the bug
10:25 ndevos xavih: you could file a bug in bugs.wireshark.org, but that is not required for sending patches
10:25 xavih ndevos: ok, no problem then :)
10:25 ndevos xavih: many patches to wireshark just dont have a bug attached :)
10:28 hagarth hello, world!
10:30 ndevos hello hagarth!
10:30 lalatenduM joined #gluster-dev
10:40 kdhananjay joined #gluster-dev
10:43 hagarth ndevos: how's it going?
10:44 ndevos hagarth: I'm good, thanks, how are you?
10:44 kanagaraj joined #gluster-dev
10:45 hagarth ndevos: thanks, been good and busy :)
10:46 ndevos hagarth: it's good that you're kept busy ;)
10:46 hagarth ndevos: lol
10:48 ndevos hagarth: you missed the meeting yesterday, if you have some status update, you may want to send a reply to the minutes
10:50 hagarth ndevos: will do, 3.5.0 is almost there and that needs to be notified.
10:50 ndevos hagarth: okay, that was one of the topics we didnt know the status of :)
10:51 hagarth ndevos: yeah, thought as much :)
10:55 xavih ndevos: it seems that the net to hard order conversion is not applied on other places, like 'mode' argument on CREATE calls
10:56 xavih ndevos: not sure if there are more places
10:56 ndevos xavih: yes, I think mode/flags is done in the same function
10:56 ndevos jclift: AI done: http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/6050
10:56 glusterbot Title: Gmane Loom (at thread.gmane.org)
10:59 lpabon joined #gluster-dev
11:00 kkeithley1 joined #gluster-dev
11:17 kanagaraj joined #gluster-dev
11:21 ppai joined #gluster-dev
11:21 ndarshan joined #gluster-dev
11:22 sahina joined #gluster-dev
11:23 shubhendu joined #gluster-dev
11:38 ira_ joined #gluster-dev
12:12 pk left #gluster-dev
12:12 itisravi joined #gluster-dev
12:21 deepakcs joined #gluster-dev
13:05 tdasilva joined #gluster-dev
13:14 jclift hagarth: I'm a bit confused about Gluster 3.5 release, and the state of 3.5 docs
13:15 jclift hagarth: Just looked on the wiki, can't see feature docs there.  Not in the docs/ dir of source repo.
13:16 awheeler joined #gluster-dev
13:16 jclift hagarth: Are we still intending on having docs for all 3.4/3.5 features ready at release?
13:30 johnmark jclift: looks like we'll have to take what's on the features pages and apply to /docs in the repo
13:34 jclift johnmark: There's almost nothing in the features pages
13:34 lalatenduM_ joined #gluster-dev
13:34 jclift Certainly no docs
13:34 * jclift just went through and looked to be sure before asking
13:34 johnmark grrr
13:34 johnmark ok, I'm sending a PSA to the lists
13:35 johnmark we can't continue to do this
13:35 jclift Bingo
13:35 jclift Thanks
13:40 johnmark sending a note to the list - saying that we're not releasing until docs are done
13:42 jclift johnmark: Thanks.  I think I had an action item about doing something like that too.  But it would be better coming from you anyway. :)
13:45 jclift johnmark: Nicely worded. :)
13:46 johnmark short and sweet
13:53 hagarth joined #gluster-dev
14:08 jobewan joined #gluster-dev
14:15 _Bryan_ joined #gluster-dev
14:23 wushudoin joined #gluster-dev
14:26 lalatenduM_ joined #gluster-dev
14:28 hagarth joined #gluster-dev
14:34 ndevos johnmark: is there a list of topics that is missing documentation? It helps to know what needs to be done...
14:35 * ndevos isnt offering to write everything, but has no idea what we're waiting on
14:38 hagarth ndevos: +1, I was about to reply to johnmark with the same question :)
14:38 ndevos :)
14:43 deepakcs joined #gluster-dev
14:57 lalatenduM_ hagarth, ndevos , I have created a wiki page to track pages which need attention  http://www.gluster.org/community/documentation/index.php/Doc_todo_list
14:57 glusterbot Title: Doc todo list - GlusterDocumentation (at www.gluster.org)
14:57 lalatenduM_ hagarth, ndevos but haven't sent the mail to gluster-devel and users
15:00 ndevos lalatenduM_: well, that doc has only one point on it, and its not related to the 3.5 release?
15:00 johnmark ndevos: no. we have a list of features, feature pages, and we have a /docs directory
15:01 johnmark the deal is, all new features need descriptions of basic user info
15:01 lalatenduM_ ndevos, I didn't know you looking for 3.5 in particular , this doc is for overall gluster documentation
15:01 johnmark if we *do* have this stuff and it just needs to be collated, then super
15:02 lalatenduM_ ndevos, I think you are looking for http://www.gluster.org/community/documentation/index.php/Planning35
15:02 glusterbot Title: Planning35 - GlusterDocumentation (at www.gluster.org)
15:02 ndevos lalatenduM_: yeah, just found it
15:03 ndevos johnmark: you state that we do not have the docs for all features, it would be good to know which docs are missing
15:03 johnmark ndevos: you guys figure it out. it's not like we haven't discussed this before
15:04 lalatenduM_ johnmark, ndevos we just updated http://www.gluster.org/community/documentation/index.php/Features/File_Snapshot, previously it didn'y have a usage section
15:05 lalatenduM_ http://www.gluster.org/community/documentation/index.php/Features/AFR_CLI_enhancements does not have any cli commands
15:05 glusterbot Title: Features/AFR CLI enhancements - GlusterDocumentation (at www.gluster.org)
15:05 ndevos johnmark: so with "docs", your intention is to have a copy of the feature page in the docs/ directory in the sources? meaning, the "docs" on the feature page itself is not sufficient?
15:06 * ndevos looks at http://www.gluster.org/community/documentation/index.php/Features/Brick_Failure_Detection and thinks its pretty much complete
15:06 glusterbot Title: Features/Brick Failure Detection - GlusterDocumentation (at www.gluster.org)
15:06 lalatenduM_ johnmark, ndevos check http://www.gluster.org/community/documentation/index.php/Main_Page#Documentation_for_GlusterFS
15:06 glusterbot Title: GlusterDocumentation (at www.gluster.org)
15:08 ndevos lalatenduM_: yeah, looks good to me, documentation either in the sources, or in the wiki (or both)
15:09 jclift Gah
15:09 jclift So, _every_ feature for 3.4 and 3.5 needs _user level docs_.
15:09 jclift User docs are ones that include:
15:09 lalatenduM_ ndevos, Actually Admin documents should be in code repo, but articles which can change frequently can be in wiki
15:10 jclift a) description of what a feature does, so that a user knows if it's something they'd want to use/try
15:10 * johnmark is on a call
15:10 johnmark will read backlog in a bit
15:10 lalatenduM_ jclift, we suck in user level documentation :(
15:10 jclift (most of the feature pages will have at leat the start of that)
15:10 ndevos lalatenduM_: can be, but I would prefer to have the admin guide not in the sources, but in a separate repo (but thats something else)
15:11 jclift b) Exact steps on setting it up.  eg CLI parameters, with examples
15:11 lalatenduM_ ndevos, yeah , even I have some ideas around it, it should be web accessible
15:11 jclift c) A fully worked example
15:11 jclift Anything else is "nice", but those 3 are mandatory
15:11 ndevos jclift: IMHO all features should have (a), otherwise it should have been denied for this release
15:12 lalatenduM_ ndevos, +1
15:12 ndevos jclift: same counts for (b)
15:12 ndevos well, and I expect (c) too
15:12 jclift ndevos: Well, with a) they've all got at last some basic description.  Not consistently in good depth though
15:12 lalatenduM_ we should have been strict about it from the beginning
15:13 jclift Yeah.  So we're not at the point where the code is there... and we're having to be strict about this last bit. ;)
15:13 lalatenduM_ We can't expect users to use feature without (a) (b) (c) jclift
15:13 ndevos +1 lalatenduM_, being strict from the beginning before approving a feature for a release would definitely be much better than bailing out in the last minute
15:14 jclift Fully agree.  For 3.7/4.0 we can do that
15:14 lalatenduM_ jclift, yeah, lets communicate this on gluster mailing lists
15:15 ndevos jclift: do you have an overview of which features need more details?
15:15 lalatenduM_ ndevos, most of the features in 3.5 does not have (b) and (c)
15:15 * jclift opened the pages for each of the 3.5 features, and 80% of them are missing anything useful for users
15:16 jclift (as of abt an hour ago)
15:16 ndevos lalatenduM_: oh, okay
15:17 ndevos wait, so effectively we have a 3.5 release if the regression tests from hagarths email passes, we just hold off the announcement until the docs are ready?
15:21 ndevos (no need to wait any longer, feel free to comment)
15:23 ndevos lalatenduM_: [other topic] have you seen my email about bug status updates? http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/6050
15:23 glusterbot Title: Gmane Loom (at thread.gmane.org)
15:24 lalatenduM_ ndevos, writing a reply as we speak :)
15:24 ndevos lalatenduM_: cool :)
15:26 lalatenduM_ ndevos, replied to your email, excellent work!! this script thought came to mind when I came to know about python-bugzilla , but went out of my mind
15:27 kkeithley_ we dpm
15:27 kkeithley_ we dpm
15:27 kkeithley_ gah
15:27 ndevos is that a password?
15:27 kkeithley_ we don't have a release until Avati or I push the release button.  Which I'm not going to do until we have docs
15:27 kkeithley_ Yes, it's my heartbleed password
15:28 ndevos :P
15:29 kkeithley_ or I just can't type when my hand is one key to the right
15:29 ndevos now we at least have a litte more idea about what docs are needed, someone should send an email to the list so that people can write those docs
15:30 ndevos your return key is right of backspace?
15:31 kkeithley_ it's to the right of '
15:32 ndevos oh, that works too
15:33 kkeithley_ hagarth hasn't tagged the tree with v3.5.0 yet, and I think the regression test ran. Or did it?
15:34 kkeithley_ yes, it did. Now we're just waiting on docs
15:42 ndevos so, docs on the feature page are sufficient, or do we have to request patches for the docs in teh docs/ directory?
15:45 kkeithley_ I'll be satisfied with them being published somewhere, anywhere.
15:45 ndevos some of the feature pages are incomplete, do we know if those features have been documented elsewhere?
15:51 kkeithley_ maybe the docs team have something, but it's 20:00 in Bangalore so probably not going to get anything from them now
15:53 ndevos sure, I'm just trying to figure out if anyone knows exactly which docs are still missing
16:04 johnmark jclift: ^^^
16:04 johnmark ndevos: I'll defer to jclift on that
16:11 jclift Gah.
16:11 jclift Ok, I'll friggin write up a list and detail the damn stuff. ;)
16:12 jclift Expect an email to the list in 1/2 hour.
16:12 ndevos thanks, jclift!
16:35 an joined #gluster-dev
16:49 ndevos xavih: http://koji.fedoraproject.org/koji/taskinfo?taskID=6725154 is building now, could you test the packages from http://koji.fedoraproject.org/scratch/devos/task_6725154 when it is done?
16:49 glusterbot Title: build (f20-candidate, wireshark-1.10.1-1.fc20.0.xavih.src.rpm) | Task Info | koji (at koji.fedoraproject.org)
16:49 ndevos xavih: no need to rush, I'll follow up on that tomorrow
16:52 jclift k, this is taking a bit longer to write up than I expected.
16:52 jclift Might take another hour
16:56 ndevos xavih: scratch that, the build failed due to some compile errors, unrelated to my change :-/
17:03 jclift Ok, first draft email here: http://titanpad.com/gluster35-docs-email
17:03 glusterbot Title: TitanPad: gluster35-docs-email (at titanpad.com)
17:04 jclift Now to figure out which features actually made it, and remove any that didn't...
17:07 lpabon joined #gluster-dev
17:12 jclift Does anyone know whether the "Exposing Volume Capabilities" feature made it into 3.5?
17:12 jclift Not seeing it in the release notes, and it's status info isn't filled out on its feature page
17:20 ndevos xavih: corrected build: http://koji.fedoraproject.org/koji/taskinfo?taskID=6725197 , download becomes available at http://koji.fedoraproject.org/scratch/devos/task_6725197
17:20 glusterbot Title: build (f20-candidate, wireshark-1.10.1-1.fc20.0.xavih.src.rpm) | Task Info | koji (at koji.fedoraproject.org)
17:21 jclift ndevos: Just emailed it
17:22 ndevos jclift: ah, I was just going throug the titanpad and wanted to ask some questions...
17:22 jclift Heh
17:22 jclift Ask here?
17:23 ndevos you listed "Brick Failure Detection", I'm wondering what more to document about it, the feature page looks complete to me
17:23 jclift Looking
17:25 jclift ndevos: We're expecting stuff in /doc directory, so for that feature it's looking like it'd just mean cut-n-paste-n-cleanup of that into an asciidoc doc
17:26 ndevos jclift: oh, and kkeithley_ said "I'll be satisfied with them being published somewhere, anywhere." :-/
17:27 ndevos jclift: so, we'll be expecting a lot more patches, both for the master and release-3.5 branches?
17:36 jclift ndevos: Yep
17:37 ndevos jclift: could you follow up on your own email, and mention that the expectation is that documentation should be added to the git repo, both branches?
17:37 ndevos jclift: and, possible file a tracker bug for the doc-additions, and preferably a bug for each feature
17:38 ndevos jclift: install python-bugzilla, and use the bugzilla command to create those bugs ;)
17:38 jclift Meh
17:39 ndevos well, those patches will need new bug, anything that accelerate the release would be welcome, I think?
17:40 ndevos but, I'll be out for today, still did not have dinner... I might be back online later
17:40 jclift Use the 3.5 tracker bz?
17:41 ndevos sure, can use the 3.5 tracker bug for all the doc update bugs too
17:42 * ndevos goes afk
18:11 hchiramm__ joined #gluster-dev
18:47 johnmark ndevos, jclift: thanks, guys
19:09 kkeithley_ (01:26:34 PM) ndevos: jclift: oh, and kkeithley_ said "I'll be satisfied with them being published somewhere, anywhere." :-/     Well, it's a good thing I'm not in charge
19:09 kkeithley_ ;-)
19:52 ndevos :)
20:23 pk joined #gluster-dev
21:05 badone joined #gluster-dev
21:55 awheeler_ joined #gluster-dev
22:52 hchiramm__ joined #gluster-dev

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