[ovirt-users] Re: user role

[Tony Brian Albers]

Godmorgen Kim,

Not sure this is actually doable. IMO you're trying to make a kind of
not-really-admins. 

Others might have better ideas than me, but I'd look into some sort of
provisioning tool where you can use a more fine-grained
access/permissions control.

/tony


On Tue, 2019-09-17 at 06:29 +, kim.karga...@noroff.no wrote:
> Hi,
> 
> We are an Higher Education Institution and have set up oVirt 4.3 as a
> Virtual Lab Environment, for both on-campus and distance learning
> students. We have integrated AD and can log in with AD credentials
> for users. However, I am struggling to find the right user role for
> normal student users. Basically, they need to be able to do the
> following:
> 1. Create a new VM and select from either a template or select an
> uploaded ISO
> 2. Start the VM
> 3. Restart the VM
> 4. Shutdown the VM
> 5. Snapshot the VM
> 6. Connect to the VM using either spice or vnc/novnc
> 7. Create a disk
> 8. Connect to the student network (only would be preferable here) as
> we have management networks that we dont want the students be be able
> to see or select (if possible)
> 
> I have tested using the PowerUserRole, but that does not allow me to
> select VNC/noVNC or spice and does not allow me to install from an
> ISO, only a template. Any suggestions on role that I can give these
> users?
> 
> Thanks.
> 
> Kind regards
> 
> Kim
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct: 
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives: 
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/4C2KCNPOR2VTJVHZZSIXTVGC54RKDY3S/
-- 
Tony Albers - Systems Architect - IT Development
Royal Danish Library, Victor Albecks Vej 1, 8000 Aarhus C, Denmark
Tel: +45 2566 2383 - CVR/SE: 2898 8842 - EAN: 5798000792142
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/5BOKYBBYIOSHZAH6VUNSJUIZBHMOFDHU/

[ovirt-users] Re: Does cluster upgrade wait for heal before proceeding to next host?

[Strahil]

As far as I know,

The UI allows the administrator to override the gluster status, although I 
always use that protection.

In my opinion gluster health (especially in my setup - replica2 arbiter1) is 
very important.

Best Regards,
Strahil NikolovOn Sep 17, 2019 00:47, Jayme  wrote:
>
> Strahil, yes this is similar to the approach I have used to upgrade my hci 
> cluster. This thread is in regards to the ui cluster upgrade procedure. It 
> fails to update after the first host is rebooted because the gluster volume 
> is still in a healing state and the attempt to set the second host to 
> maintenance fails because quorum is not met. 
>
> On Mon, Sep 16, 2019 at 1:41 PM Strahil  wrote:
>>
>> I keep reading this chain and I still don't get what/who should wait for the 
>> cluster to heal...
>> Is there some kind of built-in autopatching feature?
>>
>> Here is my approach:
>> 1. Set global maintenance
>> 2. Power off the engine
>> 3. Create a  gluster snapshot of the engine's volume
>> 4. Power on engine manually
>> 5. Check engine status
>> 6. Upgrade engine
>> 7. Upgrade engine's OS
>> 8. Reboot engine and check health
>> 9. Remove global maintenance
>> 10. Set a host into local maintenance (evacuate all VMs)
>> 11. Use UI to patch the host (enable autoreboot)
>> 12. When host is up - login and check gluster volumes' heal status
>> 13. Remove maintenance for the host and repeate for the rest of the cluster.
>>
>> I realize that for large clusters this approach is tedious and an automatic 
>> approach can be scripted.
>>
>> Best Regards,
>> Strahil Nikolov
>>
>> On Sep 16, 2019 11:02, Kaustav Majumder  wrote:
>>>
>>> Hi Jayme,
>>> It would be great if you could raise a bug regarding the same.
>>>
>>> On Wed, Sep 11, 2019 at 5:05 PM Jayme  wrote:

 This sounds similar to the issue I hit with the cluster upgrade process in 
 my environment. I have large 2tb ssds and most of my vms are several 
 hundred Gbs in size. The heal process after host reboot can take 5-10 
 minutes to complete. I may be able to address this with better gluster 
 tuning. 

 Either way the upgrade process should be aware of the heal status and wait 
 for it to complete before attempting to move on to the next host. 


 On Wed, Sep 11, 2019 at 3:53 AM Sahina Bose  wrote:
