Due to POSIX compliance, oVirt needs 512 byte physical sector size. If your
SSD/NVME has the new standard (4096) you will need to use VDO with
'--emulate512' flag (or whatever it was named). Yet, if you already got 512
physical sector size - you can skip VDO totally.
About the mount options of
"...Tuning Gluster with VDO bellow is quite difficult and the overhead of using
VDO could
reduce performance " Yup. hense creation of a dedicated data00 volume from
the 1TB SSD each server had. Matched options listed in oVirt.. but still OCP
would not address the drive as target for
Tuning Gluster with VDO bellow is quite difficult and the overhead of using VDO
could reduce performance .
I would try with VDO compression and dedup disabled.If your SSD has 512 byte
physical & logical size, you can skip VDO at all to check performance.
Also FS mount options are very important
The response was that when I select the oVirt HCI storage volumes to deploy to
(with VDO enabled) which are a single 512GB SSD with only one small IDM VM
running. The IPI OCP 4.7 deployment fails. RH closed ticket because "gluster
volume is too slow".
I then tried to create with my other
I haven't seen your email on the gluster users' mailing list .
What was your problem with the performance ?
Best Regards,Strahil Nikolov
On Mon, Apr 26, 2021 at 17:30, penguin pages wrote:
It was on a support ticket / call I was having. I googled around and the only
article I found was
On Mon, Apr 26, 2021 at 4:30 PM penguin pages
wrote:
>
> It was on a support ticket / call I was having. I googled around and the
> only article I found was the one about features being removed.. But not
> sure if this effects oVirt / HCI.
>
> My ticket was about trying to deploy OCP on a full
It was on a support ticket / call I was having. I googled around and the only
article I found was the one about features being removed.. But not sure if this
effects oVirt / HCI.
My ticket was about trying to deploy OCP on a full SSD cluster of three nodes
and disk performance over 10Gb will
On Mon, Apr 26, 2021 at 2:34 PM penguin pages
wrote:
>
> I have been building out HCI stack with KVM/RHEV + oVirt with the HCI
> deployment process. This is very nice for small / remote site use cases,
> but with Gluster being anounced as EOL in 18 months, what is the
> replacement plan?
>
Are
What do you mean Gluster being announced as EOL? Where did you find this
information?
On Mon, Apr 26, 2021 at 9:34 AM penguin pages
wrote:
>
> I have been building out HCI stack with KVM/RHEV + oVirt with the HCI
> deployment process. This is very nice for small / remote site use cases,
> but
9 matches
Mail list logo
