date:20191001

[ovirt-users] Re: Incremental backup using ovirt api

2019-10-01 Thread Eyal Shenitzky

Hi Midhun,

Incremental backup isn't supported yet in 4.3 version.

Thanks

On Sat, 28 Sep 2019 at 13:00,  wrote:

> Hi,
> I tried to take incremental backup of a vm using this script.
>
>  public function downloadDiskIncremental(){
>
>   $data=array();
>
>
>
>$xmlStr = "
> 
>   incremental
>  
> ";
>
>   $curlParam=array(
>   "url" =>
> "vms/4044e014-7e20-4dbc-abe5-64690ec45f63/diskattachments",
>   "method" => "POST",
>   "data" =>$xmlStr,
>
>
>   );
> }
>
> But it is throwing me error as
> Array ( [status] => error [message] => For correct usage, see:
> https://ovirt.bobcares.com/ovirt-engine/api/v4/model#services/disk-attachments/methods/add
> Please help me with this issue
>
> ___
> 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/7BON6MWHIDJCZ3IWTTJVWXEP2NMJYGGP/
>


-- 
Regards,
Eyal Shenitzky
___
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/H2F3MQISNVDMWPNCHPKHAFREDSZUGXJQ/

[ovirt-users] Re: Ovirt 4.2.7 won't start and drops to emergency console

2019-10-01 Thread jeremy_tourville

http://man7.org/linux/man-pages/man7/lvmthin.7.html
Command to repair a thin pool:
lvconvert --repair VG/ThinPoolLV

Repair performs the following steps:

1. Creates a new, repaired copy of the metadata.
lvconvert runs the thin_repair command to read damaged metadata from
the existing pool metadata LV, and writes a new repaired copy to the
VG's pmspare LV.

2. Replaces the thin pool metadata LV.
If step 1 is successful, the thin pool metadata LV is replaced with
the pmspare LV containing the corrected metadata. The previous thin
pool metadata LV, containing the damaged metadata, becomes visible
with the new name ThinPoolLV_tmetaN (where N is 0,1,...).

If the repair works, the thin pool LV and its thin LVs can be
activated, and the LV containing the damaged thin pool metadata can
be removed. It may be useful to move the new metadata LV (previously
pmspare) to a better PV.

If the repair does not work, the thin pool LV and its thin LVs are
lost.

This info seems to conflict with Red Hat advice. Red Hat says if metadat
volume is full don't run a lvconvert --repair operation. Now I am confused. I
am familiar with LVM and comfortable with it but this is my first time trying
to repair thin LVM. The concepts of a metadata volume are new to me.
___
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/FFN3HWUQVRPFSMXHECNJLJOFNF5ODAT6/

[ovirt-users] Re: Ovirt 4.2.7 won't start and drops to emergency console

2019-10-01 Thread jeremy_tourville

Here is my fstab file:
# /etc/fstab
# Created by anaconda on Fri Dec 21 22:26:32 2018
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
/dev/onn_vmh/ovirt-node-ng-4.2.7.1-0.20181216.0+1 / ext4 defaults,discard 1 1
UUID=9b9546f9-25d2-42a6-835b-303f32aee4b1 /boot   ext4
defaults1 2
/dev/mapper/onn_vmh-home /home ext4 defaults,discard 1 2
/dev/mapper/onn_vmh-tmp /tmp ext4 defaults,discard 1 2
/dev/mapper/onn_vmh-var /var ext4 defaults,discard 1 2
/dev/mapper/onn_vmh-var_log /var/log ext4 defaults,discard 1 2
/dev/mapper/onn_vmh-var_log_audit /var/log/audit ext4 defaults,discard 1 2
/dev/mapper/onn_vmh-swap swapswapdefaults0 0
/dev/gluster_vg1/engine_lv /gluster_bricks/engine xfs 
inode64,noatime,nodiratime 0 0
/dev/gluster_vg1/lv_vmdisks /gluster_bricks/vmstore xfs 
inode64,noatime,nodiratime 0 0
/dev/gluster_vg1/lv_datadisks /gluster_bricks/data xfs 
inode64,noatime,nodiratime 0 0
#/dev/sdd1 /gluster_bricks/iso xfs inode64,noatime,nodiratime 0 0
___
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/VYQ22EFSGRYDESRQZAAQ6E327J67JANJ/

[ovirt-users] Re: Ovirt 4.2.7 won't start and drops to emergency console

2019-10-01 Thread jeremy_tourville

I don't know why I didn't think to get some more info regarding my storage 
environment and post it here earlier.  My gluster_vg1 volume is on /dev/sda1.  
I can access the engine storage directory but I think that is because it is not 
thin provisioned.  I guess I was too bogged down in solving the problem when 
I'm stuck in emergency mode.  I had to  sneaker net my USB drive to my system 
so I could capture some info.  Anyhow here it is:

# lsblk
NAME   MAJ:MIN RM   SIZE RO 
TYPE  MOUNTPOINT
sda  8:00   5.5T  0 
disk  
└─sda1   8:10   5.5T  0 
part  
sdb  8:16   0 223.6G  0 
disk  
├─sdb1   8:17   0 1G  0 
part  /boot
└─sdb2   8:18   0 222.6G  0 
part  
  └─md1279:127  0 222.5G  0 
raid1 
├─onn_vmh-swap 253:00 4G  0 
lvm   [SWAP]
├─onn_vmh-pool00_tmeta 253:10 1G  0 
lvm   
│ └─onn_vmh-pool00-tpool   253:30 173.6G  0 
lvm   
│   ├─onn_vmh-ovirt--node--ng--4.2.7.1--0.20181216.0+1 253:40 146.6G  0 
lvm   /
│   ├─onn_vmh-pool00   253:50 173.6G  0 
lvm   
│   ├─onn_vmh-root 253:60 146.6G  0 
lvm   
│   ├─onn_vmh-home 253:70 1G  0 
lvm   /home
│   ├─onn_vmh-tmp  253:80 1G  0 
lvm   /tmp
│   ├─onn_vmh-var  253:9015G  0 
lvm   /var
│   ├─onn_vmh-var_log  253:10   0 8G  0 
lvm   /var/log
│   ├─onn_vmh-var_log_audit253:11   0 2G  0 
lvm   /var/log/audit
│   └─onn_vmh-var_crash253:12   010G  0 
lvm   /var/crash
└─onn_vmh-pool00_tdata 253:20 173.6G  0 
lvm   
  └─onn_vmh-pool00-tpool   253:30 173.6G  0 
lvm   
├─onn_vmh-ovirt--node--ng--4.2.7.1--0.20181216.0+1 253:40 146.6G  0 
lvm   /
├─onn_vmh-pool00   253:50 173.6G  0 
lvm   
├─onn_vmh-root 253:60 146.6G  0 
lvm   
├─onn_vmh-home 253:70 1G  0 
lvm   /home
├─onn_vmh-tmp  253:80 1G  0 
lvm   /tmp
├─onn_vmh-var  253:9015G  0 
lvm   /var
├─onn_vmh-var_log  253:10   0 8G  0 
lvm   /var/log
├─onn_vmh-var_log_audit253:11   0 2G  0 
lvm   /var/log/audit
└─onn_vmh-var_crash253:12   010G  0 
lvm   /var/crash
sdc  8:32   0 223.6G  0 
disk  
└─sdc1   8:33   0 222.6G  0 
part  
  └─md1279:127  0 222.5G  0 
raid1 
├─onn_vmh-swap 253:00 4G  0 
lvm   [SWAP]
├─onn_vmh-pool00_tmeta 253:10 1G  0 
lvm   
│ └─onn_vmh-pool00-tpool   253:30 173.6G  0 
lvm   
│   ├─onn_vmh-ovirt--node--ng--4.2.7.1--0.20181216.0+1 253:40 146.6G  0 
lvm   /
│   ├─onn_vmh-pool00   253:50 173.6G  0 
lvm   
│   ├─onn_vmh-root 253:60 146.6G  0 
lvm   
│   ├─onn_vmh-home 253:70 1G  0 
lvm   /home
│   ├─onn_vmh-tmp  253:80 1G  0 
lvm   /tmp
│   ├─onn_vmh-var  253:9015G  0 
lvm   /var
│   ├─onn_vmh-var_log  253:10   0 8G  0 
lvm   /var/log
│   ├─onn_vmh-var_log_audit253:11   0 2G  0 
lvm   /var/log/audit
│   └─onn_vmh-var_crash253:12   010G  0 
lvm   /var/crash
└─onn_vmh-pool00_tdata 253:20 173.6G  0 
lvm   
  └─onn_vmh-pool00-tpool   253:30 173.6G  0 
lvm   
├─onn_vmh-ovirt--node--ng--4.2.7.1--0.20181216.0+1 253:40 146.6G  0 
lvm   /
├─onn_vmh-pool00   253:50 173.6G  0 
lvm   
├─onn_vmh-root 253:6

[ovirt-users] Re: Ovirt 4.2.7 won't start and drops to emergency console

2019-10-01 Thread jeremy_tourville

"lvs -a" does not list the logical volume I am missing.
"lvdisplay -m /dev/gluster_vg1-lvthinpool-tpool_tmeta" does not work either.  
Error message is: Volume Group xxx not found.  Cannot process volume group xxx."

I am trying to follow the procedure from 
https://access.redhat.com/solutions/3251681
I am on step #2  Step 2a and 2b work without issue.  Step 2c give me an error.  
Here are the values I am using:
# lvcreate -L 2G gluster_vg3 --name tmpLV 
# lvchange -ay gluster_vg3/tmpLV
# lvconvert --thinpool gluster_vg1/lvthinpool --poolmetadata gluster_vg3/tmpLV

VG name mismatch from position arg (gluster_vg1) and option arg (gluster_vg3)

Do I need to create the LV on the same disk that failed?  (gluster_vg1)
Is creating a new LV on (gluster_vg3) ok for this situation?
___
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/OJN6VVEMQY743WFXHVZOZB3KAEIN6PWM/

[ovirt-users] Re: Failed to synchronize networks of Provider ovirt-provider-ovn

2019-10-01 Thread Mail SET Inc. Group

Few hours later i'm fixed SSL error, but get a new error

2019-10-02 01:02:38,369 root Starting server
2019-10-02 01:02:38,369 root Version: 1.2.22-1
2019-10-02 01:02:38,369 root Build date: 20190509114402
2019-10-02 01:02:38,369 root Githash: 38acbde
2019-10-02 01:02:46,471 root From: :::172.19.0.10:33644 Request: POST 
/v2.0/tokens
2019-10-02 01:02:46,471 root Request body:
{"auth": {"passwordCredentials": {"username": "admin@internal", "password": 
""}}}
2019-10-02 01:02:46,472 root Error during SSO authentication invalid_request : 
Missing parameter: 'client_secret'
Traceback (most recent call last):
  File "/usr/share/ovirt-provider-ovn/handlers/base_handler.py", line 138, in 
_handle_request
method, path_parts, content
  File "/usr/share/ovirt-provider-ovn/handlers/selecting_handler.py", line 175, 
in handle_request
return self.call_response_handler(handler, content, parameters)
  File "/usr/share/ovirt-provider-ovn/handlers/keystone.py", line 33, in 
call_response_handler
return response_handler(content, parameters)
  File "/usr/share/ovirt-provider-ovn/handlers/keystone_responses.py", line 69, 
in post_tokens
if not auth.validate_token(token):
  File "/usr/share/ovirt-provider-ovn/auth/plugin_facade.py", line 31, in 
validate_token
return auth.core.plugin.validate_token(token)
  File 
"/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/authorization_by_username.py",
 line 36, in validate_token
return self._is_user_name(token, _admin_user_name())
  File 
"/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/authorization_by_username.py",
 line 47, in _is_user_name
timeout=AuthorizationByUserName._timeout())
  File "/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/sso.py", line 131, in 