>
>
>
> On Fri, Aug 9, 2019 at 3:41 PM Martin Perina  wrote:
>>
>>
>>
>> On Thu, Aug 8, 2019 at 10:25 AM Sandro Bonazzola  
>> wrote:
>>>
>>>
>>>
>>> Il giorno mar 6 ago 2019 alle ore 23:17 Jayme  ha 
>>> scritto:

 I’m aware of the heal process but it’s unclear to me if the update 
 continues to run while the volumes are healing and resumes when they 
 are done. There doesn’t seem to be any indication in the ui (unless 
 I’m mistaken)
>>>
>>>
>>> Adding @Martin Perina , @Sahina Bose   and ___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/RXIIK2PEA7D4H6EXRKLDOEUMLITL6HZ6/

[ovirt-users] user role

[kim . kargaard]

Hi,

We are an Higher Education Institution and have set up oVirt 4.3 as a Virtual 
Lab Environment, for both on-campus and distance learning students. We have 
integrated AD and can log in with AD credentials for users. However, I am 
struggling to find the right user role for normal student users. Basically, 
they need to be able to do the following:
1. Create a new VM and select from either a template or select an uploaded ISO
2. Start the VM
3. Restart the VM
4. Shutdown the VM
5. Snapshot the VM
6. Connect to the VM using either spice or vnc/novnc
7. Create a disk
8. Connect to the student network (only would be preferable here) as we have 
management networks that we dont want the students be be able to see or select 
(if possible)

I have tested using the PowerUserRole, but that does not allow me to select 
VNC/noVNC or spice and does not allow me to install from an ISO, only a 
template. Any suggestions on role that I can give these users?

Thanks.

Kind regards

Kim
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/4C2KCNPOR2VTJVHZZSIXTVGC54RKDY3S/

[ovirt-users] Cannot Activate iSCSI Storage Domain After Errors

[Clint Boggio]

Good Day To all;

oVirt 4.3.4.3-1.el7
6 Dell R710 oVirt Nodes
10 gig Infiniband iSCSI
Standalone Engine

After an error during scheduled automated VM backkup, the iSCSi datastore that 
the VMs beinng backed up lived on suddenly went inactive and refuse to activate.

The backup job did not finish as the source datastore went inactive but the 
task did clear from the console after i restarted the ovirt-engine service.

I have tried:

1. Restart the ovirt-engine service
2. Restarted the engine physical server.
3. Tried to migrate the VM disks to a different datastore (failure)

The virtual machines that are currently living on the inactive datastore are 
still running and accessible.

Trying to reboot one of those VM as a test fails as the VM will not come up due 
to the system believing that the datastore is inactive.

From engin.log:


