There are 3 issues with adding GPU and adding code to glusterFS:
1. Cost: Since you cannot stick any GTX card inside your server, you'll be
forced to buy a $2K+ card for that. That could be an issue if the GlusterFS
is made out of old/cheap servers and the company/institution doesn't have
money
On January 11, 2018 10:58:28 PM EST, Lindsay Mathieson
wrote:
>On 12/01/2018 3:14 AM, Darrell Budic wrote:
>> It would also add physical resource requirements to future client
>> deploys, requiring more than 1U for the server (most likely), and I’m
>
>> not likely
Thanks Vijay/Raghavendra. We will try this.
Thanks and Regards,
Ram
From: raghavendra...@gmail.com [mailto:raghavendra...@gmail.com] On Behalf Of
Raghavendra G
Sent: Thursday, January 11, 2018 11:20 PM
To: Vijay Bellur
Cc: Ram Ankireddypalle; gluster-devel@gluster.org
Subject: Re:
GlusterFS Coverity covscan results are available from
http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2018-01-12-cf37aa99
___
Gluster-devel mailing list
Gluster-devel@gluster.org
We have a new GD2 release!!
This has been a while coming. The last release happened around the
time of the Gluster summit, and we have been working hard the last 2
months.
There have been a lot of changes, most of them aimed at getting GD2 in
shape for release. We also have new commands and
On Wed, Jan 10, 2018 at 03:36:55PM -0500, Shyam Ranganathan wrote:
> Hi,
>
> As we are introducing a new protocol version, the existing gluster
> wireshark plugin [1] needs to be updated.
>
> Further this needs to get released to wireshark users in some fashion,
> which looks like a need to
On Thu, Jan 11, 2018 at 12:14:20PM -0500, Kaleb S. KEITHLEY wrote:
> On 01/11/2018 11:34 AM, Shyam Ranganathan wrote:
> >>>
> >>> One thing not covered above is what happens when GD2 fixes a high priority
> >>> bug between releases of glusterfs.
> >>>
> >>> Once option is we wait until the next
Nigel,
Could you give a machine where geo-rep is failing even with bashrc fix to
debug ?
Thanks,
Kotresh HR
On Fri, Jan 12, 2018 at 3:54 PM, Amar Tumballi wrote:
> Can we have a separate test case to validate for all the basic necessity
> for whole test suite to pass?
Can we have a separate test case to validate for all the basic necessity
for whole test suite to pass? That way the very first run will report an
error in the setup and we can fix it faster, instead of waiting for the
failure which is a setup issue after 3-4hrs ?
-Amar
On Fri, Jan 12, 2018 at
On Thu, Jan 11, 2018 at 10:15 AM, Nigel Babu wrote:
> Hello folks,
>
> We may have been a little too quick to blame Meltdown on the Jenkins
> failures yesterday. In any case, we've open a ticket with our provider and
> they're looking into the failures. I've looked at the last
10 matches
Mail list logo