[ovirt-users] Re: oVirt upgrade version from 4.2 to 4.3

2019-05-18 Thread Yedidyah Bar David
On Thu, May 16, 2019 at 3:40 PM wrote: > > I cannot find an official upgrade procedure from 4.2 to 4.3 oVirt version on > this page: > https://www.ovirt.org/documentation/upgrade-guide/upgrade-guide.html > > Can you help me? As others noted, the above should be sufficient, for general upgrade i

[ovirt-users] Re: [ovirt-announce] Re: [ANN] oVirt 4.3.4 First Release Candidate is now available

2019-05-18 Thread Strahil
On this one https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.3/html-single/configuring_red_hat_virtualization_with_red_hat_gluster_storage/index#proc-To_Configure_Volumes_Using_the_Command_Line_Interface We should have the following options: performance.quick-read=off per

[ovirt-users] Re: [ovirt-announce] Re: [ANN] oVirt 4.3.4 First Release Candidate is now available

2019-05-18 Thread Strahil
OK, Can we summarize it: 1. VDO must 'emulate512=true' 2. 'network.remote-dio' should be off ? As per this: https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3/html/configuring_red_hat_openstack_with_red_hat_storage/sect-setting_up_red_hat_storage_trusted_storage_pool We sho

[ovirt-users] Re: [ovirt-announce] Re: [ANN] oVirt 4.3.4 First Release Candidate is now available

2019-05-18 Thread Sahina Bose
On Sun, 19 May 2019 at 12:21 AM, Nir Soffer wrote: > On Fri, May 17, 2019 at 7:54 AM Gobinda Das wrote: > >> From RHHI side default we are setting below volume options: >> >> { group: 'virt', >> storage.owner-uid: '36', >> storage.owner-gid: '36', >> network.ping-timeout: '30', >>

[ovirt-users] Re: [ovirt-announce] Re: [ANN] oVirt 4.3.4 First Release Candidate is now available

2019-05-18 Thread Sahina Bose
On Fri, 17 May 2019 at 2:13 AM, Strahil Nikolov wrote: > > >This may be another issue. This command works only for storage with 512 > bytes sector size. > > >Hyperconverge systems may use VDO, and it must be configured in > compatibility mode to >support > >512 bytes sector size. > > >I'm not sur

[ovirt-users] Re: [ovirt-announce] Re: [ANN] oVirt 4.3.4 First Release Candidate is now available

2019-05-18 Thread Nir Soffer
On Fri, May 17, 2019 at 7:54 AM Gobinda Das wrote: > From RHHI side default we are setting below volume options: > > { group: 'virt', > storage.owner-uid: '36', > storage.owner-gid: '36', > network.ping-timeout: '30', > performance.strict-o-direct: 'on', > network.remote-

[ovirt-users] Re: Wrong disk size in UI after expanding iscsi direct LUN

2019-05-18 Thread Nir Soffer
On Thu, May 16, 2019 at 6:10 PM Bernhard Dick wrote: > Hi, > > I've extended the size of one of my direct iSCSI LUNs. The VM is seeing > the new size but in the webinterface there is still the old size > reported. Is there a way to update this information? I already took a > look into the list bu

[ovirt-users] Re: Gluster VM image Resync Time

2019-05-18 Thread Indivar Nair
Thanks, Strahil, Sorry, got busy with some other work. But, better late than never. Regards, Indivar Nair On Wed, Mar 27, 2019 at 4:34 PM Strahil wrote: > By default ovirt uses 'sharding' which splits the files into logical > chunks. This greatly reduces healing time, as VM's disk is not alw

[ovirt-users] Re: Gluster VM image Resync Time

2019-05-18 Thread Indivar Nair
Thanks, Krutika, Sorry, got busy with some other work. But, better late than never. Regards, Indivar Nair On Thu, Mar 28, 2019 at 12:26 PM Krutika Dhananjay wrote: > Right. So Gluster stores what are called "indices" for each modified file > (or shard) > under a special hidden directory of t