get_token_info
timeout=timeout
  File "/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/sso.py", line 55, in 
wrapper
_check_for_error(response)
  File "/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/sso.py", line 181, in 
_check_for_error
result['error'], details))
Unauthorized: Error during SSO authentication invalid_request : Missing 
parameter: 'client_secret'


> 1 окт. 2019 г., в 22:53, Mail SET Inc. Group  написал(а):
> 
> Hello!
> Get problems with clean installation  4.3.6.6-1.el7 and OVN
> 
> When i try to test OVN get notification:
> «Import provider certificate»
>  Do you approve trusting self signed certificate subject CN=Certificate 
> Authority, O=SET.LOCAL, SHA-1 fingerprint 
> a9d9b91160bb306667a521e6f2c66037ddc437cb?
> 
>  When i’m press «Yes», see old problem:
> Failed to communicate with the external provider, see log for additional 
> details.
> 
> [root@engine ~]# tail -f /var/log/ovirt-provider-ovn.log 
> timeout=self._timeout())
>   File "/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/sso.py", line 75, in 
> create_token
> username, password, engine_url, ca_file, timeout)
>   File "/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/sso.py", line 91, in 
> _get_sso_token
> timeout=timeout
>   File "/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/sso.py", line 54, in 
> wrapper
> response = func(*args, **kwargs)
>   File "/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/sso.py", line 47, in 
> wrapper
> raise BadGateway(e)
> BadGateway: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed 
> (_ssl.c:618)
> 
> [root@engine ~]# cat 
> /etc/ovirt-provider-ovn/conf.d/10-setup-ovirt-provider-ovn.conf
> # This file is automatically generated by engine-setup. Please do not edit 
> manually
> [OVN REMOTE]
> ovn-remote=ssl:127.0.0.1:6641
> [SSL]
> https-enabled=true
> ssl-cacert-file=/etc/pki/ovirt-engine/apache-ca.pem
> ssl-cert-file=/etc/pki/ovirt-engine/certs/apache.cer
> ssl-key-file=/etc/pki/ovirt-engine/keys/apache.key.nopass
> [OVIRT]
> ovirt-sso-client-id=ovirt-provider-ovn
> ovirt-ca-file=/etc/pki/ovirt-engine/certs/engine.cer
> ovirt-host=https://engine.set.local:443/ovirt-engine/ 
> 
> ovirt-sso-client-secret=vy80-QmCNNv6wP7JFvN9GWhPmYvo0lBNl5J8hpiGRa4
> [NETWORK]
> port-security-enabled-default=True
> [PROVIDER]
> provider-host=engine.set.local
> 
> [root@engine ~]# python -c "import requests; \
> print requests.get('https://engine.set.local ', \
> verify='/etc/pki/ovirt-engine/apache-ca.pem')"
> 
> 
> What’s wrong ?

___
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/IDUB3LOJHLRQVC2EFLSCN3MKYDEPZIRZ/

[ovirt-users] Re: Failed to synchronize networks of Provider ovirt-provider-ovn

2019-10-01 Thread Mail SET Inc. Group

Hello!
Get problems with clean installation  4.3.6.6-1.el7 and OVN

When i try to test OVN get notification:
«Import provider certificate»
 Do you approve trusting self signed certificate subject CN=Certificate 
Authority, O=SET.LOCAL, SHA-1 fingerprint 
a9d9b91160bb306667a521e6f2c66037ddc437cb?

 When i’m press «Yes», see old problem:
Failed to communicate with the external provider, see log for additional 
details.

[root@engine ~]# tail -f /var/log/ovirt-provider-ovn.log 
timeout=self._timeout())
  File "/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/sso.py", line 75, in 
create_token
username, password, engine_url, ca_file, timeout)
  File "/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/sso.py", line 91, in 
_get_sso_token
timeout=timeout
  File "/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/sso.py", line 54, in 
wrapper
response = func(*args, **kwargs)
  File "/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/sso.py", line 47, in 
wrapper
raise BadGateway(e)
BadGateway: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed 
(_ssl.c:618)

