[ovirt-users] Hardware for Hyperconverged oVirt: Gluster storage best practice

[Mahdi Adnan]

Hi,


4 SSDs in "distributed replica 2" volume for VM images, with additional 20 HDDs in another volume.

We had some minor XFS issues with the HDDs volume.

as for monitoring, standard snmp with few scripts to read smart report, we're still looking for a better way to monitor Gluster.

hardware is Cisco UCS C220.


We have another setup but not HC, and its equipped with 96 SSDs only.

No major issues so far.


--

Respectfully
Mahdi A. Mahdi

________________________________
From: ovirt at fateknollogee.com <ovirt at fateknollogee.com>
Sent: Sunday, June 11, 2017 4:45:30 PM
To: Mahdi Adnan
Cc: Barak Korren; Yaniv Kaul; Ovirt Users
Subject: Re: [ovirt-users] Hardware for Hyperconverged oVirt: Gluster storage best practice

Mahdi,

Can you share some more detail on your hardware?
How many total SSDs?
Have you had any drive failures?
How do you monitor for failed drives?
Was it a problem replacing failed drives?

On 2017-06-11 02:21, Mahdi Adnan wrote:
> Hi,
>
> In our setup, we used each SSD as a standalone brick "no RAID" and
> created distributed replica with sharding.
>
> Also, we are NOT managing Gluster from ovirt.
>
> --
>
> Respectfully
> MAHDI A. MAHDI
>
> -------------------------
>
> FROM: users-bounces at ovirt.org <users-bounces at ovirt.org> on behalf of
> Barak Korren <bkorren at redhat.com>
> SENT: Sunday, June 11, 2017 11:20:45 AM
> TO: Yaniv Kaul
> CC: ovirt at fateknollogee.com; Ovirt Users
> SUBJECT: Re: [ovirt-users] Hardware for Hyperconverged oVirt: Gluster
> storage best practice
>
> On 11 June 2017 at 11:08, Yaniv Kaul <ykaul at redhat.com> wrote:
>>
>>> I will install the o/s for each node on a SATADOM.
>>> Since each node will have 6x SSD for gluster storage.
>>> Should this be software RAID, hardware RAID or no RAID?
>>
>> I'd reckon that you should prefer HW RAID on software RAID, and some
> RAID on
>> no RAID at all, but it really depends on your budget, performance,
> and your
>> availability requirements.
>>
>
> Not sure that is the best advice, given the use of Gluster+SSDs for
> hosting individual VMs.
>
> Typical software or hardware RAID systems are designed for use with
> spinning disks, and may not yield any better performance on SSDs. RAID
> is also not very good when I/O is highly scattered as it probably is
> when running multiple different VMs.
>
> So we are left with using RAID solely for availability. I think
> Gluster may already provide that, so adding additional software or
> hardware layers for RAID may just degrade performance without
> providing any tangible benefits.
>
> I think just defining each SSD as a single Gluster brick may provide
> the best performance for VMs, but my understanding of this is
> theoretical, so I leave it to the Gluster people to provide further
> insight.
>
> --
> Barak Korren
> RHV DevOps team , RHCE, RHCi
> Red Hat EMEA
> redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20170611/60b85a17/attachment.html>