Sorry to be clearer
There is 15 Spin disks total
9 SSD disks total
Spin will be split into 3x RAID-5's on the physical hosts (5 disks)
SSD will be split into 3x RAID-5's on the physical hosts (3 disks)
My plan was as you said, create a single brick on each of the 3 spin
RAID-5's and a single
if you go with RAID 5 option it is expected to have performance degradation but
you will have double protection for your data.
my suggestion, go with each HDD disks as individual bricks with replica 3
volumes and same for SSD's
___
Users mailing list -
Hi Strahil Nikolov
Thank you so much all your valuable input. Finally resolved the issue with
below actions
1) shutdown all the vms running in the volume,
2) temporarily created new folders in another hdd drive ( in all three hosts)
where it had enough free space
3) expanded the issue volum
Disabling this repo at least allows the install to succeed.
Gary
> On Dec 1, 2021, at 3:58 PM, Gary Pedretty wrote:
>
> Now there is another repo that is required but not reachable. The site
> appears to be completely down.
>
> https://copr-be.cloud.fedoraproject.org/results/sbonazzo/EL8_co
Hello,
1. I know vdsm communication adopted rpc over "stomp" and i'm wondering if
it's due to use of the message broker or any other purpose.
2. according to
https://www.ovirt.org/develop/release-management/features/infra/jsonrpc.html,
vdsm has the final plan to completely separate msg broker. Is
Now there is another repo that is required but not reachable. The site appears
to be completely down.
https://copr-be.cloud.fedoraproject.org/results/sbonazzo/EL8_collection/epel-8-x86_64/repodata/repomd.xml
[Failed to connect to copr-be.cloud.fedoraproject.org port 443: Connection
refused]
Lev
Thanks for the quick fix.
Changing to the baseurl fixed it for me now and will test the mirrors again
later today or tomorrow.
Gary
> On Dec 1, 2021, at 12:20 PM, Lev Veyde wrote:
>
> Hi Gary,
>
> Thanks for letting us know about the issue.
> Looks like the repo metadata became corrupt
Hi Gary,
Thanks for letting us know about the issue.
Looks like the repo metadata became corrupted for some reason.
I just finished re-generating the repo, and it should propagate to the
mirrors soon.
As a workaround you can temporarily modify your oVirt repo conf. file to
point to the main dist
Any idea when the download repositories will be fixed. Seems like none of the
mirrors are working so we cannot do new installs of Ovirt
Error: Error downloading packages:
Cannot download x86_64/ovirt-imageio-daemon-2.3.0-1.el8.x86_64.rpm: All
mirrors were tried
This has been happening since M
Hi,
I have ovirt version: 4.3.4.3-1.el7 I can't find in the documentation how to
set up a server disk profile during creation via the REST API. If it didn't
work during creation, then it doesn't matter later after creation.
How to please set up a disk profile server via REST API?
Thank you.
__
This is affecting me as well on RHEL 8.5 hosts.
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Wednesday, December 1st, 2021 at 2:25 AM, Gary Pedretty
wrote:
> Started happening for me yesterday. Was working just a few days ago.
>
> Gary
>
> [FAILED] ovirt-ansible-
11 matches
Mail list logo