[root@engine ~]# cat 
/etc/ovirt-provider-ovn/conf.d/10-setup-ovirt-provider-ovn.conf
# This file is automatically generated by engine-setup. Please do not edit 
manually
[OVN REMOTE]
ovn-remote=ssl:127.0.0.1:6641
[SSL]
https-enabled=true
ssl-cacert-file=/etc/pki/ovirt-engine/apache-ca.pem
ssl-cert-file=/etc/pki/ovirt-engine/certs/apache.cer
ssl-key-file=/etc/pki/ovirt-engine/keys/apache.key.nopass
[OVIRT]
ovirt-sso-client-id=ovirt-provider-ovn
ovirt-ca-file=/etc/pki/ovirt-engine/certs/engine.cer
ovirt-host=https://engine.set.local:443/ovirt-engine/
ovirt-sso-client-secret=vy80-QmCNNv6wP7JFvN9GWhPmYvo0lBNl5J8hpiGRa4
[NETWORK]
port-security-enabled-default=True
[PROVIDER]
provider-host=engine.set.local

[root@engine ~]# python -c "import requests; \
print requests.get('https://engine.set.local', \
verify='/etc/pki/ovirt-engine/apache-ca.pem')"


What’s wrong ?___
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/FG63FR3KLBL726V3IOJD552O3A7AOHW4/

[ovirt-users] Re: Super Low VM disk IO via Shared Storage

2019-10-01 Thread Amit Bawer

On Tue, Oct 1, 2019 at 12:49 PM Vrgotic, Marko 
wrote:

> Thank you very much Amit,
>
>
>
> I hope the result of suggested tests allows us improve the speed for
> specific IO test case as well.
>
>
>
> Apologies for not being more clear, but I was referring  to changing mount
> options for storage where SHE also runs. It cannot be put in Maintenance
> mode since the engine is running on it.
> What to do in this case? Its clear that I need to power it down, but where
> can I then change the settings?
>

You can see similar question about changing mnt_options of hosted engine
and answer here [1]
[1] https://lists.ovirt.org/pipermail/users/2018-January/086265.html

>
>
> Kindly awaiting your reply.
>
>
>
> — — —
> Met vriendelijke groet / Kind regards,
>
> *Marko Vrgotic*
>
>
>
>
>
>
>
> *From: *Amit Bawer 
> *Date: *Saturday, 28 September 2019 at 20:25
> *To: *"Vrgotic, Marko" 
> *Cc: *Tony Brian Albers , "hunter86...@yahoo.com" <
> hunter86...@yahoo.com>, "users@ovirt.org" 
> *Subject: *Re: [ovirt-users] Re: Super Low VM disk IO via Shared Storage
>
>
>
>
>
>
>
> On Fri, Sep 27, 2019 at 4:02 PM Vrgotic, Marko 
> wrote:
>
> Hi oVirt gurus,
>
>
>
> Thank s to Tony, who pointed me into discovery process, the performance of
> the IO seems greatly dependent on the flags.
>
>
>
> [root@lgu215 ~]# dd if=/dev/zero of=/tmp/test1.img bs=512 count=10
>
> 10+0 records in
>
> 10+0 records out
>
> 5120 bytes (51 MB) copied, 0.108962 s, *470 MB/s*
>
> [root@lgu215 ~]# dd if=/dev/zero of=/tmp/test1.img bs=512 count=10
> *oflag=dsync*
>
> 10+0 records in
>
> 10+0 records out
>
> 5120 bytes (51 MB) copied, 322.314 s, *159 kB/s*
>
>
>
> Dsync flag tells dd to ignore all buffers, cache except certain kernel
> buffers and write data physically to the disc, before writing further.
> According to number of sites I looked at, this is the way to test Server
> Latency in regards to IO operations. Difference in performance is huge, as
> you can see (below I have added results from tests with 4k and 8k block)
>
>
>
> Still, certain software component we run tests with writes data in
> this/similar way, which is why I got this complaint in the first place.
>
>
>
> Here is my current NFS mount settings:
>
>
> rw,relatime,vers=4.0,rsize=65536,wsize=65536,namlen=255,soft,nosharecache,proto=tcp,timeo=600,retrans=6,sec=sys,clientaddr=172.17.28.11,local_lock=none,addr=172.17.28.5
>
>
>
> *If you have any suggestions on possible NFS tuning options, to try to
> increase performance, I would highly appreciate it.*
>
> *Can someone tell me how to change NFS mount options in oVirt for already
> existing/used storage?*
>
>
>
> Taking into account your network configured MTU [1] and Linux version [2],
> you can tune wsize, rsize mount options.
>
> Editing mount options can be done from Storage->Domains->Manage Domain
> menu.
>
>
>
> [1]  https://access.redhat.com/solutions/2440411
>
> [2] https://access.redhat.com/solutions/753853
>
>
>
>
>
> Test results with 4096 and 8192 byte size.
>
> [root@lgu215 ~]# dd if=/dev/zero of=/tmp/test1.img bs=4096 count=10
>
> 10+0 records in
>
> 10+0 records out
>
> 40960 bytes (410 MB) copied, 1.49831 s, *273 MB/s*
>
> [root@lgu215-admin ~]# dd if=/dev/zero of=/tmp/test1.img bs=4096
> count=10 *oflag=dsync*
>
> 10+0 records in
>
> 10+0 records out
>
> 40960 bytes (410 MB) copied, 349.041 s, *1.2 MB/s*
>
>
>
> [root@lgu215 ~]# dd if=/dev/zero of=/tmp/test1.img bs=8192 count=10
>
> 10+0 records in
>
> 10+0 records out
>
> 81920 bytes (819 MB) copied, 11.6553 s, *70.3 MB/s*
>
> [root@lgu215-admin ~]# dd if=/dev/zero of=/tmp/test1.img bs=8192
> count=10 *oflag=dsync*
>
> 10+0 records in
>
> 10+0 records out
>
> 81920 bytes (819 MB) copied, 393.035 s, *2.1 MB/s*
>
>
>
>
>
> *From: *"Vrgotic, Marko" 
> *Date: *Thursday, 26 September 2019 at 09:51
> *To: *Amit Bawer 
> *Cc: *Tony Brian Albers , "hunter86...@yahoo.com" <
> hunter86...@yahoo.com>, "users@ovirt.org" 
> *Subject: *Re: [ovirt-users] Re: Super Low VM disk IO via Shared Storage
>
>
>
> Dear all,
>
>
>
> I very much appreciate all help and suggestions so far.
>
>
>
> Today I will send the test results and current mount settings for NFS4.
> Our production setup is using Netapp based NFS server.
>
>
>
> I am surprised with results from Tony’s test.
>
> We also have one setup with Gluster based NFS, and I will run tests on
> those as well.
>
> Sent from my iPhone
>
>
>
> On 25 Sep 2019, at 14:18, Amit Bawer  wrote:
>
>
>
>
>
> On Wed, Sep 25, 2019 at 2:44 PM Tony Brian Albers  wrote:
>
> Guys,
>
> Just for info, this is what I'm getting on a VM that is on shared
> storage via NFSv3:
>
> --snip--
> [root@proj-000 ~]# time dd if=/dev/zero of=testfile bs=4096
> count=100
> 100+0 records in
> 100+0 records out
> 409600 bytes (4.1 GB) copied, 18.0984 s, 226 MB/s
>
> real0m18.171s
> user0m1.077s
> sys

[ovirt-users] Ovirt Blog Don't work

2019-10-01 Thread siovelrm

Hi, the link https://blogs.ovirt.org/ does not work. Could you please activate 
it?
___
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/ZSYHKVXR2RV4ZL74GB7344LBLWFAGAC6/

[ovirt-users] Re: Fwd: Unable to Upgrade

2019-10-01 Thread Satheesaran Sundaramoorthi

On Tue, Oct 1, 2019 at 8:09 PM Jayme  wrote:

> Hello,
>
> I am running oVirt 4.3.6 and glusterd service and peers on all HCI nodes
> are connected and working properly after updating.  I'm not sure if I
> understand what your question or issue is.  It definitely should be safe to
> update your oVirt HCI to 4.3.6.  GlusterFS is able to update from 5.6 to
> 6.5 one host at a time, the other hosts are still able to connect after one
> has been updated to Gluster 6x
>
> Thanks Jayme for the update. Probably Akshita should have some other
problem with the infra.

-- sas
___
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/CO7KLRGGLMDD4RW5KMTIHDRH2FXCZYTT/

[ovirt-users] Re: [ANN] oVirt 4.3.6 is now generally available

