Camelia, the Perl 6 bug

IRC log for #gluster-dev, 2013-02-18

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

All times shown according to UTC.

Time Nick Message
01:36 bharata joined #gluster-dev
01:38 bala joined #gluster-dev
02:46 bulde joined #gluster-dev
04:12 hagarth joined #gluster-dev
04:24 sripathi joined #gluster-dev
04:40 an joined #gluster-dev
04:51 deepakcs joined #gluster-dev
04:56 sgowda joined #gluster-dev
04:58 bala joined #gluster-dev
04:59 deepakcs bala, hi
05:00 deepakcs is there a python binding for gluster cli that i can use in general as a standalone package ?
05:02 deepakcs i found 2 projects googling.. glupy ( this is more for writing translators in python - iiuc) and python-gluster ( not much updated since few months ), hence the Q
05:02 sripathi joined #gluster-dev
05:04 bala deepakcs: there is no straight-forward python bindings available
05:04 bala deepakcs: vdsm/gluster/cli.py is the one available
05:04 deepakcs bala,  i want to use it as part of autotest
05:05 deepakcs bala, is there any plan of contributing the vdsm gluster plugin as a standalone project to python pip ?
05:05 deepakcs bala, my aim is to use it outside of vdsm scope
05:06 bala deepakcs:  no plan as such.  having a standalone gluster cli python binding is easy to extract from vdsm
05:07 bala deepakcs: from vdsm.gluster import cli as gcli
05:07 bala deepakcs: one prob is supervdsm :)
05:07 deepakcs bala, but for that vdsm shud be present on the system rite ? oethewise how can i do from vdsm.gluster
05:08 deepakcs bala, as i said.. i was looking at using as part of autotest ( not vdsm)
05:08 deepakcs and automating the qemu-kvm gluster backend testing
05:08 bala deepakcs: ok got it
05:08 deepakcs in that system vdsm won't be present
05:09 deepakcs bala, i think its a good idea to think if its possible to contribute the vdsm gluster plugin as a standalone to python repository
05:09 bala deepakcs: its good idea to have python binding as separate proj outside of vdsm
05:09 deepakcs bala, exactly.. supervdsm part of gluster/cli.py can be replaced by a thread or some entity that takes on root priv
05:09 vpshastry joined #gluster-dev
05:10 deepakcs bala, bcos thats all u need to really execute gluster cli
05:10 bala deepakcs: yes that can be done
05:11 deepakcs bala, i think there is some procedure to follow for contributing something to python pip repo... the same gluster/cli.py can be nicely packaged and contributed, it should help a  lot i feel
05:12 deepakcs bala, any idea how is this different ? (https://github.com/joejulian/python-gluster)
05:13 deepakcs bala, it would be goood to have 1 codebase ( hence reuse vdsm gluster plugin) between vdsm and standalone gluster python binding
05:13 bala deepakcs: checking
05:17 bala deepakcs: its not fully complete
05:18 deepakcs bala, but how is that diff from ur vdsm gluster plugin ?
05:18 bala deepakcs: also its not using xml output
05:18 deepakcs bala, ya so looks outdated as well
05:19 bala deepakcs: currently implemented for volume create/info
05:19 bala deepakcs: and peer detach/probe/status
05:19 deepakcs bala, i feel its a good idea then to push ur vdsm gluster plugin which is complete and kept up2date ( for obvious reasons :) ) forked and contributed to python repo
05:20 deepakcs bala, eventually i should be able to install gluster python via pip-pyton :)
05:21 bala deepakcs: yes. i would like to do some thought-process before doing it
05:22 bala deepakcs: mainly how generic it would be
05:22 sahina joined #gluster-dev
05:22 sgowda joined #gluster-dev
05:23 deepakcs bala, yup, let me know if I can help any
05:25 bala deepakcs: sure
05:34 mohankumar joined #gluster-dev
05:48 sgowda joined #gluster-dev
06:00 aravindavk joined #gluster-dev
06:03 bulde1 joined #gluster-dev
06:09 raghu joined #gluster-dev
06:20 overclk joined #gluster-dev
06:25 hagarth joined #gluster-dev
06:31 an joined #gluster-dev
06:32 sripathi joined #gluster-dev
06:35 16WAAGGWY joined #gluster-dev
06:37 bulde joined #gluster-dev
06:55 hagarth joined #gluster-dev
07:01 sripathi1 joined #gluster-dev
07:11 deepakcs joined #gluster-dev
07:42 badone joined #gluster-dev
07:44 quillo joined #gluster-dev
08:16 sahina joined #gluster-dev
08:24 bala joined #gluster-dev
08:54 puebele joined #gluster-dev
08:57 gbrand_ joined #gluster-dev
09:02 bala joined #gluster-dev
09:13 puebele joined #gluster-dev
09:16 sahina joined #gluster-dev
09:53 sripathi joined #gluster-dev
09:59 gbrand_ joined #gluster-dev
10:17 sghosh1 joined #gluster-dev
10:21 sripathi joined #gluster-dev
10:27 an joined #gluster-dev
10:27 sripathi joined #gluster-dev
11:13 sahina joined #gluster-dev
12:34 hagarth joined #gluster-dev
12:35 edward1 joined #gluster-dev
13:06 mohankumar sgowda: hagarth: i have one minor issue in BD xlator (gluster volume help output)
13:07 mohankumar can i post the fix using rfc.sh or do i need to open a bz# before posting a fix ?
13:27 hagarth joined #gluster-dev
13:40 bulde joined #gluster-dev
13:49 vpshastry joined #gluster-dev
14:02 sgowda mohan: Do you have any existing related bug?
14:03 hagarth sgowda: mohan seems to have left
14:03 vpshastry left #gluster-dev
14:04 sgowda hagarth: ok, will ping him tomorrow
14:04 semiosis glusterbot can take a message & deliver it when someone comes back online...
14:05 semiosis @later tell semiosis this is the message
14:05 glusterbot semiosis: The operation succeeded.
14:05 semiosis and it just PM me
14:05 semiosis s/PM/PMed/
14:06 hagarth semiosis: thanks!
14:06 semiosis yw
14:39 deepakcs joined #gluster-dev
15:07 nixpanic joined #gluster-dev
15:08 nixpanic joined #gluster-dev
15:16 H__ joined #gluster-dev
15:16 H__ what's the recommended option for glusters' configure script to build release binaries ? (so no debug binaries) or is that just using strip afterwards ?
15:21 wushudoin joined #gluster-dev
15:32 H__ is it the install-strip makefile target ?
15:35 bala joined #gluster-dev
15:41 bgpepi joined #gluster-dev
15:43 H__ I see it compiles with "-O0 -g -O2" :-/
15:48 H__ strip:/etc/init.d/_inst.1107_: File format not recognized        ...   I guess it's not the install-strip makefile target
16:04 H__ I'm worried about the unkown-brick lines. How can I check if glusterd upgrade worked ? http://dpaste.org/YxYmR/
16:16 bala joined #gluster-dev
16:38 overclk joined #gluster-dev
17:05 an joined #gluster-dev
17:29 sghosh joined #gluster-dev
17:35 an joined #gluster-dev
17:36 bfoster joined #gluster-dev
17:52 __Bryan__ joined #gluster-dev
18:11 gbrand__ joined #gluster-dev
18:35 an joined #gluster-dev
18:38 gbrand_ joined #gluster-dev
19:54 an joined #gluster-dev
22:58 badone joined #gluster-dev

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