Re: [Users] oVirt 3.2 on CentOS with Gluster 3.3

2013-03-13 Thread Dan Kenigsberg
On Mon, Mar 11, 2013 at 12:34:51PM +0200, Dan Kenigsberg wrote: On Mon, Mar 11, 2013 at 06:09:56AM -0400, Balamurugan Arumugam wrote: Rob, It seems that a bug in vdsm code is hiding the real issue. Could you do a sed -i s/ParseError/ElementTree.ParseError

Re: [Users] oVirt 3.2 on CentOS with Gluster 3.3

2013-03-13 Thread Federico Simoncelli
Baron aba...@redhat.com Sent: Wednesday, March 13, 2013 9:03:39 PM Subject: Re: [Users] oVirt 3.2 on CentOS with Gluster 3.3 On Mon, Mar 11, 2013 at 12:34:51PM +0200, Dan Kenigsberg wrote: On Mon, Mar 11, 2013 at 06:09:56AM -0400, Balamurugan Arumugam wrote: Rob, It seems

Re: [Users] oVirt 3.2 on CentOS with Gluster 3.3

2013-03-13 Thread Dan Kenigsberg
...@zwissler.org, users@ovirt.org, a...@ovirt.org, Aravinda VK avish...@redhat.com, Ayal Baron aba...@redhat.com Sent: Wednesday, March 13, 2013 9:03:39 PM Subject: Re: [Users] oVirt 3.2 on CentOS with Gluster 3.3 On Mon, Mar 11, 2013 at 12:34:51PM +0200, Dan Kenigsberg wrote: On Mon, Mar 11, 2013

Re: [Users] oVirt 3.2 on CentOS with Gluster 3.3

2013-03-09 Thread Dan Kenigsberg
On Wed, Mar 06, 2013 at 02:34:10PM +0530, Balamurugan Arumugam wrote: On 03/06/2013 01:20 PM, Dan Kenigsberg wrote: On Tue, Mar 05, 2013 at 10:08:48AM -0800, Rob Zwissler wrote: On Mon, Mar 4, 2013 at 11:46 PM, Dan Kenigsberg dan...@redhat.com wrote: Rob, It seems that a bug in vdsm code is

Re: [Users] oVirt 3.2 on CentOS with Gluster 3.3

2013-03-07 Thread Dave Neary
Hi Rob, On 03/06/2013 05:59 PM, Rob Zwissler wrote: On one hand I like oVirt, I think you guys have done a good job with this, and it is free software so I don't want to complain. But on the other hand, if you release a major/stable release (ie: oVirt 3.2), but it relies on a major/critical

Re: [Users] oVirt 3.2 on CentOS with Gluster 3.3

2013-03-07 Thread Vijay Bellur
On 03/07/2013 04:36 PM, Dave Neary wrote: Hi Rob, On 03/06/2013 05:59 PM, Rob Zwissler wrote: On one hand I like oVirt, I think you guys have done a good job with this, and it is free software so I don't want to complain. But on the other hand, if you release a major/stable release (ie: oVirt

Re: [Users] oVirt 3.2 on CentOS with Gluster 3.3

2013-03-06 Thread Shireesh Anjal
On 03/05/2013 06:08 AM, Rob Zwissler wrote: Running CentOS 6.3 with the following VDSM packages from dre's repo: vdsm-xmlrpc-4.10.3-0.30.19.el6.noarch vdsm-gluster-4.10.3-0.30.19.el6.noarch vdsm-python-4.10.3-0.30.19.el6.x86_64 vdsm-4.10.3-0.30.19.el6.x86_64 vdsm-cli-4.10.3-0.30.19.el6.noarch

Re: [Users] oVirt 3.2 on CentOS with Gluster 3.3

2013-03-06 Thread Balamurugan Arumugam
On 03/05/2013 01:16 PM, Dan Kenigsberg wrote: On Mon, Mar 04, 2013 at 04:38:50PM -0800, Rob Zwissler wrote: Running CentOS 6.3 with the following VDSM packages from dre's repo: vdsm-xmlrpc-4.10.3-0.30.19.el6.noarch vdsm-gluster-4.10.3-0.30.19.el6.noarch vdsm-python-4.10.3-0.30.19.el6.x86_64

Re: [Users] oVirt 3.2 on CentOS with Gluster 3.3