2019-09-15 17:09:08,787-05 INFO  
[org.ovirt.engine.core.bll.storage.disk.RemoveDiskCommand] 
(EE-ManagedThreadFactory-commandCoordinator-Thread-8) [fbdd9b7] Removing 
'Wildix4-PBX_snapshot_metadata' disk
2019-09-15 17:09:13,399-05 ERROR 
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(EE-ManagedThreadFactory-commandCoordinator-Thread-8) [fbdd9b7] EVENT_ID: 
IRS_BROKER_COMMAND_FAILURE(10,803), VDSM command DeleteImageGroupVDS failed: 
General Storage Exception: ('5 [\'  Logical volume 
d1c5f4da-9024-4599-9135-4dabafe86cf8/c5f64501-142b-4a38-9b9c-faf283a64b06 
changed.\'] [\'  WARNING: This metadata update is NOT backed up.\', \'  
WARNING: Combining activation change with other commands is not advised.\', \'  
/dev/mapper/36001405f448f60ecea7479f9d920ac51: Checksum error at offset 
19198423553536\', "  Couldn\'t read volume group metadata from 
/dev/mapper/36001405f448f60ecea7479f9d920ac51.", \'  Metadata location on 
/dev/mapper/36001405f448f60ecea7479f9d920ac51 at 19198423553536 has invalid 
summary for VG.\', \'  Failed to read metadata summary from 
/dev/mapper/36001405f448f60ecea7479f9d920ac51\', \'  Failed to scan VG from 
/dev/mapper/36001405f448f60ecea7479f9d920ac51\', \'  Volume group 
"d1c5f4da-9024-4599-9135-4dabafe86cf8" not found\', \'  Cannot process volume 
group 
d1c5f4da-9024-4599-9135-4dabafe86cf8\']\nd1c5f4da-9024-4599-9135-4dabafe86cf8/{\'c5f64501-142b-4a38-9b9c-faf283a64b06\':
 ImgsPar(imgs=[\'aadbfed3-af54-4400-af79-65d09b74c687\'], 
parent=\'----\')}',)
2019-09-15 17:09:13,399-05 ERROR 
[org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand] 
(EE-ManagedThreadFactory-commandCoordinator-Thread-8) [fbdd9b7] 
IrsBroker::Failed::DeleteImageGroupVDS: IRSGenericException: IRSErrorException: 
Failed to DeleteImageGroupVDS, error = General Storage Exception: ('5 [\'  
Logical volume 
d1c5f4da-9024-4599-9135-4dabafe86cf8/c5f64501-142b-4a38-9b9c-faf283a64b06 
changed.\'] [\'  WARNING: This metadata update is NOT backed up.\', \'  
WARNING: Combining activation change with other commands is not advised.\', \'  
/dev/mapper/36001405f448f60ecea7479f9d920ac51: Checksum error at offset 
19198423553536\', "  Couldn\'t read volume group metadata from 
/dev/mapper/36001405f448f60ecea7479f9d920ac51.", \'  Metadata location on 
/dev/mapper/36001405f448f60ecea7479f9d920ac51 at 19198423553536 has invalid 
summary for VG.\', \'  Failed to read metadata summary from 
/dev/mapper/36001405f448f60ecea7479f9d920ac51\', \'  Failed to scan VG from 
/dev/mapper/36001405f448f60ecea7479f9d920ac51\', \'  Volume group 
"d1c5f4da-9024-4599-9135-4dabafe86cf8" not found\', \'  Cannot process volume 
group 
d1c5f4da-9024-4599-9135-4dabafe86cf8\']\nd1c5f4da-9024-4599-9135-4dabafe86cf8/{\'c5f64501-142b-4a38-9b9c-faf283a64b06\':
 ImgsPar(imgs=[\'aadbfed3-af54-4400-af79-65d09b74c687\'], 
parent=\'----\')}',), code = 200
2019-09-15 17:09:13,463-05 ERROR 
[org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] 
(EE-ManagedThreadFactory-commandCoordinator-Thread-8) [fbdd9b7] Command 
'org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand' failed: 
EngineException: org.ovirt.engine.core.vdsbroker.irsbroker.IRSErrorException: 
IRSGenericException: IRSErrorException: Failed to DeleteImageGroupVDS, error = 
General Storage Exception: ('5 [\'  Logical volume 
d1c5f4da-9024-4599-9135-4dabafe86cf8/c5f64501-142b-4a38-9b9c-faf283a64b06 
changed.\'] [\'  WARNING: This metadata update is NOT backed up.\', \'  
WARNING: Combining activation change with other commands is not advised.\', \'  
/dev/mapper/36001405f448f60ecea7479f9d920ac51: Checksum error at offset 
19198423553536\', "  Couldn\'t read volume group metadata from 
/dev/mapper/36001405f448f60ecea7479f9d920ac51.", \'  Metadata location on 
/dev/mapper/36001405f448f60ecea7479f9d920ac51 at 19198423553536 has invalid 
summary for VG.\', \'  Failed to read metadata summary from 
/dev/mapper/36001405f448f60ecea7479f9d920ac51\', \'  Failed to scan VG from 
/dev/mapper/36001405f448f60ecea7479f9d920ac51\', \'  Volume group 
"d1c5f4da-9024-4599-913

[ovirt-users] Re: Does cluster upgrade wait for heal before proceeding to next host?

[Jayme]

Strahil, yes this is similar to the approach I have used to upgrade my hci
cluster. This thread is in regards to the ui cluster upgrade procedure. It
fails to update after the first host is rebooted because the gluster volume
is still in a healing state and the attempt to set the second host to
maintenance fails because quorum is not met.

On Mon, Sep 16, 2019 at 1:41 PM Strahil  wrote:

> I keep reading this chain and I still don't get what/who should wait for
> the cluster to heal...
> Is there some kind of built-in autopatching feature?
>
> Here is my approach:
> 1. Set global maintenance
> 2. Power off the engine
> 3. Create a  gluster snapshot of the engine's volume
> 4. Power on engine manually
> 5. Check engine status
> 6. Upgrade engine
> 7. Upgrade engine's OS
> 8. Reboot engine and check health
> 9. Remove global maintenance
> 10. Set a host into local maintenance (evacuate all VMs)
> 11. Use UI to patch the host (enable autoreboot)
> 12. When host is up - login and check gluster volumes' heal status
> 13. Remove maintenance for the host and repeate for the rest of the
> cluster.
>
> I realize that for large clusters this approach is tedious and an
> automatic approach can be scripted.
>
> Best Regards,
> Strahil Nikolov
> On Sep 16, 2019 11:02, Kaustav Majumder  wrote:
>
> Hi Jayme,
> It would be great if you could raise a bug regarding the same.
>
> On Wed, Sep 11, 2019 at 5:05 PM Jayme  wrote:
>
> This sounds similar to the issue I hit with the cluster upgrade process in
> my environment. I have large 2tb ssds and most of my vms are several
> hundred Gbs in size. The heal process after host reboot can take 5-10
> minutes to complete. I may be able to address this with better gluster
> tuning.
>
> Either way the upgrade process should be aware of the heal status and wait
> for it to complete before attempting to move on to the next host.
>
>
> On Wed, Sep 11, 2019 at 3:53 AM Sahina Bose  wrote:
>
>
>
> On Fri, Aug 9, 2019 at 3:41 PM Martin Perina  wrote:
>
>
>
> On Thu, Aug 8, 2019 at 10:25 AM Sandro Bonazzola 
> wrote:
>
>
>
> Il giorno mar 6 ago 2019 alle ore 23:17 Jayme  ha
> scritto:
>
> I’m aware of the heal process but it’s unclear to me if the update
> continues to run while the volumes are healing and resumes when they are
> done. There doesn’t seem to be any indication in the ui (unless I’m
> mistaken)
>
>
> Adding @Martin Perina  , @Sahina Bose
>and @Laura Wright   on this,
> hyperconverged deployments using cluster upgrade command would probably
> need some improvement.
>
>
> The cluster upgrade process continues to the 2nd host after the 1st host
> becomes Up. If 2nd host then fails to switch to maintenance, we stop the
> upgrade process to prevent breakage.
> Sahina, is gluster healing process status exposed in RESTAPI? If so, does
> it makes sense to wait for healing to be finished before trying to move
> next host to maintenance? Or any other ideas how to improve?
>
>
> I need to cross-check this, if we expose the heal count in the gluster
> bricks. Moving a host to maintenance does check if there are pending heal
> entries or possibility of quorum loss. And this would prevent the
> additional hosts to upgrade.
> +Gobinda Das  +Sachidananda URS 
>
>
>
>
>
> On Tue, Aug 6, 2019 at 6:06 PM Robert O'Kane  wrote:
>
> Hello,
>
> Often(?), updates to a hypervisor that also has (provides) a Gluster
> brick takes the hypervisor offline (updates often require a reboot).
>
> This reboot then makes the brick "out of sync" and it has to be resync'd.
>
> I find it a "feature" than another host that is also part of a gluster
> domain can not be updated (rebooted) before all the bricks are updated
> in order to guarantee there is not data loss. It is called Quorum, or?
>
> Always let the heal process end. Then the next update can start.
> For me there is ALWAYS a healing time before Gluster is happy again.
>
> Cheers,
>
> Robert O'Kane
>
>
> Am 06.08.2019 um 16:38 schrieb Shani Leviim:
> > Hi Jayme,
> > I can't recall such a healing time.
> > Can you please retry and attach the engine & vdsm logs so we'll be
> smarter?
> >
> > *Regards,
> > *
> > *Shani Leviim
> > *
> >
> >
> > On Tue, Aug 6, 2019 at 5:24 PM Jayme  > > wrote:
> >
> > I've yet to have cluster upgrade finish updating my three host HCI
> > cluster.  The most recent try was today moving from oVirt 4.3.3 to
> > 4.3.5.5.  The first host updates normally, but when it moves on to
> > the second host it fails to put it in maintenance and the cluster
> > upgrade stops.
> >
> > I suspect this is due to that fact that after my hosts are updated
> > it takes 10 minutes or more for all volumes to sync/heal.  I have
> > 2Tb SSDs.
> >
> > Does the cluster upgrade process take heal time in to account before
> > attempting to place the next host in maintenance to upgrade it? Or
> > is there something else that may be at fault here, or perhaps a
> > reason why the heal p

[ovirt-users] Re: Does cluster upgrade wait for heal before proceeding to next host?

[Strahil]

I keep reading this chain and I still don't get what/who should wait for the 
cluster to heal...
Is there some kind of built-in autopatching feature?

Here is my approach:
1. Set global maintenance
2. Power off the engine
3. Create a  gluster snapshot of the engine's volume
4. Power on engine manually
5. Check engine status
6. Upgrade engine
7. Upgrade engine's OS
8. Reboot engine and check health
9. Remove global maintenance
10. Set a host into local maintenance (evacuate all VMs)
11. Use UI to patch the host (enable autoreboot)
12. When host is up - login and check gluster volumes' heal status
13. Remove maintenance for the host and repeate for the rest of the cluster.


I realize that for large clusters this approach is tedious and an automatic 
approach can be scripted.

Best Regards,
Strahil NikolovOn Sep 16, 2019 11:02, Kaustav Majumder  
wrote:
>
> Hi Jayme,
> It would be great if you could raise a bug regarding the same.
>
> On Wed, Sep 11, 2019 at 5:05 PM Jayme  wrote:
>>
>> This sounds similar to the issue I hit with the cluster upgrade process in 
>> my environment. I have large 2tb ssds and most of my vms are several hundred 
>> Gbs in size. The heal process after host reboot can take 5-10 minutes to 
>> complete. I may be able to address this with better gluster tuning. 
>>
>> Either way the upgrade process should be aware of the heal status and wait 
>> for it to complete before attempting to move on to the next host. 
>>
>>
>> On Wed, Sep 11, 2019 at 3:53 AM Sahina Bose  wrote:
>>>
>>>
>>>
>>> On Fri, Aug 9, 2019 at 3:41 PM Martin Perina  wrote:



 On Thu, Aug 8, 2019 at 10:25 AM Sandro Bonazzola  
 wrote:
>
>
>
> Il giorno mar 6 ago 2019 alle ore 23:17 Jayme  ha 
> scritto:
>>
>> I’m aware of the heal process but it’s unclear to me if the update 
>> continues to run while the volumes are healing and resumes when they are 
>> done. There doesn’t seem to be any indication in the ui (unless I’m 
>> mistaken)
>
>
> Adding @Martin Perina , @Sahina Bose   and @Laura Wright  on this, 
> hyperconverged deployments using cluster upgrade command would probably 
> need some improvement.


 The cluster upgrade process continues to the 2nd host after the 1st host 
 becomes Up. If 2nd host then fails to switch to maintenance, we stop the 
 upgrade process to prevent breakage.
 Sahina, is gluster healing process status exposed in RESTAPI? If so, does 
 it makes sense to wait for healing to be finished before trying to move 
 next host to maintenance? Or any other ideas how to improve?
>>>
>>>
>>> I need to cross-check this, if we expose the heal count in the gluster 
>>> bricks. Moving a host to maintenance does check if there are pending heal 
>>> entries or possibility of quorum loss. And this would prevent the 
>>> additional hosts to upgrade.
>>> +Gobinda Das +Sachidananda URS 
>>>
>
>  
>>
>>
>> On Tue, Aug 6, 2019 at 6:06 PM Robert O'Kane  wrote:
>>>
>>> Hello,
>>>
>>> Often(?), updates to a hypervisor that also has (provides) a Gluster 
>>> brick takes the hypervisor offline (updates often require a reboot).
>>>
>>> This reboot then makes the brick "out of sync" and it has to be 
>>> resync'd.
>>>
>>> I find it a "feature" than another host that is also part of a gluster 
>>> domain can not be updated (rebooted) before all the bricks are updated 
>>> in order to guarantee there is not data loss. It is called Quorum, or?
>>>
>>> Always let the heal process end. Then the next update can start.
>>> For me there is ALWAYS a healing time before Gluster is happy again.
>>>
>>> Cheers,
>>>
>>> Robert O'Kane
>>>
>>>
>>> Am 06.08.2019 um 16:38 schrieb Shani Leviim:
>>> > Hi Jayme,
>>> > I can't recall such a healing time.
>>> > Can you please retry and attach the engine & vdsm logs so we'll be 
>>> > smarter?
>>> > 
>>> > *Regards,
>>> > *
>>> > *Shani Leviim
>>> > *
>>> > 
>>> > 
>>> > On Tue, Aug 6, 2019 at 5:24 PM Jayme >> > > wrote:
>>> > 
>>> >     I've yet to have cluster upgrade finish updating my three host HCI
>>> >     cluster.  The most recent try was today moving from oVirt 4.3.3 to
>>> >     4.3.5.5.  The first host updates normally, but when it moves on to
>>> >     the second host it fails to put it in maintenance and the cluster
>>> >     upgrade stops.
>>> > 
>>> >     I suspect this is due to that fact that after my hosts are updated
>>> >     it takes 10 minutes or more for all volumes to sync/heal.  I have
>>> >     2Tb SSDs.
>>> > 
>>> >     Does the cluster upgrade process take heal time in to account 
>>> >before
>>> >     attempting to place the next host in maintenance to upgrade it? Or
>>> >     is there something else that may be

[ovirt-users] Re: Virt-Viewer issue

[Staniforth, Paul]

Hello,

   you should use remote-viewer, it's part of the virt-viewer package.



Paul Staniforth

School of Built Environment Engineering and Computing.

Leeds Beckett University

Networked Systems Analyst, Research and Engineering Support.

tel: +44 (0)113 28123754
email: p.stanifo...@leedsbeckett.ac.uk

From: Lozada, Agustin T 
Sent: 13 September 2019 15:38
To: users@ovirt.org
Subject: [ovirt-users] Virt-Viewer issue

Im building my first VM in ovirt with gluster and Im getting this issue when 
I'm opening a console session using virt-viewer. Does anyone has encountered 
this issue?


[cid:image001.png@01D56A15.FECFDAF0]
To view the terms under which this email is distributed, please go to:-
http://leedsbeckett.ac.uk/disclaimer/email/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/6TXQZVPF75OKBCHGIRVUSFDGDSNQUHZE/

[ovirt-users] Re: Does cluster upgrade wait for heal before proceeding to next host?

[Kaustav Majumder]

Hi Jayme,
It would be great if you could raise a bug regarding the same.

On Wed, Sep 11, 2019 at 5:05 PM Jayme  wrote:

> This sounds similar to the issue I hit with the cluster upgrade process in
> my environment. I have large 2tb ssds and most of my vms are several
> hundred Gbs in size. The heal process after host reboot can take 5-10
> minutes to complete. I may be able to address this with better gluster
> tuning.
>
> Either way the upgrade process should be aware of the heal status and wait
> for it to complete before attempting to move on to the next host.
>
>
> On Wed, Sep 11, 2019 at 3:53 AM Sahina Bose  wrote:
>
>>
>>
>> On Fri, Aug 9, 2019 at 3:41 PM Martin Perina  wrote:
>>
>>>
>>>
>>> On Thu, Aug 8, 2019 at 10:25 AM Sandro Bonazzola 
>>> wrote:
>>>


 Il giorno mar 6 ago 2019 alle ore 23:17 Jayme  ha
 scritto:

> I’m aware of the heal process but it’s unclear to me if the update
> continues to run while the volumes are healing and resumes when they are
> done. There doesn’t seem to be any indication in the ui (unless I’m
> mistaken)
>

 Adding @Martin Perina  , @Sahina Bose
and @Laura Wright   on this,
 hyperconverged deployments using cluster upgrade command would probably
 need some improvement.

>>>
>>> The cluster upgrade process continues to the 2nd host after the 1st host
>>> becomes Up. If 2nd host then fails to switch to maintenance, we stop the
>>> upgrade process to prevent breakage.
>>> Sahina, is gluster healing process status exposed in RESTAPI? If so,
>>> does it makes sense to wait for healing to be finished before trying to
>>> move next host to maintenance? Or any other ideas how to improve?
>>>
>>
>> I need to cross-check this, if we expose the heal count in the gluster
>> bricks. Moving a host to maintenance does check if there are pending heal
>> entries or possibility of quorum loss. And this would prevent the
>> additional hosts to upgrade.
>> +Gobinda Das  +Sachidananda URS 
>>
>>


>
> On Tue, Aug 6, 2019 at 6:06 PM Robert O'Kane  wrote:
>
>> Hello,
>>
>> Often(?), updates to a hypervisor that also has (provides) a Gluster
>> brick takes the hypervisor offline (updates often require a reboot).
>>
>> This reboot then makes the brick "out of sync" and it has to be
>> resync'd.
>>
>> I find it a "feature" than another host that is also part of a
>> gluster
>> domain can not be updated (rebooted) before all the bricks are
>> updated
>> in order to guarantee there is not data loss. It is called Quorum, or?
>>
>> Always let the heal process end. Then the next update can start.
>> For me there is ALWAYS a healing time before Gluster is happy again.
>>
>> Cheers,
>>
>> Robert O'Kane
>>
>>
>> Am 06.08.2019 um 16:38 schrieb Shani Leviim:
>> > Hi Jayme,
>> > I can't recall such a healing time.
>> > Can you please retry and attach the engine & vdsm logs so we'll be
>> smarter?
>> >
>> > *Regards,
>> > *
>> > *Shani Leviim
>> > *
>> >
>> >
>> > On Tue, Aug 6, 2019 at 5:24 PM Jayme > > > wrote:
>> >
>> > I've yet to have cluster upgrade finish updating my three host
>> HCI
>> > cluster.  The most recent try was today moving from oVirt 4.3.3
>> to
>> > 4.3.5.5.  The first host updates normally, but when it moves on
>> to
>> > the second host it fails to put it in maintenance and the
>> cluster
>> > upgrade stops.
>> >
>> > I suspect this is due to that fact that after my hosts are
>> updated
>> > it takes 10 minutes or more for all volumes to sync/heal.  I
>> have
>> > 2Tb SSDs.
>> >
>> > Does the cluster upgrade process take heal time in to account
>> before
>> > attempting to place the next host in maintenance to upgrade it?
>> Or
>> > is there something else that may be at fault here, or perhaps a
>> > reason why the heal process takes 10 minutes after reboot to
>> complete?
>> > ___
>> > Users mailing list -- users@ovirt.org 
>> > To unsubscribe send an email to users-le...@ovirt.org
>> > 
>> > Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>> > oVirt Code of Conduct:
>> > https://www.ovirt.org/community/about/community-guidelines/
>> > List Archives:
>> >
>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/5XM3QB3364ZYIPAKY4KTTOSJZMCWHUPD/
>> >
>> >
>> > ___
>> > Users mailing list -- users@ovirt.org
>> > To unsubscribe send an email to users-le...@ovirt.org
>> > Privacy Statement: https://www.ovirt.org/site/privacy-policy/

[ovirt-users] Re: CentOS 6 in oVirt

[Dominik Holler]

On Sun, Sep 15, 2019 at 2:48 PM Nir Soffer  wrote:

>
>
> On Wed, Sep 11, 2019, 10:07 Dominik Holler  wrote:
>
>> Hello,
>> are the official CentOS 6 cloud images known to work in oVirt?
>> I tried, but they seem not to work in oVirt [1], but on plain libvirt.
>> Are there any pitfalls known during using them in oVirt?
>>
>
> Why do you want to use prehisroric images?
>
>
Because we support it and we put in effort to keep it running by fixing
https://bugzilla.redhat.com/1611889
But still we lack upstream OST, to enable engineers feel comfortable to
modify
their code and make sure our functionality is not broken by our own changes
or by
those of the platform.


> Thanks
>> Dominik
>>
>>
>> [1]
>>   https://gerrit.ovirt.org/#/c/101117/
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@ovirt.org
>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/TN5SEECVFGCCMQ2QACYYEZXNLFGBYDZH/
>>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/56QZL5RQE6H4ZVLKPT3LZATQKW3GPFRS/