2019-10-01 Thread Guillaume Pavese

Good idea Strahil.

I guess there could be benefits, as when I mailed vdo-devel in March asking
about emulate512 performance impact, the answer from RedHat's Michael
Sclafani was as follows :
Begin citation:

512 emulation was intended to support drivers that only do a fraction of
their I/O in blocks smaller 4KB. It is not optimized for performance in any
way. Under the covers, VDO is still operating on 4KB physical blocks, so
each 512-byte read is potentially amplified to a 4KB read, and each
512-byte write to a 4KB read followed by a 4KB write. A workload consisting
exclusively of 512-byte randomly-distributed writes could effectively be
amplified by a factor of 16.

We have a suite of automated tests we run in 512e mode on a nightly basis.
That suite is a subset of our regular tests, containing only ones we expect
would be likely to expose problems specific to the emulation.

There should be no penalty to having emulation enabled on a volume that no
longer uses it. If the I/O is 4KB-aligned and 4KB or larger, having it
enabled won't affect it.
It does not appear the setting can be modified by the VDO manager, but I
cannot remember at this moment why that should be so.

Best

Guillaume Pavese
Ingénieur Système et Réseau
Interactiv-Group

On Tue, Oct 1, 2019 at 6:07 PM Strahil  wrote:

> You can go with 512 emulation and later you can recreate the brick without
> that emulation (if there are benefits of doing so).
> After all, you gluster is either replica 2 arbiter 1 or a replica 3 volume.
>
> Best Regards,
> Strahil Nikolov
> On Oct 1, 2019 09:26, Satheesaran Sundaramoorthi 
> wrote:
>
> On Tue, Oct 1, 2019 at 11:27 AM Guillaume Pavese <
> guillaume.pav...@interactiv-group.com> wrote:
>
> Hi all,
>
> Sorry for asking again :/
>
> Is there any consensus on not using --emulate512 anymore while creating
> VDO volumes on Gluster?
> Since this parameter can not be changed once the volume is created and we
> are nearing production setup. I would really like to have an official
> advice on this.
>
> Best,
>
> Guillaume Pavese
> Ingénieur Système et Réseau
> Interactiv-Group
>
> Hello Guillaume Pavese,
> If you are not using --emulate512 for VDO volume, then VDO volume will be
> created
> as 4K Native volume (with 4K block size).
>
> There are couple of things that bothers here:
> 1. 4K Native device support requires fixes at QEMU that will be part of
> CentOS 7.7.2 ( not yet available )
> 2. 4K Native support with VDO volumes on Gluster is not yet validated
> thoroughly.
>
> Based on the above items, it would be better you have emulate512=on or
> delay
> your production setup ( if possible, till above both items are addressed )
> to make use of 4K VDO volume.
>
> @Sahina Bose  Do you have any other suggestions ?
>
> -- Satheesaran S (sas)
>
>
> On Fri, Sep 27, 2019 at 3:19 PM Sandro Bonazzola 
> wrote:
>
>
>
>

-- 

Ce message et toutes les pièces jointes (ci-après le “message”) sont 
établis à l’intention exclusive de ses destinataires et sont confidentiels. 
Si vous recevez ce message par erreur, merci de le détruire et d’en avertir 
immédiatement l’expéditeur. Toute utilisation de ce message non conforme a 
sa destination, toute diffusion ou toute publication, totale ou partielle, 
est interdite, sauf autorisation expresse. L’internet ne permettant pas 
d’assurer l’intégrité de ce message . Interactiv-group (et ses filiales) 
décline(nt) toute responsabilité au titre de ce message, dans l’hypothèse 
ou il aurait été modifié. IT, ES, UK.  

___
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/B4LJ6A5DV6OJAFKV3RQ4LE2UH7WDOLM6/

[ovirt-users] Re: [ANN] oVirt 4.3.6 is now generally available

2019-10-01 Thread Derek Atkins

jvdw...@xs4all.nl writes:

>> Yes, it's still available. It will be dropped in 4.4.
>
> OK, good to know, time to polish up my ansible or start writing api scripts.
>
> Now that 4.4 popped up, how is that going?
> I looked a bit at the Gerrit yesterday and right now and see that el8
> builds are being done now, great work!

Yeah.  I've got a startup script that I use to start all my VMs (see
below).  I'll need to figure out how to migrate that script to SDK4.
It really sucks that there's no SDK4 version of ovirt-shell.  I suspect
my script will expand by an order of magnitude, and everyone who has
written a script around ovirt-shell will have to duplicate effort.

I know there is a feature for the engine to autostart VMs (which I
believe will be in 4.4), but AFAIK it doesn't do ordering.  I need at
least one specific VM to start up before everything else.

Thanks,

-derek

#!/bin/bash

[ -f /etc/sysconfig/vm_list ] || exit 0
. /etc/sysconfig/vm_list

echo -n "Starting at "
date

# Wait for the engine to respond
while [ `ovirt-shell -I -c -F -T 50 -E ping 2>/dev/null | grep -c success` != 1 
]
do
echo "Not ready... Sleeping..."
sleep 60
done

# Now wait for the storage domain to appear active
echo -n "Engine up.  Searching for disks at "
date
total_disks=`ovirt-shell -I -c -E summary | grep storage_domains-total | sed -e 
's/.*: //'`
# subtract one because we know we're not using the image-repository
total_disks=`expr $total_disks - 1`
active_disks=`ovirt-shell -I -c -E summary | grep storage_domains-active | sed 
-e 's/.*: //'`
while [ $active_disks -lt $total_disks ]
do
echo "Storage Domains not active yet.  Only found 
$active_disks/$total_disks.  Waiting..."
sleep 60
active_disks=`ovirt-shell -I -c -E summary | grep storage_domains-active | 
sed -e 's/.*: //'`
done

# Now start all of the VMs in the requested order.
echo -n "All storage mounted.  Starting VMs at "
date
for vm in "${vm_list[@]}"
do
  timeout=${vm_timeout[$vm]:-$default_timeout}
  ovirt-shell -I -c -E "action vm $vm start"
  sleep "$timeout"
done

-- 
   Derek Atkins 617-623-3745
   de...@ihtfp.com www.ihtfp.com
   Computer and Internet Security Consultant
___
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/NS4VMN66G6K3WH2ROGSEBTQDEAMZB5DQ/

[ovirt-users] Re: Fwd: Unable to Upgrade

2019-10-01 Thread Jayme

Hello,

I am running oVirt 4.3.6 and glusterd service and peers on all HCI nodes
are connected and working properly after updating.  I'm not sure if I
understand what your question or issue is.  It definitely should be safe to
update your oVirt HCI to 4.3.6.  GlusterFS is able to update from 5.6 to
6.5 one host at a time, the other hosts are still able to connect after one
has been updated to Gluster 6x

On Tue, Oct 1, 2019 at 9:52 AM Satheesaran Sundaramoorthi <
sasun...@redhat.com> wrote:

> On Tue, Oct 1, 2019 at 6:00 PM Jayme  wrote:
>
>> In an oVirt HCI gluster configuration you should be able to take down at
>> least one host at a time.  The procedure I use to upgrade my oVirt HCI
>> cluster goes something like this:
>>
>> 1. Upgrade the oVirt engine setup packages.  Upgrade the engine.  Yum
>> update and reboot.
>> 2. Place the first host in maintenance mode and upgrade the host.
>> Reboot.  Wait until the host is active and gluster bricks are fully healed.
>> 3. Place the next host in maintenance and perform the same steps until
>> all hosts are upgraded.
>>
>> *From: *"Akshita Jain" 
 *Subject: **Unable to Upgrade*
 *Date: *1 October 2019 at 11:12:58 CEST
 *To: *in...@ovirt.org

 After upgrading oVirt 4.3.4 to 4.3.6, the gluster is also upgrading
 from 5.6 to 6.5. But as soon as it upgrades gluster peer status shows
 disconnected.
 What is the correct method to upgrade oVirt with gluster HCI
 environment?