2013-03-06 Thread Balamurugan Arumugam
On 03/06/2013 01:20 PM, Dan Kenigsberg wrote: On Tue, Mar 05, 2013 at 10:08:48AM -0800, Rob Zwissler wrote: On Mon, Mar 4, 2013 at 11:46 PM, Dan Kenigsberg dan...@redhat.com wrote: Rob, It seems that a bug in vdsm code is hiding the real issue. Could you do a sed -i

Re: [Users] oVirt 3.2 on CentOS with Gluster 3.3

2013-03-06 Thread Dan Kenigsberg
On Wed, Mar 06, 2013 at 02:04:29PM +0530, Shireesh Anjal wrote: On 03/05/2013 06:08 AM, Rob Zwissler wrote: Running CentOS 6.3 with the following VDSM packages from dre's repo: vdsm-xmlrpc-4.10.3-0.30.19.el6.noarch vdsm-gluster-4.10.3-0.30.19.el6.noarch vdsm-python-4.10.3-0.30.19.el6.x86_64

Re: [Users] oVirt 3.2 on CentOS with Gluster 3.3

2013-03-06 Thread Aravinda
Hi, Sent a patch to handle ParseError attribute issue. vdsm still depends on newer(3.4) version of glusterfs, but Python ParseError is fixed. http://gerrit.ovirt.org/#/c/12752/ -- regards Aravinda On 03/06/2013 01:20 PM, Dan Kenigsberg wrote: On Tue, Mar 05, 2013 at 10:08:48AM -0800, Rob

Re: [Users] oVirt 3.2 on CentOS with Gluster 3.3

2013-03-06 Thread Rob Zwissler
On Wed, Mar 6, 2013 at 12:34 AM, Shireesh Anjal san...@redhat.com wrote: oVirt 3.2 needs a newer (3.4.0) version of glusterfs, which is currently in alpha and hence not available in stable repositories. http://bits.gluster.org/pub/gluster/glusterfs/3.4.0alpha/ This issue has been reported

Re: [Users] oVirt 3.2 on CentOS with Gluster 3.3

2013-03-06 Thread Shireesh Anjal
On 03/06/2013 10:29 PM, Rob Zwissler wrote: On Wed, Mar 6, 2013 at 12:34 AM, Shireesh Anjal san...@redhat.com wrote: oVirt 3.2 needs a newer (3.4.0) version of glusterfs, which is currently in alpha and hence not available in stable repositories.

Re: [Users] oVirt 3.2 on CentOS with Gluster 3.3

2013-03-05 Thread Rob Zwissler
On Mon, Mar 4, 2013 at 11:46 PM, Dan Kenigsberg dan...@redhat.com wrote: Rob, It seems that a bug in vdsm code is hiding the real issue. Could you do a sed -i s/ParseError/ElementTree.ParseError /usr/share/vdsm/gluster/cli.py restart vdsmd, and retry? Bala, would you send a patch

Re: [Users] oVirt 3.2 on CentOS with Gluster 3.3

2013-03-05 Thread Dan Kenigsberg
On Tue, Mar 05, 2013 at 10:08:48AM -0800, Rob Zwissler wrote: On Mon, Mar 4, 2013 at 11:46 PM, Dan Kenigsberg dan...@redhat.com wrote: Rob, It seems that a bug in vdsm code is hiding the real issue. Could you do a sed -i s/ParseError/ElementTree.ParseError

[Users] oVirt 3.2 on CentOS with Gluster 3.3

2013-03-04 Thread Rob Zwissler
Running CentOS 6.3 with the following VDSM packages from dre's repo: vdsm-xmlrpc-4.10.3-0.30.19.el6.noarch vdsm-gluster-4.10.3-0.30.19.el6.noarch vdsm-python-4.10.3-0.30.19.el6.x86_64 vdsm-4.10.3-0.30.19.el6.x86_64 vdsm-cli-4.10.3-0.30.19.el6.noarch And the following gluster packages from the

Re: [Users] oVirt 3.2 on CentOS with Gluster 3.3

2013-03-04 Thread Dan Kenigsberg
On Mon, Mar 04, 2013 at 04:38:50PM -0800, Rob Zwissler wrote: Running CentOS 6.3 with the following VDSM packages from dre's repo: vdsm-xmlrpc-4.10.3-0.30.19.el6.noarch vdsm-gluster-4.10.3-0.30.19.el6.noarch vdsm-python-4.10.3-0.30.19.el6.x86_64 vdsm-4.10.3-0.30.19.el6.x86_64