> Hello Akshita,
>
> Jayme's steps are perfect enough for the update.
> If you see post updating to oVirt 4.3.6, your peers are in disconnected
> state,
> could you confirm that glusterd service is up and running on all HCI nodes
> ( # systemctl status glusterd ).
>
> Meanwhile, I can also try for the quick update from gluster-5.6 to 6.5 and
> update the results here.
>
> -- Satheesaran S ( sas )
>
___
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/MU55ZEEFN73USUADOCTDLBO63QXJILYG/

[ovirt-users] Re: Fwd: Unable to Upgrade

2019-10-01 Thread Satheesaran Sundaramoorthi

On Tue, Oct 1, 2019 at 6:00 PM Jayme  wrote:

> In an oVirt HCI gluster configuration you should be able to take down at
> least one host at a time.  The procedure I use to upgrade my oVirt HCI
> cluster goes something like this:
>
> 1. Upgrade the oVirt engine setup packages.  Upgrade the engine.  Yum
> update and reboot.
> 2. Place the first host in maintenance mode and upgrade the host.
> Reboot.  Wait until the host is active and gluster bricks are fully healed.
> 3. Place the next host in maintenance and perform the same steps until all
> hosts are upgraded.
>
> *From: *"Akshita Jain" 
>>> *Subject: **Unable to Upgrade*
>>> *Date: *1 October 2019 at 11:12:58 CEST
>>> *To: *in...@ovirt.org
>>>
>>> After upgrading oVirt 4.3.4 to 4.3.6, the gluster is also upgrading from
>>> 5.6 to 6.5. But as soon as it upgrades gluster peer status shows
>>> disconnected.
>>> What is the correct method to upgrade oVirt with gluster HCI environment?
>>>
>>>
Hello Akshita,

Jayme's steps are perfect enough for the update.
If you see post updating to oVirt 4.3.6, your peers are in disconnected
state,
could you confirm that glusterd service is up and running on all HCI nodes
( # systemctl status glusterd ).

Meanwhile, I can also try for the quick update from gluster-5.6 to 6.5 and
update the results here.

-- Satheesaran S ( sas )
___
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/6ZWJHJO6ADLTDFUEXEWRTUPCCM52R62T/

[ovirt-users] Re: Fwd: Unable to Upgrade

2019-10-01 Thread Gobinda Das

Hi Anton,
 There is nothing special for upgrading HCI env with Gluster. Bellow steps will 
be enough:

1- Stop glusterd service in one node which needs to be upgraded.
2- upgrade that node and start glusterd service.
3- wait heal to be completed.
4- continue same procedure for other nodes.


In your case can you please restar glusterd in all nodes and check. If it's 
still not working please share glusterd log?
Also please share "gluster volume status" out put.

Get Outlook for Android


From: Sandro Bonazzola 
Sent: Tuesday, October 1, 2019, 5:01 PM
To: Anton Marchukov; Gobinda Das; Sundaramoorthi, Satheesaran; Sahina Bose
Cc: users; Akshita Jain
Subject: Re: [ovirt-users] Fwd: Unable to Upgrade



Il giorno mar 1 ott 2019 alle ore 11:27 Anton Marchukov 
mailto:amarc...@redhat.com>> ha scritto:
Forwarding to the users list.

Begin forwarded message:

From: "Akshita Jain" 
mailto:aksh...@councilinfosec.org>>
Subject: Unable to Upgrade
Date: 1 October 2019 at 11:12:58 CEST
To: in...@ovirt.org

After upgrading oVirt 4.3.4 to 4.3.6, the gluster is also upgrading from 5.6 to 
6.5. But as soon as it upgrades gluster peer status shows disconnected.
What is the correct method to upgrade oVirt with gluster HCI environment?

+Gobinda Das , +Sundaramoorthi, 
Satheesaran , +Sahina 
Bose can you please follow up on this question?


___
Infra mailing list -- in...@ovirt.org
To unsubscribe send an email to 
infra-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/in...@ovirt.org/message/24D6NKVLMYQA3LI2GBXJFMOHA3U42KHS/

--
Anton Marchukov
Associate Manager - RHV DevOps - Red Hat






___
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/YO2RYKFDCSPQ7EWOVXVE6LIO7GMY36SA/


--

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat EMEA

sbona...@redhat.com

[https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png]
Red Hat respects your work life balance. Therefore there is no need to answer 
this email out of your office hours.

___
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/PUMPJHGZ66QS2HB3BFEXM75PVZHJW6A5/

[ovirt-users] Re: Fwd: Unable to Upgrade

2019-10-01 Thread Jayme

In an oVirt HCI gluster configuration you should be able to take down at
least one host at a time.  The procedure I use to upgrade my oVirt HCI
cluster goes something like this:

1. Upgrade the oVirt engine setup packages.  Upgrade the engine.  Yum
update and reboot.
2. Place the first host in maintenance mode and upgrade the host.  Reboot.
Wait until the host is active and gluster bricks are fully healed.
3. Place the next host in maintenance and perform the same steps until all
hosts are upgraded.

On Tue, Oct 1, 2019 at 8:33 AM Sandro Bonazzola  wrote:

>
>
> Il giorno mar 1 ott 2019 alle ore 11:27 Anton Marchukov <
> amarc...@redhat.com> ha scritto:
>
>> Forwarding to the users list.
>>
>> Begin forwarded message:
>>
>> *From: *"Akshita Jain" 
>> *Subject: **Unable to Upgrade*
>> *Date: *1 October 2019 at 11:12:58 CEST
>> *To: *in...@ovirt.org
>>
>> After upgrading oVirt 4.3.4 to 4.3.6, the gluster is also upgrading from
>> 5.6 to 6.5. But as soon as it upgrades gluster peer status shows
>> disconnected.
>> What is the correct method to upgrade oVirt with gluster HCI environment?
>>
>>
> +Gobinda Das  , +Sundaramoorthi, Satheesaran
>  , +Sahina Bose  can you please
> follow up on this question?
>
>
>
>> ___
>> Infra mailing list -- in...@ovirt.org
>> To unsubscribe send an email to infra-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/in...@ovirt.org/message/24D6NKVLMYQA3LI2GBXJFMOHA3U42KHS/
>>
>>
>> --
>> Anton Marchukov
>> Associate Manager - RHV DevOps - Red Hat
>>
>>
>>
>>
>>
>>
>> ___
>> 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/YO2RYKFDCSPQ7EWOVXVE6LIO7GMY36SA/
>>
>
>
> --
>
> Sandro Bonazzola
>
> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
>
> Red Hat EMEA 
>
> sbona...@redhat.com
> *Red Hat respects your work life balance.
> Therefore there is no need to answer this email out of your office hours.
> *
> ___
> 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/VLYFAJS73RRFUUS5VM4RIJ3KZ2ZS7MTJ/
>
___
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/IX3CJF6W56UDSYNCY2Z2YA3DGZEODSEH/

[ovirt-users] Re: change connection string in db

2019-10-01 Thread olaf . buitelaar

Never mind again,
for those looking for the same thing, it's via the;
hosted-engine --set-shared-config storage 10.201.0.1:/ovirt-engine 
--type=he_shared
hosted-engine --set-shared-config storage 10.201.0.1:/ovirt-engine 
--type=he_local
___
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/VSMQWNZ4UGCWY2FVBMSSNXTNLR5KP5P2/

[ovirt-users] Re: Fwd: Unable to Upgrade

2019-10-01 Thread Sandro Bonazzola

Il giorno mar 1 ott 2019 alle ore 11:27 Anton Marchukov 
ha scritto:

> Forwarding to the users list.
>
> Begin forwarded message:
>
> *From: *"Akshita Jain" 
> *Subject: **Unable to Upgrade*
> *Date: *1 October 2019 at 11:12:58 CEST
> *To: *in...@ovirt.org
>
> After upgrading oVirt 4.3.4 to 4.3.6, the gluster is also upgrading from
> 5.6 to 6.5. But as soon as it upgrades gluster peer status shows
> disconnected.
> What is the correct method to upgrade oVirt with gluster HCI environment?
>
>
+Gobinda Das  , +Sundaramoorthi, Satheesaran
 , +Sahina Bose  can you please
follow up on this question?



> ___
> Infra mailing list -- in...@ovirt.org
> To unsubscribe send an email to infra-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/in...@ovirt.org/message/24D6NKVLMYQA3LI2GBXJFMOHA3U42KHS/
>
>
> --
> Anton Marchukov
> Associate Manager - RHV DevOps - Red Hat
>
>
>
>
>
>
> ___
> 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/YO2RYKFDCSPQ7EWOVXVE6LIO7GMY36SA/
>


-- 

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat EMEA 

sbona...@redhat.com
*Red Hat respects your work life balance.
Therefore there is no need to answer this email out of your office hours.
*
___
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/VLYFAJS73RRFUUS5VM4RIJ3KZ2ZS7MTJ/

[ovirt-users] Fwd: Unable to Upgrade

2019-10-01 Thread Anton Marchukov

Forwarding to the users list.

> Begin forwarded message:
> 
> From: "Akshita Jain" 
> Subject: Unable to Upgrade
> Date: 1 October 2019 at 11:12:58 CEST
> To: in...@ovirt.org
> 
> After upgrading oVirt 4.3.4 to 4.3.6, the gluster is also upgrading from 5.6 
> to 6.5. But as soon as it upgrades gluster peer status shows disconnected.
> What is the correct method to upgrade oVirt with gluster HCI environment?
> ___
> Infra mailing list -- in...@ovirt.org
> To unsubscribe send an email to infra-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/in...@ovirt.org/message/24D6NKVLMYQA3LI2GBXJFMOHA3U42KHS/

-- 
Anton Marchukov
Associate Manager - RHV DevOps - Red Hat






___
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/YO2RYKFDCSPQ7EWOVXVE6LIO7GMY36SA/

[ovirt-users] Re: [ANN] oVirt 4.3.6 is now generally available

2019-10-01 Thread Strahil

You can go with 512 emulation and later you can recreate the brick without that 
emulation (if there are benefits of doing so).
After all, you gluster is either replica 2 arbiter 1 or a replica 3 volume.

Best Regards,
Strahil Nikolov
On Oct 1, 2019 09:26, Satheesaran Sundaramoorthi  wrote:
>
> On Tue, Oct 1, 2019 at 11:27 AM Guillaume Pavese 
>  wrote:
>>
>> Hi all,
>>
>> Sorry for asking again :/
>>
>> Is there any consensus on not using --emulate512 anymore while creating VDO 
>> volumes on Gluster?
>> Since this parameter can not be changed once the volume is created and we 
>> are nearing production setup. I would really like to have an official advice 
>> on this.
>>
>> Best,
>>
>> Guillaume Pavese
>> Ingénieur Système et Réseau
>> Interactiv-Group
>>
> Hello Guillaume Pavese,
> If you are not using --emulate512 for VDO volume, then VDO volume will be 
> created
> as 4K Native volume (with 4K block size). 
>
> There are couple of things that bothers here:
> 1. 4K Native device support requires fixes at QEMU that will be part of 
> CentOS 7.7.2 ( not yet available )
> 2. 4K Native support with VDO volumes on Gluster is not yet validated
> thoroughly.
>
> Based on the above items, it would be better you have emulate512=on or delay
> your production setup ( if possible, till above both items are addressed ) 
> to make use of 4K VDO volume.
>
> @Sahina Bose Do you have any other suggestions ?
>
> -- Satheesaran S (sas)
>>
>>
>> On Fri, Sep 27, 2019 at 3:19 PM Sandro Bonazzola  wrote:
>>>
>>>
>>>
___
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/WDETM3AKVJASI3MQKBB6EIZCK52C7IW2/

[ovirt-users] Re: [ANN] oVirt 4.3.6 is now generally available

2019-10-01 Thread Sandro Bonazzola

Il giorno mar 1 ott 2019 alle ore 09:48  ha scritto:

> September 30, 2019 2:23 PM, "Sandro Bonazzola" 
> wrote:
>
> > Il giorno ven 27 set 2019 alle ore 17:54 Derek Atkins 
> ha scritto:
> >
> >> On Fri, September 27, 2019 11:46 am, Sandro Bonazzola wrote:
> >> [nsip]
> >
> > I'm curious what the steps should be going from 4.1.9 / EL7.4 to 4.3.x /
> > EL7.7? I am pretty sure I need some steps along the way (I doubt I can
> > jump directly from 4.1.9 -> 4.3.x and 7.4 -> 7.7, right).
> >
> > So should I jump from 7.4/4.1.9 to 7.6/4.2.8 and then from there to
> > 7.7/4.3.6?
> >
> > 4.1 cluster level is still supported by 4.3 engine.
> > So you can upgrade the engine from 7.4/4.1.9 to 7.6/4.2.8 and then to
> > 7.7/4.3.6 while on the host side you can go straight to 4.3.6/7.7.
> > Once done, please update cluster level to 4.3.
> >> Excellent, I can do that. I just need to ensure that the cluster
> settings
> >> fully upgraded from 4.0 to 4.1.
> >>
> >> One final question: I know that ovirt-shell is deprecated, but is it
> >> still available in 4.3.x?
> >
> > Yes, it's still available. It will be dropped in 4.4.
>
> OK, good to know, time to polish up my ansible or start writing api
> scripts.
>
> Now that 4.4 popped up, how is that going?
> I looked a bit at the Gerrit yesterday and right now and see that el8
> builds are being done now, great work!
>

Pushing builds to el8 and fc30. A few big show stoppers like the lack of
ansible in EPEL 8 (Bug 1744975
)
and CentOS Community Build System not yet enabled to build for CentOS 8,
but we are working on it.


>
> Greetings,
>
> Joop
> ___
> 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/DAEUKE62ZOHVFRPCPSZ3UXMLDIXQGQED/
>


-- 

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat EMEA 

sbona...@redhat.com
*Red Hat respects your work life balance.
Therefore there is no need to answer this email out of your office hours.*
___
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/UNBUUVH47BPIOE5JZSKJ4WADY26REKTR/

[ovirt-users] Re: Creating vm from snapshot via API

2019-10-01 Thread Aleksei Ivanovich

So, if someone has any ideas or can suggest the directions for further research 
I will be grateful.
___
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/EP3LXHAK7ODCGIM4CN6T7UQLLSJACW6J/

[ovirt-users] Re: [ANN] oVirt 4.3.6 is now generally available

2019-10-01 Thread jvdwege

September 30, 2019 2:23 PM, "Sandro Bonazzola"  wrote:

> Il giorno ven 27 set 2019 alle ore 17:54 Derek Atkins  ha 
> scritto:
> 
>> On Fri, September 27, 2019 11:46 am, Sandro Bonazzola wrote:
>> [nsip]
> 
> I'm curious what the steps should be going from 4.1.9 / EL7.4 to 4.3.x /
> EL7.7? I am pretty sure I need some steps along the way (I doubt I can
> jump directly from 4.1.9 -> 4.3.x and 7.4 -> 7.7, right).
> 
> So should I jump from 7.4/4.1.9 to 7.6/4.2.8 and then from there to
> 7.7/4.3.6?
> 
> 4.1 cluster level is still supported by 4.3 engine.
> So you can upgrade the engine from 7.4/4.1.9 to 7.6/4.2.8 and then to
> 7.7/4.3.6 while on the host side you can go straight to 4.3.6/7.7.
> Once done, please update cluster level to 4.3.
>> Excellent, I can do that. I just need to ensure that the cluster settings
>> fully upgraded from 4.0 to 4.1.
>> 
>> One final question: I know that ovirt-shell is deprecated, but is it
>> still available in 4.3.x?
> 
> Yes, it's still available. It will be dropped in 4.4.

OK, good to know, time to polish up my ansible or start writing api scripts.

Now that 4.4 popped up, how is that going?
I looked a bit at the Gerrit yesterday and right now and see that el8 builds 
are being done now, great work!

Greetings,

Joop
___
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/DAEUKE62ZOHVFRPCPSZ3UXMLDIXQGQED/

[ovirt-users] Re: [ANN] oVirt 4.3.6 is now generally available

2019-10-01 Thread Gobinda Das

Hi Guillaume,
 As Satheesaran suggested the possible options which is completly valid
points. Thanks sas for that.
I would suggest to wait till 4Kn validation complet with Gluster + VDO (All
usecases), if you want 4K support. Other wise you can go ahead
with emulate512=on .

On Tue, Oct 1, 2019 at 11:56 AM Satheesaran Sundaramoorthi <
sasun...@redhat.com> wrote:

> On Tue, Oct 1, 2019 at 11:27 AM Guillaume Pavese <
> guillaume.pav...@interactiv-group.com> wrote:
>
>> Hi all,
>>
>> Sorry for asking again :/
>>
>> Is there any consensus on not using --emulate512 anymore while creating
>> VDO volumes on Gluster?
>> Since this parameter can not be changed once the volume is created and we
>> are nearing production setup. I would really like to have an official
>> advice on this.
>>
>> Best,
>>
>> Guillaume Pavese
>> Ingénieur Système et Réseau
>> Interactiv-Group
>>
>> Hello Guillaume Pavese,
> If you are not using --emulate512 for VDO volume, then VDO volume will be
> created
> as 4K Native volume (with 4K block size).
>
> There are couple of things that bothers here:
> 1. 4K Native device support requires fixes at QEMU that will be part of
> CentOS 7.7.2 ( not yet available )
> 2. 4K Native support with VDO volumes on Gluster is not yet validated
> thoroughly.
>
> Based on the above items, it would be better you have emulate512=on or
> delay
> your production setup ( if possible, till above both items are addressed )
> to make use of 4K VDO volume.
>
> @Sahina Bose  Do you have any other suggestions ?
>
> -- Satheesaran S (sas)
>
>>
>> On Fri, Sep 27, 2019 at 3:19 PM Sandro Bonazzola 
>> wrote:
>>
>>>
>>>
>>> Il giorno ven 27 set 2019 alle ore 05:21 Guillaume Pavese <
>>> guillaume.pav...@interactiv-group.com> ha scritto:
>>>
 I see that oVirt 4.3.6 finally has 4k domain support.

 - Would that mean that VDO enabled Gluster domains will be created
 without the --emulate512 workaround?
 - If the wizard to create the Gluster volumes has not yet removed that
 parameter, is it safe to edit & remove it manually before creation?
 - Should we expect performance increase by using the native 4k block
 size of VDO?


>>>
>>> +Nir Soffer  +Sundaramoorthi, Satheesaran
>>>  +Gobinda Das  can you answer
>>> here?
>>>
>>>
>>>
 Thanks

 Guillaume Pavese
 Ingénieur Système et Réseau
 Interactiv-Group


 On Fri, Sep 27, 2019 at 12:00 AM Sandro Bonazzola 
 wrote:

> The oVirt Project is pleased to announce the general availability of
> oVirt 4.3.6 as of September 26th, 2019.
>
>
>
> This update is the sixth in a series of stabilization updates to the
> 4.3 series.
>
>
>
> This release is available now on x86_64 architecture for:
>
> * Red Hat Enterprise Linux 7.7 or later (but < 8)
>
> * CentOS Linux (or similar) 7.7 or later (but < 8)
>
>
>
> This release supports Hypervisor Hosts on x86_64 and ppc64le
> architectures for:
>
> * Red Hat Enterprise Linux 7.7 or later (but < 8)
>
> * CentOS Linux (or similar) 7.7 or later (but < 8)
>
> * oVirt Node 4.3 (available for x86_64 only)
>
>
>
> Due to Fedora 28 being now at end of life this release is missing
> experimental tech preview for x86_64 and s390x architectures for Fedora 
> 28.
>
> We are working on Fedora 29 and 30 support and we may re-introduce
> experimental support for Fedora in next release.
>
>
>
> See the release notes [1] for installation / upgrade instructions and
> a list of new features and bugs fixed.
>
>
>
> Notes:
>
> - oVirt Appliance is already available
>
> - oVirt Node is already available[2]
>
> oVirt Node and Appliance have been updated including:
>
> - oVirt 4.3.6: http://www.ovirt.org/release/4.3.6/
>
> - Wildfly 17.0.1:
> https://wildfly.org/news/2019/07/07/WildFly-1701-Released/
>
> - Latest CentOS 7.7 updates including:
>
>-
>
>Release for CentOS Linux 7 (1908) on the x86_64 Architecture
>
> 
>-
>
>CEBA-2019:2601 CentOS 7 NetworkManager BugFix Update
>
> 
>
>-
>
>CEBA-2019:2023 CentOS 7 efivar BugFix Update
>
> 
>-
>
>CEBA-2019:2614 CentOS 7 firewalld BugFix Update
>
> 
>-
>
>CEBA-2019:2227 CentOS 7 grubby BugFix Update
>
> 
>-
>
>CESA-2019:2258 Moderate CentOS 7

[ovirt-users] Re: [ANN] oVirt 4.3.6 is now generally available

2019-10-01 Thread Satheesaran Sundaramoorthi

On Tue, Oct 1, 2019 at 11:27 AM Guillaume Pavese <
guillaume.pav...@interactiv-group.com> wrote:

> Hi all,
>
> Sorry for asking again :/
>
> Is there any consensus on not using --emulate512 anymore while creating
> VDO volumes on Gluster?
> Since this parameter can not be changed once the volume is created and we
> are nearing production setup. I would really like to have an official
> advice on this.
>
> Best,
>
> Guillaume Pavese
> Ingénieur Système et Réseau
> Interactiv-Group
>
> Hello Guillaume Pavese,
If you are not using --emulate512 for VDO volume, then VDO volume will be
created
as 4K Native volume (with 4K block size).

There are couple of things that bothers here:
1. 4K Native device support requires fixes at QEMU that will be part of
CentOS 7.7.2 ( not yet available )
2. 4K Native support with VDO volumes on Gluster is not yet validated
thoroughly.

Based on the above items, it would be better you have emulate512=on or delay
your production setup ( if possible, till above both items are addressed )
to make use of 4K VDO volume.

@Sahina Bose  Do you have any other suggestions ?

-- Satheesaran S (sas)

>
> On Fri, Sep 27, 2019 at 3:19 PM Sandro Bonazzola 
> wrote:
>
>>
>>
>> Il giorno ven 27 set 2019 alle ore 05:21 Guillaume Pavese <
>> guillaume.pav...@interactiv-group.com> ha scritto:
>>
>>> I see that oVirt 4.3.6 finally has 4k domain support.
>>>
>>> - Would that mean that VDO enabled Gluster domains will be created
>>> without the --emulate512 workaround?
>>> - If the wizard to create the Gluster volumes has not yet removed that
>>> parameter, is it safe to edit & remove it manually before creation?
>>> - Should we expect performance increase by using the native 4k block
>>> size of VDO?
>>>
>>>
>>
>> +Nir Soffer  +Sundaramoorthi, Satheesaran
>>  +Gobinda Das  can you answer
>> here?
>>
>>
>>
>>> Thanks
>>>
>>> Guillaume Pavese
>>> Ingénieur Système et Réseau
>>> Interactiv-Group
>>>
>>>
>>> On Fri, Sep 27, 2019 at 12:00 AM Sandro Bonazzola 
>>> wrote:
>>>
 The oVirt Project is pleased to announce the general availability of
 oVirt 4.3.6 as of September 26th, 2019.



 This update is the sixth in a series of stabilization updates to the
 4.3 series.



 This release is available now on x86_64 architecture for:

 * Red Hat Enterprise Linux 7.7 or later (but < 8)

 * CentOS Linux (or similar) 7.7 or later (but < 8)



 This release supports Hypervisor Hosts on x86_64 and ppc64le
 architectures for:

 * Red Hat Enterprise Linux 7.7 or later (but < 8)

 * CentOS Linux (or similar) 7.7 or later (but < 8)

 * oVirt Node 4.3 (available for x86_64 only)



 Due to Fedora 28 being now at end of life this release is missing
 experimental tech preview for x86_64 and s390x architectures for Fedora 28.

 We are working on Fedora 29 and 30 support and we may re-introduce
 experimental support for Fedora in next release.



 See the release notes [1] for installation / upgrade instructions and a
 list of new features and bugs fixed.



 Notes:

 - oVirt Appliance is already available

 - oVirt Node is already available[2]

 oVirt Node and Appliance have been updated including:

 - oVirt 4.3.6: http://www.ovirt.org/release/4.3.6/

 - Wildfly 17.0.1:
 https://wildfly.org/news/2019/07/07/WildFly-1701-Released/

 - Latest CentOS 7.7 updates including:

-

Release for CentOS Linux 7 (1908) on the x86_64 Architecture

 
-

CEBA-2019:2601 CentOS 7 NetworkManager BugFix Update

 

-

CEBA-2019:2023 CentOS 7 efivar BugFix Update

 
-

CEBA-2019:2614 CentOS 7 firewalld BugFix Update

 
-

CEBA-2019:2227 CentOS 7 grubby BugFix Update

 
-

CESA-2019:2258 Moderate CentOS 7 http-parser Security Update

 
-

CESA-2019:2600 Important CentOS 7 kernel Security Update

 
-

CEBA-2019:2599 CentOS 7 krb5 BugFix Update

 
-

CEBA-2019:2358 CentOS 7 libguestfs BugFix Update

[ovirt-users] Re: [ANN] oVirt 4.3.6 is now generally available

2019-10-01 Thread Guillaume Pavese

Hi all,

Sorry for asking again :/

Is there any consensus on not using --emulate512 anymore while creating VDO
volumes on Gluster?
Since this parameter can not be changed once the volume is created and we
are nearing production setup. I would really like to have an official
advice on this.

Best,

Guillaume Pavese
Ingénieur Système et Réseau
Interactiv-Group


On Fri, Sep 27, 2019 at 3:19 PM Sandro Bonazzola 
wrote:

>
>
> Il giorno ven 27 set 2019 alle ore 05:21 Guillaume Pavese <
> guillaume.pav...@interactiv-group.com> ha scritto:
>
>> I see that oVirt 4.3.6 finally has 4k domain support.
>>
>> - Would that mean that VDO enabled Gluster domains will be created
>> without the --emulate512 workaround?
>> - If the wizard to create the Gluster volumes has not yet removed that
>> parameter, is it safe to edit & remove it manually before creation?
>> - Should we expect performance increase by using the native 4k block size
>> of VDO?
>>
>>
>
> +Nir Soffer  +Sundaramoorthi, Satheesaran
>  +Gobinda Das  can you answer here?
>
>
>
>> Thanks
>>
>> Guillaume Pavese
>> Ingénieur Système et Réseau
>> Interactiv-Group
>>
>>
>> On Fri, Sep 27, 2019 at 12:00 AM Sandro Bonazzola 
>> wrote:
>>
>>> The oVirt Project is pleased to announce the general availability of
>>> oVirt 4.3.6 as of September 26th, 2019.
>>>
>>>
>>>
>>> This update is the sixth in a series of stabilization updates to the 4.3
>>> series.
>>>
>>>
>>>
>>> This release is available now on x86_64 architecture for:
>>>
>>> * Red Hat Enterprise Linux 7.7 or later (but < 8)
>>>
>>> * CentOS Linux (or similar) 7.7 or later (but < 8)
>>>
>>>
>>>
>>> This release supports Hypervisor Hosts on x86_64 and ppc64le
>>> architectures for:
>>>
>>> * Red Hat Enterprise Linux 7.7 or later (but < 8)
>>>
>>> * CentOS Linux (or similar) 7.7 or later (but < 8)
>>>
>>> * oVirt Node 4.3 (available for x86_64 only)
>>>
>>>
>>>
>>> Due to Fedora 28 being now at end of life this release is missing
>>> experimental tech preview for x86_64 and s390x architectures for Fedora 28.
>>>
>>> We are working on Fedora 29 and 30 support and we may re-introduce
>>> experimental support for Fedora in next release.
>>>
>>>
>>>
>>> See the release notes [1] for installation / upgrade instructions and a
>>> list of new features and bugs fixed.
>>>
>>>
>>>
>>> Notes:
>>>
>>> - oVirt Appliance is already available
>>>
>>> - oVirt Node is already available[2]
>>>
>>> oVirt Node and Appliance have been updated including:
>>>
>>> - oVirt 4.3.6: http://www.ovirt.org/release/4.3.6/
>>>
>>> - Wildfly 17.0.1:
>>> https://wildfly.org/news/2019/07/07/WildFly-1701-Released/
>>>
>>> - Latest CentOS 7.7 updates including:
>>>
>>>-
>>>
>>>Release for CentOS Linux 7 (1908) on the x86_64 Architecture
>>>
>>> 
>>>-
>>>
>>>CEBA-2019:2601 CentOS 7 NetworkManager BugFix Update
>>>
>>> 
>>>
>>>-
>>>
>>>CEBA-2019:2023 CentOS 7 efivar BugFix Update
>>>
>>> 
>>>-
>>>
>>>CEBA-2019:2614 CentOS 7 firewalld BugFix Update
>>>
>>> 
>>>-
>>>
>>>CEBA-2019:2227 CentOS 7 grubby BugFix Update
>>>
>>> 
>>>-
>>>
>>>CESA-2019:2258 Moderate CentOS 7 http-parser Security Update
>>>
>>> 
>>>-
>>>
>>>CESA-2019:2600 Important CentOS 7 kernel Security Update
>>>
>>> 
>>>-
>>>
>>>CEBA-2019:2599 CentOS 7 krb5 BugFix Update
>>>
>>> 
>>>-
>>>
>>>CEBA-2019:2358 CentOS 7 libguestfs BugFix Update
>>>
>>> 
>>>-
>>>
>>>CEBA-2019:2679 CentOS 7 libvirt BugFix Update
>>>
>>> 
>>>-
>>>
>>>CEBA-2019:2501 CentOS 7 rsyslog BugFix Update
>>>
>>> 
>>>-
>>>
>>>CEBA-2019:2355 CentOS 7 selinux-policy BugFix Update
>>>
>>> 
>>>-
>>>
>>>CEBA-2019:2612 CentOS 7 sg3_utils BugFix Update
>>>
>>> 
>>>-
>>>
>>>CEBA-2019:2602 CentOS 7 sos BugFix Update
>>>
>>> 
>>>
>>>-
>>>
>>>CEBA-2019:2564 CentOS 7

[ovirt-users] Re: Incremental backup using ovirt api

[ovirt-users] Re: Ovirt 4.2.7 won't start and drops to emergency console

[ovirt-users] Re: Ovirt 4.2.7 won't start and drops to emergency console

[ovirt-users] Re: Ovirt 4.2.7 won't start and drops to emergency console

[ovirt-users] Re: Ovirt 4.2.7 won't start and drops to emergency console

[ovirt-users] Re: Failed to synchronize networks of Provider ovirt-provider-ovn

[ovirt-users] Re: Failed to synchronize networks of Provider ovirt-provider-ovn

[ovirt-users] Re: Super Low VM disk IO via Shared Storage

[ovirt-users] Ovirt Blog Don't work

[ovirt-users] Re: Fwd: Unable to Upgrade

[ovirt-users] Re: [ANN] oVirt 4.3.6 is now generally available

[ovirt-users] Re: [ANN] oVirt 4.3.6 is now generally available

[ovirt-users] Re: Fwd: Unable to Upgrade

[ovirt-users] Re: Fwd: Unable to Upgrade

[ovirt-users] Re: Fwd: Unable to Upgrade

[ovirt-users] Re: Fwd: Unable to Upgrade

[ovirt-users] Re: change connection string in db

[ovirt-users] Re: Fwd: Unable to Upgrade

[ovirt-users] Fwd: Unable to Upgrade

[ovirt-users] Re: [ANN] oVirt 4.3.6 is now generally available

[ovirt-users] Re: [ANN] oVirt 4.3.6 is now generally available

[ovirt-users] Re: Creating vm from snapshot via API

[ovirt-users] Re: [ANN] oVirt 4.3.6 is now generally available

[ovirt-users] Re: [ANN] oVirt 4.3.6 is now generally available

[ovirt-users] Re: [ANN] oVirt 4.3.6 is now generally available

[ovirt-users] Re: [ANN] oVirt 4.3.6 is now generally available

26 matches

Site Navigation

Mail list logo

Footer information