[ovirt-users] Can't Install/Upgrade host
Hi guys,
I'm trying to upgrade/re-install a host running Centos 6.5, but even
after removing the host completely and trying to re-add it, I keep
getting a Certificate enrollment failed error. The full error below
is taken from my engine.log...
2014-05-27 10:38:33,729 ERROR
[org.ovirt.engine.core.utils.servlet.ServletUtils]
(ajp--127.0.0.1-8702-4) Can't read file
/var/lib/ovirt-engine/reports.xml for request
/ovirt-engine/services/reports-ui, will send a 404 error response.
2014-05-27 11:10:49,343 ERROR [org.ovirt.engine.core.bll.VdsDeploy]
(VdsDeploy) Error during deploy dialog: java.io.IOException:
Unexpected connection termination
2014-05-27 11:10:49,344 ERROR
[org.ovirt.engine.core.utils.ssh.SSHDialog]
(org.ovirt.thread.pool-6-thread-31) SSH error running command
root@10.251.193.9:'umask 0077; MYTMP=$(mktemp -t ovirt-XX);
trap chmod -R u+rwX \${MYTMP}\ /dev/null 21; rm -fr
\${MYTMP}\ /dev/null 21 0; rm -fr ${MYTMP} mkdir
${MYTMP} tar --warning=no-timestamp -C ${MYTMP} -x
${MYTMP}/setup DIALOG/dialect=str:machine
DIALOG/customization=bool:True':
javax.naming.TimeLimitExceededException: SSH session hard timeout host
'root@10.251.193.9'
2014-05-27 11:10:49,369 ERROR [org.ovirt.engine.core.bll.VdsDeploy]
(org.ovirt.thread.pool-6-thread-31) [26c21342] Timeout during host
10.251.193.9 install: javax.naming.TimeLimitExceededException: SSH
session hard timeout host 'root@10.251.193.9'
2014-05-27 11:10:49,377 ERROR
[org.ovirt.engine.core.bll.InstallerMessages]
(org.ovirt.thread.pool-6-thread-31) [26c21342] Installation
10.251.193.9: Processing stopped due to timeout
2014-05-27 11:10:49,434 ERROR
[org.ovirt.engine.core.bll.InstallVdsCommand]
(org.ovirt.thread.pool-6-thread-31) [26c21342] Host installation
failed for host 322cbee8-16e6-11e2-9d38-6388c61dd004,
node02.blabla.gov.za.: javax.naming.TimeLimitExceededException: SSH
session hard timeout host 'root@10.251.193.9'
2014-05-27 12:44:36,200 ERROR
[org.ovirt.engine.core.utils.servlet.ServletUtils]
(ajp--127.0.0.1-8702-1) Can't read file
/var/lib/ovirt-engine/reports.xml for request
/ovirt-engine/services/reports-ui, will send a 404 error response.
2014-05-27 13:16:21,679 ERROR
[org.ovirt.engine.core.utils.hostinstall.OpenSslCAWrapper] (VdsDeploy)
Sign Certificate request failed with exit code 1
2014-05-27 13:16:21,680 ERROR
[org.ovirt.engine.core.utils.hostinstall.OpenSslCAWrapper] (VdsDeploy)
Sign Certificate request script errors:
Error opening Certificate ca.pem
140249235597128:error:0200100D:system library:fopen:Permission
denied:bss_file.c:398:fopen('ca.pem','r')
140249235597128:error:20074002:BIO routines:FILE_CTRL:system lib:bss_file.c:400:
Error opening CA private key private/ca.pem
140630029801288:error:0200100D:system library:fopen:Permission
denied:bss_file.c:398:fopen('private/ca.pem','r')
140630029801288:error:20074002:BIO routines:FILE_CTRL:system lib:bss_file.c:400:
2014-05-27 13:16:21,684 ERROR [org.ovirt.engine.core.bll.VdsDeploy]
(VdsDeploy) Error during deploy dialog: java.lang.RuntimeException:
Certificate enrollment failed
2014-05-27 13:16:21,689 ERROR [org.ovirt.engine.core.bll.VdsDeploy]
(org.ovirt.thread.pool-6-thread-21) [1a930dd7] Error during host
10.251.193.9 install: java.lang.RuntimeException: Certificate
enrollment failed
2014-05-27 13:16:21,694 ERROR
[org.ovirt.engine.core.bll.InstallerMessages]
(org.ovirt.thread.pool-6-thread-21) [1a930dd7] Installation
10.251.193.9: Certificate enrollment failed
2014-05-27 13:16:21,740 ERROR [org.ovirt.engine.core.bll.VdsDeploy]
(org.ovirt.thread.pool-6-thread-21) [1a930dd7] Error during host
10.251.193.9 install, prefering first exception:
java.lang.RuntimeException: Certificate enrollment failed
2014-05-27 13:16:21,744 ERROR
[org.ovirt.engine.core.bll.InstallVdsCommand]
(org.ovirt.thread.pool-6-thread-21) [1a930dd7] Host installation
failed for host 322cbee8-16e6-11e2-9d38-6388c61dd004,
node02.blabla.gov.za.: java.lang.RuntimeException: Certificate
enrollment failed
2014-05-27 14:31:12,192 ERROR
[org.ovirt.engine.core.utils.servlet.ServletUtils]
(ajp--127.0.0.1-8702-2) Can't read file
/var/lib/ovirt-engine/reports.xml for request
/ovirt-engine/services/reports-ui, will send a 404 error response.
2014-05-27 14:32:58,669 ERROR
[org.ovirt.engine.core.utils.servlet.ServletUtils]
(ajp--127.0.0.1-8702-7) Can't read file
/var/lib/ovirt-engine/reports.xml for request
/ovirt-engine/services/reports-ui, will send a 404 error response.
2014-05-27 14:36:33,523 ERROR
[org.ovirt.engine.core.utils.hostinstall.OpenSslCAWrapper] (VdsDeploy)
Sign Certificate request failed with exit code 1
2014-05-27 14:36:33,524 ERROR
[org.ovirt.engine.core.utils.hostinstall.OpenSslCAWrapper] (VdsDeploy)
Sign Certificate request script errors:
Error opening Certificate ca.pem
140189576382280:error:0200100D:system library:fopen:Permission
denied:bss_file.c:398:fopen('ca.pem','r')
140189576382280:error:20074002:BIO routines:FILE_CTRL:system lib:bss_file.c:400:
Error opening CA private key private/ca.pem
Re: [ovirt-users] Can't Install/Upgrade host
Please send the output of:
# ls -lR /etc/pki/ovirt-engine/
- Original Message -
From: Neil nwilson...@gmail.com
To: users@ovirt.org
Sent: Wednesday, May 28, 2014 9:04:57 AM
Subject: [ovirt-users] Can't Install/Upgrade host
Hi guys,
I'm trying to upgrade/re-install a host running Centos 6.5, but even
after removing the host completely and trying to re-add it, I keep
getting a Certificate enrollment failed error. The full error below
is taken from my engine.log...
2014-05-27 10:38:33,729 ERROR
[org.ovirt.engine.core.utils.servlet.ServletUtils]
(ajp--127.0.0.1-8702-4) Can't read file
/var/lib/ovirt-engine/reports.xml for request
/ovirt-engine/services/reports-ui, will send a 404 error response.
2014-05-27 11:10:49,343 ERROR [org.ovirt.engine.core.bll.VdsDeploy]
(VdsDeploy) Error during deploy dialog: java.io.IOException:
Unexpected connection termination
2014-05-27 11:10:49,344 ERROR
[org.ovirt.engine.core.utils.ssh.SSHDialog]
(org.ovirt.thread.pool-6-thread-31) SSH error running command
root@10.251.193.9:'umask 0077; MYTMP=$(mktemp -t ovirt-XX);
trap chmod -R u+rwX \${MYTMP}\ /dev/null 21; rm -fr
\${MYTMP}\ /dev/null 21 0; rm -fr ${MYTMP} mkdir
${MYTMP} tar --warning=no-timestamp -C ${MYTMP} -x
${MYTMP}/setup DIALOG/dialect=str:machine
DIALOG/customization=bool:True':
javax.naming.TimeLimitExceededException: SSH session hard timeout host
'root@10.251.193.9'
2014-05-27 11:10:49,369 ERROR [org.ovirt.engine.core.bll.VdsDeploy]
(org.ovirt.thread.pool-6-thread-31) [26c21342] Timeout during host
10.251.193.9 install: javax.naming.TimeLimitExceededException: SSH
session hard timeout host 'root@10.251.193.9'
2014-05-27 11:10:49,377 ERROR
[org.ovirt.engine.core.bll.InstallerMessages]
(org.ovirt.thread.pool-6-thread-31) [26c21342] Installation
10.251.193.9: Processing stopped due to timeout
2014-05-27 11:10:49,434 ERROR
[org.ovirt.engine.core.bll.InstallVdsCommand]
(org.ovirt.thread.pool-6-thread-31) [26c21342] Host installation
failed for host 322cbee8-16e6-11e2-9d38-6388c61dd004,
node02.blabla.gov.za.: javax.naming.TimeLimitExceededException: SSH
session hard timeout host 'root@10.251.193.9'
2014-05-27 12:44:36,200 ERROR
[org.ovirt.engine.core.utils.servlet.ServletUtils]
(ajp--127.0.0.1-8702-1) Can't read file
/var/lib/ovirt-engine/reports.xml for request
/ovirt-engine/services/reports-ui, will send a 404 error response.
2014-05-27 13:16:21,679 ERROR
[org.ovirt.engine.core.utils.hostinstall.OpenSslCAWrapper] (VdsDeploy)
Sign Certificate request failed with exit code 1
2014-05-27 13:16:21,680 ERROR
[org.ovirt.engine.core.utils.hostinstall.OpenSslCAWrapper] (VdsDeploy)
Sign Certificate request script errors:
Error opening Certificate ca.pem
140249235597128:error:0200100D:system library:fopen:Permission
denied:bss_file.c:398:fopen('ca.pem','r')
140249235597128:error:20074002:BIO routines:FILE_CTRL:system
lib:bss_file.c:400:
Error opening CA private key private/ca.pem
140630029801288:error:0200100D:system library:fopen:Permission
denied:bss_file.c:398:fopen('private/ca.pem','r')
140630029801288:error:20074002:BIO routines:FILE_CTRL:system
lib:bss_file.c:400:
2014-05-27 13:16:21,684 ERROR [org.ovirt.engine.core.bll.VdsDeploy]
(VdsDeploy) Error during deploy dialog: java.lang.RuntimeException:
Certificate enrollment failed
2014-05-27 13:16:21,689 ERROR [org.ovirt.engine.core.bll.VdsDeploy]
(org.ovirt.thread.pool-6-thread-21) [1a930dd7] Error during host
10.251.193.9 install: java.lang.RuntimeException: Certificate
enrollment failed
2014-05-27 13:16:21,694 ERROR
[org.ovirt.engine.core.bll.InstallerMessages]
(org.ovirt.thread.pool-6-thread-21) [1a930dd7] Installation
10.251.193.9: Certificate enrollment failed
2014-05-27 13:16:21,740 ERROR [org.ovirt.engine.core.bll.VdsDeploy]
(org.ovirt.thread.pool-6-thread-21) [1a930dd7] Error during host
10.251.193.9 install, prefering first exception:
java.lang.RuntimeException: Certificate enrollment failed
2014-05-27 13:16:21,744 ERROR
[org.ovirt.engine.core.bll.InstallVdsCommand]
(org.ovirt.thread.pool-6-thread-21) [1a930dd7] Host installation
failed for host 322cbee8-16e6-11e2-9d38-6388c61dd004,
node02.blabla.gov.za.: java.lang.RuntimeException: Certificate
enrollment failed
2014-05-27 14:31:12,192 ERROR
[org.ovirt.engine.core.utils.servlet.ServletUtils]
(ajp--127.0.0.1-8702-2) Can't read file
/var/lib/ovirt-engine/reports.xml for request
/ovirt-engine/services/reports-ui, will send a 404 error response.
2014-05-27 14:32:58,669 ERROR
[org.ovirt.engine.core.utils.servlet.ServletUtils]
(ajp--127.0.0.1-8702-7) Can't read file
/var/lib/ovirt-engine/reports.xml for request
/ovirt-engine/services/reports-ui, will send a 404 error response.
2014-05-27 14:36:33,523 ERROR
[org.ovirt.engine.core.utils.hostinstall.OpenSslCAWrapper] (VdsDeploy)
Sign Certificate request failed with exit code 1
2014-05-27 14:36:33,524 ERROR
[ovirt-users] hosted-engine configure startup time allowance?
Hi, I was just wondering if it's possible to configure the startup-time allowance of the hosted-engine? I seem to sometime have this issue where my hosted-engine would start automatically but it would be sent a reboot signal 30 seconds before the engine has time to startup. This is because it fails the 'liveliness check', just before it reboots the engine status would be set to up but as the reboot signal was already sent the VM will reboot and then startup on another host. This then goes into a loop, until I do a global maintenance, manual bootup and then maintenance mode none. Thanks, Andrew. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Can't Install/Upgrade host
Hi Alon,
Thanks for the reply, below is the output.
[root@engine01 ovirt-engine]# ls -lR /etc/pki/ovirt-engine/
/etc/pki/ovirt-engine/:
total 80
lrwxrwxrwx. 1 root root 6 May 16 13:56 apache-ca.pem - ca.pem
-rw-r--r--. 1 root root 570 May 16 13:56 cacert.conf
-rw-r--r--. 1 root root 519 May 16 13:56 cacert.template
-rw-r--r--. 1 root root 384 Mar 24 12:47 cacert.template.in
-rw-r--r--. 1 root root 482 May 16 13:56 cacert.template.rpmnew
-rwxr-x---. 1 root root 3362 May 16 13:56 ca.pem
-rw-r--r--. 1 root root 585 May 16 13:56 cert.conf
drwxr-xr-x. 2 ovirt ovirt 4096 Mar 24 12:47 certs
-rw-r--r--. 1 root root 572 May 16 13:56 cert.template
-rw-r--r--. 1 root root 483 Mar 24 12:47 cert.template.in
-rw-r--r--. 1 root root 534 May 16 13:56 cert.template.rpmnew
-rw-r--r--. 1 ovirt ovirt 950 May 22 20:07 database.txt
-rw-r--r--. 1 ovirt ovirt 20 May 22 20:07 database.txt.attr
-rw-r--r--. 1 ovirt ovirt 20 May 16 13:56 database.txt.attr.old
-rw-r--r--. 1 ovirt ovirt 885 May 16 13:56 database.txt.old
drwxr-xr-x. 2 root root 4096 Mar 24 12:47 keys
-rw-r--r--. 1 root root 548 Mar 24 12:47 openssl.conf
drwxr-x---. 2 ovirt ovirt 4096 Mar 24 12:47 private
drwxr-xr-x. 2 ovirt ovirt 4096 May 27 13:16 requests
-rw-r--r--. 1 ovirt ovirt3 May 22 20:07 serial.txt
-rw-r--r--. 1 ovirt ovirt3 May 16 13:56 serial.txt.old
/etc/pki/ovirt-engine/certs:
total 100
-rw-r--r--. 1 root root 3362 May 16 13:56 01.pem
-rw-r--r--. 1 root root 3509 May 16 13:56 02.pem
-rw-r--r--. 1 root root 3466 May 16 13:56 03.pem
-rw-r--r--. 1 root root 3466 May 16 13:56 04.pem
-rw-r--r--. 1 root root 3362 May 16 13:56 05.pem
-rw-r--r--. 1 root root 3509 May 16 13:56 06.pem
-rw-r--r--. 1 root root 3362 May 16 13:56 07.pem
-rw-r--r--. 1 root root 3509 May 16 13:56 08.pem
-rw-r--r--. 1 root root 3466 May 16 13:56 09.pem
-rw-r--r--. 1 root root 3467 May 16 13:56 0A.pem
-rw-r--r--. 1 root root 3467 May 16 13:56 0B.pem
-rw-r--r--. 1 root root 3467 May 16 13:56 0C.pem
-rw-r--r--. 1 root root 3467 May 16 13:56 0D.pem
-rw-r--r--. 1 root root 3070 May 16 13:56 0E.pem
-rw-r--r--. 1 root root 3070 May 16 13:56 0F.pem
-rw-r--r--. 1 root root 3070 May 16 13:56 10.251.193.8cert.pem
-rw-r--r--. 1 root root 3070 May 16 13:56 10.251.193.9cert.pem
-rw-r--r--. 1 root root 4267 May 22 20:07 10.pem
-rw-r-. 1 root root 3509 May 16 13:56 apache.cer
-rw-r--r--. 1 root root 763 May 16 13:56 ca.der
-rw-r--r--. 1 root root 3509 May 16 13:56 engine.cer
-rw-r--r--. 1 root root 784 May 16 13:56 engine.der
-rw-r--r--. 1 root root 4267 May 22 20:07 websocket-proxy.cer
/etc/pki/ovirt-engine/keys:
total 36
-rw-r-. 1 root root 916 May 16 13:56 apache.key.nopass
-rw-r-. 1 root root 2786 May 16 13:56 apache.p12
-rw---. 1 root root 1054 May 22 20:07 engine_id_rsa
-rw---. 1 root root 916 May 16 13:56 engine_id_rsa.20140522200739
-rw---. 1 root root 912 May 16 13:56 engine_id_rsa.old
-rw-r-. 1 ovirt ovirt 2786 May 16 13:56 engine.p12
-rw-r--r--. 1 root root 220 May 16 13:56 engine.ssh.key.txt
-rw---. 1 ovirt ovirt 1832 May 22 20:07 websocket-proxy.key.nopass
-rw---. 1 root root 2517 May 22 20:07 websocket-proxy.p12
/etc/pki/ovirt-engine/private:
total 4
-rwxr-x---. 1 root root 887 May 16 13:56 ca.pem
/etc/pki/ovirt-engine/requests:
total 24
-rw-r--r--. 1 root root 862 May 16 13:56 10.251.193.8req.pem
-rw-r--r--. 1 ovirt ovirt 862 May 27 17:35 10.251.193.9.req
-rw-r--r--. 1 root root 862 May 16 13:56 10.251.193.9req.pem
-rw-r--r--. 1 root root 603 May 16 13:56 ca.csr
-rw-r--r--. 1 root root 597 May 16 13:56 engine.req
-rw-r--r--. 1 root root 863 May 22 20:07 websocket-proxy.req
On Wed, May 28, 2014 at 8:19 AM, Alon Bar-Lev alo...@redhat.com wrote:
Please send the output of:
# ls -lR /etc/pki/ovirt-engine/
- Original Message -
From: Neil nwilson...@gmail.com
To: users@ovirt.org
Sent: Wednesday, May 28, 2014 9:04:57 AM
Subject: [ovirt-users] Can't Install/Upgrade host
Hi guys,
I'm trying to upgrade/re-install a host running Centos 6.5, but even
after removing the host completely and trying to re-add it, I keep
getting a Certificate enrollment failed error. The full error below
is taken from my engine.log...
2014-05-27 10:38:33,729 ERROR
[org.ovirt.engine.core.utils.servlet.ServletUtils]
(ajp--127.0.0.1-8702-4) Can't read file
/var/lib/ovirt-engine/reports.xml for request
/ovirt-engine/services/reports-ui, will send a 404 error response.
2014-05-27 11:10:49,343 ERROR [org.ovirt.engine.core.bll.VdsDeploy]
(VdsDeploy) Error during deploy dialog: java.io.IOException:
Unexpected connection termination
2014-05-27 11:10:49,344 ERROR
[org.ovirt.engine.core.utils.ssh.SSHDialog]
(org.ovirt.thread.pool-6-thread-31) SSH error running command
root@10.251.193.9:'umask 0077; MYTMP=$(mktemp -t ovirt-XX);
trap chmod -R u+rwX \${MYTMP}\ /dev/null 21; rm -fr
\${MYTMP}\ /dev/null 21 0; rm -fr ${MYTMP} mkdir
${MYTMP} tar --warning=no-timestamp
Re: [ovirt-users] hosted-engine configure startup time allowance?
On 05/28/2014 08:52 AM, Andrew Lau wrote: Hi, I was just wondering if it's possible to configure the startup-time allowance of the hosted-engine? I seem to sometime have this issue where my hosted-engine would start automatically but it would be sent a reboot signal 30 seconds before the engine has time to startup. This is because it fails the 'liveliness check', just before it reboots the engine status would be set to up but as the reboot signal was already sent the VM will reboot and then startup on another host. This then goes into a loop, until I do a global maintenance, manual bootup and then maintenance mode none. Hi Andrew, try to look into [1] and tweak the timeouts there. Don't forget to restart the ovirt-ha-agent service when you change it. --Jirka [1] /usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/constants.py Thanks, Andrew. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Can't Install/Upgrade host
- Original Message - From: Neil nwilson...@gmail.com To: Alon Bar-Lev alo...@redhat.com Cc: users@ovirt.org Sent: Wednesday, May 28, 2014 10:04:00 AM Subject: Re: [ovirt-users] Can't Install/Upgrade host Hi Alon, Thanks for the reply, below is the output. Something changed the file attributes of ca.pem (two places) to be incorrect. [root@engine01 ovirt-engine]# ls -lR /etc/pki/ovirt-engine/ /etc/pki/ovirt-engine/: total 80 lrwxrwxrwx. 1 root root 6 May 16 13:56 apache-ca.pem - ca.pem -rw-r--r--. 1 root root 570 May 16 13:56 cacert.conf -rw-r--r--. 1 root root 519 May 16 13:56 cacert.template -rw-r--r--. 1 root root 384 Mar 24 12:47 cacert.template.in -rw-r--r--. 1 root root 482 May 16 13:56 cacert.template.rpmnew -rwxr-x---. 1 root root 3362 May 16 13:56 ca.pem this ^ should be world readable, not executable. -rw-r--r--. 1 root root 585 May 16 13:56 cert.conf drwxr-xr-x. 2 ovirt ovirt 4096 Mar 24 12:47 certs -rw-r--r--. 1 root root 572 May 16 13:56 cert.template -rw-r--r--. 1 root root 483 Mar 24 12:47 cert.template.in -rw-r--r--. 1 root root 534 May 16 13:56 cert.template.rpmnew -rw-r--r--. 1 ovirt ovirt 950 May 22 20:07 database.txt -rw-r--r--. 1 ovirt ovirt 20 May 22 20:07 database.txt.attr -rw-r--r--. 1 ovirt ovirt 20 May 16 13:56 database.txt.attr.old -rw-r--r--. 1 ovirt ovirt 885 May 16 13:56 database.txt.old drwxr-xr-x. 2 root root 4096 Mar 24 12:47 keys -rw-r--r--. 1 root root 548 Mar 24 12:47 openssl.conf drwxr-x---. 2 ovirt ovirt 4096 Mar 24 12:47 private drwxr-xr-x. 2 ovirt ovirt 4096 May 27 13:16 requests -rw-r--r--. 1 ovirt ovirt3 May 22 20:07 serial.txt -rw-r--r--. 1 ovirt ovirt3 May 16 13:56 serial.txt.old /etc/pki/ovirt-engine/certs: total 100 -rw-r--r--. 1 root root 3362 May 16 13:56 01.pem -rw-r--r--. 1 root root 3509 May 16 13:56 02.pem -rw-r--r--. 1 root root 3466 May 16 13:56 03.pem -rw-r--r--. 1 root root 3466 May 16 13:56 04.pem -rw-r--r--. 1 root root 3362 May 16 13:56 05.pem -rw-r--r--. 1 root root 3509 May 16 13:56 06.pem -rw-r--r--. 1 root root 3362 May 16 13:56 07.pem -rw-r--r--. 1 root root 3509 May 16 13:56 08.pem -rw-r--r--. 1 root root 3466 May 16 13:56 09.pem -rw-r--r--. 1 root root 3467 May 16 13:56 0A.pem -rw-r--r--. 1 root root 3467 May 16 13:56 0B.pem -rw-r--r--. 1 root root 3467 May 16 13:56 0C.pem -rw-r--r--. 1 root root 3467 May 16 13:56 0D.pem -rw-r--r--. 1 root root 3070 May 16 13:56 0E.pem -rw-r--r--. 1 root root 3070 May 16 13:56 0F.pem -rw-r--r--. 1 root root 3070 May 16 13:56 10.251.193.8cert.pem -rw-r--r--. 1 root root 3070 May 16 13:56 10.251.193.9cert.pem these two are strange as I expect to be owned by ovirt user as engine created. -rw-r--r--. 1 root root 4267 May 22 20:07 10.pem -rw-r-. 1 root root 3509 May 16 13:56 apache.cer -rw-r--r--. 1 root root 763 May 16 13:56 ca.der -rw-r--r--. 1 root root 3509 May 16 13:56 engine.cer -rw-r--r--. 1 root root 784 May 16 13:56 engine.der -rw-r--r--. 1 root root 4267 May 22 20:07 websocket-proxy.cer /etc/pki/ovirt-engine/keys: total 36 -rw-r-. 1 root root 916 May 16 13:56 apache.key.nopass -rw-r-. 1 root root 2786 May 16 13:56 apache.p12 -rw---. 1 root root 1054 May 22 20:07 engine_id_rsa -rw---. 1 root root 916 May 16 13:56 engine_id_rsa.20140522200739 -rw---. 1 root root 912 May 16 13:56 engine_id_rsa.old -rw-r-. 1 ovirt ovirt 2786 May 16 13:56 engine.p12 -rw-r--r--. 1 root root 220 May 16 13:56 engine.ssh.key.txt -rw---. 1 ovirt ovirt 1832 May 22 20:07 websocket-proxy.key.nopass -rw---. 1 root root 2517 May 22 20:07 websocket-proxy.p12 /etc/pki/ovirt-engine/private: total 4 -rwxr-x---. 1 root root 887 May 16 13:56 ca.pem this should be owned by ovirt user and not be executable. /etc/pki/ovirt-engine/requests: total 24 -rw-r--r--. 1 root root 862 May 16 13:56 10.251.193.8req.pem -rw-r--r--. 1 ovirt ovirt 862 May 27 17:35 10.251.193.9.req -rw-r--r--. 1 root root 862 May 16 13:56 10.251.193.9req.pem -rw-r--r--. 1 root root 603 May 16 13:56 ca.csr -rw-r--r--. 1 root root 597 May 16 13:56 engine.req -rw-r--r--. 1 root root 863 May 22 20:07 websocket-proxy.req On Wed, May 28, 2014 at 8:19 AM, Alon Bar-Lev alo...@redhat.com wrote: Please send the output of: # ls -lR /etc/pki/ovirt-engine/ - Original Message - From: Neil nwilson...@gmail.com To: users@ovirt.org Sent: Wednesday, May 28, 2014 9:04:57 AM Subject: [ovirt-users] Can't Install/Upgrade host Hi guys, I'm trying to upgrade/re-install a host running Centos 6.5, but even after removing the host completely and trying to re-add it, I keep getting a Certificate enrollment failed error. The full error below is taken from my engine.log... 2014-05-27 10:38:33,729 ERROR [org.ovirt.engine.core.utils.servlet.ServletUtils] (ajp--127.0.0.1-8702-4) Can't read file /var/lib/ovirt-engine/reports.xml
[ovirt-users] [QE][ACTION NEEDED] oVirt 3.5.0 Second Alpha status
Hi, We're preparing for feature freeze scheduled for 2014-05-30. We're going to compose a Second Alpha on Firday *2014-05-30 08:00 UTC*. Maintainers: - Please be sure that master snapshot allow to create VMs before *2014-05-29 15:00 UTC* The bug tracker [1] shows the following proposed blockers to be reviewed: Bug ID Whiteboard Status Summary 1001100 integration NEW Add log gathering for a new ovirt module (External scheduler) 1073944 integration ASSIGNEDAdd log gathering for a new ovirt module (External scheduler) 1060198 integration NEW [RFE] add support for Fedora 20 1100236 integration NEW all-in-one setup should configure cluster compatibility as max common between vdsm and engine Feature freeze has been postponed to 2014-05-30 and the following features should be testable in 3.5.0 Alpha according to Features Status Table [2] Group oVirt BZTitle gluster 1096713 Monitoring (UI plugin) Dashboard (Integrated with Nagios monitoring) infra 1090530 [RFE] Please add host count and guest count columns to Clusters tab in webadmin infra 1078738 [RFE] make ovirt easy configurable to allow redirection of all logs to syslog infra 1054778 [RFE] Allow to perform fence operations from a host in another DC infra 1090803 [RFE] Change the Slot field to Service Profile when cisco_ucs is selected as the fencing type infra 1090511 [RFE] Improve fencing robustness by retrying failed attempts infra 1090800 [RFE] Add periodic power management health check to detect/warn about link-down detection of power management LAN infra 1090794 [RFE] Search VMs based on MAC address from web-admin portal infra 1090793 consider the event type while printing events to engine.log infra 1090796 [RFE] Re-work engine ovirt-node host-deploy sequence infra 1090798 [RFE] Admin GUI - Add host uptime information to the General tab infra 1090808 [RFE] Ability to dismiss alerts and events from web-admin portal infra 1058737 [RFE] Restart HA VMs ASAP infra-api 1090797 [RFE] RESTAPI: Add /tags sub-collection for Template resource infra-dwh 1091686 prevent OutOfMemoryError after starting the dwh service. infra-dwh 1091687 History DB should sync user's first and last name for user usage tables network 1078836 Add a warning when adding display network network 1079719 Display of NIC Slave/Bond fault on Event Log network 1080984 Support bridging_opts functionality within oVirt network 1080987 Support ethtool_opts functionality within oVirt network 1078862 Providing Neutron Applience storage Store OVF on any domains storage 1083312 Disk alias recycling in web-admin portal storage 1086181 [RFE] Snapshot overview in webadmin portal ux 1064543 oVirt new look and feel [PatternFly adoption] - phase #1 virt1058832 Allow to clone a (down) VM without snapshot/template virt1031040 can't set different keymap for vnc via runonce option virt1043471 oVirt guest agent for SLES virt1073453 Debian 7 support (incl. 1043474 oVirt guest agent for Debian) virt1072313 Edit Running Vm virt1083049 add progress bar for vm migration virt1083065 EL 7 guest compatibility virtAllow guest serial number to be configurable virt1047624 [RFE] support BIOS boot device menu virt1083129 allows setting netbios name, locale, language and keyboard settings for windows vm's virt1038632 spice-html5 button to show debug console/output window virt1080002 [RFE] Enable user defined Windows Sysprep file Some more features may be included since they were near to be completed on last sync meeting. The table will be updated on next sync meeting scheduled for 2014-05-28. There are still 377 bugs [3] targeted to 3.5.0. Excluding node and documentation bugs we still have 314 bugs [4] targeted to 3.5.0. Maintainers / Assignee: - Please remember to rebuild your packages before *2014-05-29 15:00 UTC* if needed, otherwise nightly snapshot will be taken. - Please be sure that master snapshot allow to create VMs before *2014-05-29 15:00 UTC* - If you find a blocker bug please remember to add it to the tracker [1] - Please start filling release notes, the page has been created here [5] - Please review and add test cases to oVirt 3.5 Test Day [6] Community: - You're welcome to join us testing this alpha release and
Re: [ovirt-users] Help creating virtual machines in ovirt
- Original Message - From: Grant Tailor therealwebg...@gmail.com To: Omer Frenkel ofren...@redhat.com, vanoppen koen vanoppen.k...@gmail.com Cc: Eli Mesika emes...@redhat.com, users@ovirt.org Sent: Wednesday, May 28, 2014 3:59:33 AM Subject: Re: [ovirt-users] Help creating virtual machines in ovirt Ok here is what i have so far The PC i am using are 2 identical Dell Optiplex XE with Intel Core 2 Duo E8400 and 16GB RAM Please see all screenshots...since you can see most things better Also i have no idea how to look at the vm_static database..so if you tell me the steps to take to get to it..will appreciate it. Thanks. ok from 1ovirt.png you can clearly see that the 'Emulated Machine' is null for the cluster you probably hit https://bugzilla.redhat.com/show_bug.cgi?id=1077300 you can try maintenance ALL hosts and activate them again. if it doesnt work, need to see what Emulations your host support, run this on one of them: vdsClient -s 0 getVdsCaps and please paste here what returned for 'emulatedMachines' ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] [QE][ACTION NEEDED] oVirt 3.4.2 status
Hi, We're going to start composing oVirt 3.4.2 GA on *2014-06-10 08:00 UTC* from 3.4.2 branches. The bug tracker [1] shows no blocking bugs for the release There are still 58 bugs [2] targeted to 3.4.2. Excluding node and documentation bugs we still have 27 bugs [3] targeted to 3.4.2. Maintainers / Assignee: - Please add the bugs to the tracker if you think that 3.4.2 should not be released without them fixed. - Please update the target to any next release for bugs that won't be in 3.4.2: it will ease gathering the blocking bugs for next releases. Critical bugs will be re-targeted to 3.4.3 after 3.4.2 GA release. All remaining bugs will be re-targeted to 3.5.0. - Please fill release notes, the page has been created here [4] - Please build packages before *2014-06-09 15:00 UTC*. Community: - If you're testing oVirt 3.4.2 RC, please add yourself to the test page [5] [1] http://bugzilla.redhat.com/1095370 [2] http://red.ht/1oqLLlr [3] http://red.ht/1nIAZXO [4] http://www.ovirt.org/OVirt_3.4.2_Release_Notes [5] http://www.ovirt.org/Testing/oVirt_3.4.2_Testing Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Can HA Agent control NFS Mount?
Hi Doron, Before the initial thread sways a little more.. On Mon, May 26, 2014 at 4:38 PM, Doron Fediuck dfedi...@redhat.com wrote: - Original Message - From: Andrew Lau and...@andrewklau.com To: Bob Doolittle b...@doolittle.us.com Cc: users users@ovirt.org Sent: Monday, May 26, 2014 7:30:41 AM Subject: Re: [ovirt-users] Can HA Agent control NFS Mount? On Mon, May 26, 2014 at 5:10 AM, Bob Doolittle b...@doolittle.us.com wrote: On 05/25/2014 02:51 PM, Joop wrote: On 25-5-2014 19:38, Bob Doolittle wrote: Also curious is that when I say poweroff it actually reboots and comes up again. Could that be due to the timeouts on the way down? Ah, that's something my F19 host does too. Some more info: if engine hasn't been started on the host then I can shutdown it and it will poweroff. IF engine has been run on it then it will reboot. Its not vdsm (I think) because my shutdown sequence is (on my f19 host): service ovirt-agent-ha stop service ovirt-agent-broker stop service vdsmd stop ssh root@engine01 init 0 init 0 I don't use maintenance mode because when I poweron my host (= my desktop) I want engine to power on automatically which it does most of the time within 10 min. For comparison, I see this issue and I *do* use maintenance mode (because presumably that's the 'blessed' way to shut things down and I'm scared to mess this complex system up by straying off the beaten path ;). My process is: ssh root@engine init 0 (wait for vdsClient -s 0 list | grep Status: to show the vm as down) hosted-engine --set-maintenance --mode=global poweroff And then on startup: hosted-engine --set-maintenance --mode=none hosted-engine --vm-start There are two issues here. I am not sure if they are related or not. 1. The NFS timeout during shutdown (Joop do you see this also? Or just #2?) 2. The system reboot instead of poweroff (which messes up remote machine management) For 1. I was wondering if perhaps, we could have an option to specify the mount options. If I understand correctly, applying a soft mount instead of a hard mount would prevent this from happening. I'm however not sure of the implications this would have on the data integrity.. I would really like to see it happen in the ha-agent, as it's the one which connects/mounts the storage it should also unmount it on boot. However the stability on it, is flaky at best. I've noticed if `df` hangs because of another NFS mount having timed-out the agent will die. That's not a good sign.. this was what actually caused my hosted-engine to run twice in one case. Thanks, Bob I think wdmd or sanlock are causing the reboot instead of poweroff Joop Great to have your feedback guys! So just to clarify some of the issues you mentioned; Hosted engine wasn't designed for a 'single node' use case, as we do want it to be highly available. This is why it's being restarted elsewhere or even on the same server if no better alternative. Having said that, it is possible to set global maintenance mode as a first step (in the UI: right click engine vm and choose ha-maintenance). Then you can ssh into the engine vm and init 0. After a short while, the qemu process should gracefully end and release its sanlock lease as well as any other resource, which means you can reboot your hypervisor peacefully. What about in a 2 host cluster. Lets say we want to take down 1 host for maintenance, so 50% chance it could be running the engine. Would setting maintenance-mode local do the same thing and allow a clean shutdown/reboot? Doron ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] hosted-engine configure startup time allowance?
Hi Jiri, On Wed, May 28, 2014 at 5:10 PM, Jiri Moskovcak jmosk...@redhat.com wrote: On 05/28/2014 08:52 AM, Andrew Lau wrote: Hi, I was just wondering if it's possible to configure the startup-time allowance of the hosted-engine? I seem to sometime have this issue where my hosted-engine would start automatically but it would be sent a reboot signal 30 seconds before the engine has time to startup. This is because it fails the 'liveliness check', just before it reboots the engine status would be set to up but as the reboot signal was already sent the VM will reboot and then startup on another host. This then goes into a loop, until I do a global maintenance, manual bootup and then maintenance mode none. Hi Andrew, try to look into [1] and tweak the timeouts there. Don't forget to restart the ovirt-ha-agent service when you change it. Thanks, I'll try that out. Are all those values there available in /etc/ovirt-hosted-engine-ha/agent.conf ? --Jirka [1] /usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/constants.py Thanks, Andrew. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] workflow node installation
On 05/27/2014 06:25 PM, Ryan Barry wrote: On 05/26/2014 04:15 AM, Fabian Deutsch wrote: Am Sonntag, den 25.05.2014, 09:01 -0400 schrieb Doron Fediuck: Don't we have ovirtmgmt defined by default during the registration process? Hey, IIRC that is done by ovirt-host-deploy during the registration, yes. - fabian - Forwarded Message - From: Jorick Astrego j.astr...@netbulae.eu To: users users@ovirt.org Sent: Monday, May 19, 2014 1:11:58 PM Subject: [ovirt-users] workflow node installation Hi, I don't know if I'm doing things wrong but the workflow for node installation is a bit cumbersome for me. The things I have to do to get a node up in ovirt engine: - install node image from pxe - approve node - put node into maintenance mode (storage not available) - Setup Host Networks - Sync network (otherwise I cannot save the network changes) - Setup Host Networks again - Save Network setup - activate node This seems problematic to me -- the host networks should be automatically set when you approve the node joining a given cluster. Are you setting up the host networks on the engine side, or do you have to approve, log back into the node, configure networking, etc? Everything from the engine side, we would like to deploy all the servers without manual intervention as much as possible so we don't have to login to the nodes at all. Preferably we disable local login completely for security purposes. ovirtmgmt works fine but I have two iSCSI networks and a separate internet network that are all set to required network. And this I have to do for every node. It could save me some time if I could setup the networks on approval or engine puts it directly into maintenance mode without the sync requirement. Kind regards, Jorick Astrego Netbulae B.V. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] engine-setup : Failed to execute stage 'Environment setup'
Le 28/05/2014 01:18, Alon Bar-Lev a écrit : - Original Message - From: Alon Bar-Lev alo...@redhat.com To: Nathanaël Blanchet blanc...@abes.fr Cc: users@ovirt.org Sent: Wednesday, May 28, 2014 2:16:16 AM Subject: Re: [ovirt-users] engine-setup : Failed to execute stage 'Environment setup' - Original Message - From: Nathanaël Blanchet blanc...@abes.fr To: users@ovirt.org Sent: Wednesday, May 28, 2014 2:06:26 AM Subject: [ovirt-users] engine-setup : Failed to execute stage 'Environment setup' Hello, I deleted ovirt_engine_reports* database from postgres because I didn't want anymore to use dwh after testing it. Now when I run engine-setup for upgrading or configuring, I always get this error and I can't successfully end the setup : [ ERROR ] Failed to execute stage 'Environment setup': Cannot connect to Reports database using existing credentials: ovirt_engine_reports_20140527180625@localhost:5432 What can I do for running engine-config? Backup and remove /etc/ovirt-engine-reports/ovirt-engine-reports.conf.d/10* And try again. those files were already erased You probably need to remove /var/lib/ovirt-engine-reports/build-conf as well. This command was the good one to solve the issue, thanks. ovirt 3.4.1 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users -- Nathanaël Blanchet Supervision réseau Pôle exploitation et maintenance Département des systèmes d'information 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanc...@abes.fr ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] hosted-engine configure startup time allowance?
On 05/28/2014 10:08 AM, Andrew Lau wrote: Hi Jiri, On Wed, May 28, 2014 at 5:10 PM, Jiri Moskovcak jmosk...@redhat.com wrote: On 05/28/2014 08:52 AM, Andrew Lau wrote: Hi, I was just wondering if it's possible to configure the startup-time allowance of the hosted-engine? I seem to sometime have this issue where my hosted-engine would start automatically but it would be sent a reboot signal 30 seconds before the engine has time to startup. This is because it fails the 'liveliness check', just before it reboots the engine status would be set to up but as the reboot signal was already sent the VM will reboot and then startup on another host. This then goes into a loop, until I do a global maintenance, manual bootup and then maintenance mode none. Hi Andrew, try to look into [1] and tweak the timeouts there. Don't forget to restart the ovirt-ha-agent service when you change it. Thanks, I'll try that out. Are all those values there available in /etc/ovirt-hosted-engine-ha/agent.conf ? - no, they're not --Jirka [1] /usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/constants.py Thanks, Andrew. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Can HA Agent control NFS Mount?
- Original Message - From: Andrew Lau and...@andrewklau.com To: Doron Fediuck dfedi...@redhat.com Cc: Bob Doolittle b...@doolittle.us.com, users users@ovirt.org, Jiri Moskovcak jmosk...@redhat.com, Sandro Bonazzola sbona...@redhat.com Sent: Wednesday, May 28, 2014 11:03:38 AM Subject: Re: [ovirt-users] Can HA Agent control NFS Mount? Hi Doron, Before the initial thread sways a little more.. On Mon, May 26, 2014 at 4:38 PM, Doron Fediuck dfedi...@redhat.com wrote: - Original Message - From: Andrew Lau and...@andrewklau.com To: Bob Doolittle b...@doolittle.us.com Cc: users users@ovirt.org Sent: Monday, May 26, 2014 7:30:41 AM Subject: Re: [ovirt-users] Can HA Agent control NFS Mount? On Mon, May 26, 2014 at 5:10 AM, Bob Doolittle b...@doolittle.us.com wrote: On 05/25/2014 02:51 PM, Joop wrote: On 25-5-2014 19:38, Bob Doolittle wrote: Also curious is that when I say poweroff it actually reboots and comes up again. Could that be due to the timeouts on the way down? Ah, that's something my F19 host does too. Some more info: if engine hasn't been started on the host then I can shutdown it and it will poweroff. IF engine has been run on it then it will reboot. Its not vdsm (I think) because my shutdown sequence is (on my f19 host): service ovirt-agent-ha stop service ovirt-agent-broker stop service vdsmd stop ssh root@engine01 init 0 init 0 I don't use maintenance mode because when I poweron my host (= my desktop) I want engine to power on automatically which it does most of the time within 10 min. For comparison, I see this issue and I *do* use maintenance mode (because presumably that's the 'blessed' way to shut things down and I'm scared to mess this complex system up by straying off the beaten path ;). My process is: ssh root@engine init 0 (wait for vdsClient -s 0 list | grep Status: to show the vm as down) hosted-engine --set-maintenance --mode=global poweroff And then on startup: hosted-engine --set-maintenance --mode=none hosted-engine --vm-start There are two issues here. I am not sure if they are related or not. 1. The NFS timeout during shutdown (Joop do you see this also? Or just #2?) 2. The system reboot instead of poweroff (which messes up remote machine management) For 1. I was wondering if perhaps, we could have an option to specify the mount options. If I understand correctly, applying a soft mount instead of a hard mount would prevent this from happening. I'm however not sure of the implications this would have on the data integrity.. I would really like to see it happen in the ha-agent, as it's the one which connects/mounts the storage it should also unmount it on boot. However the stability on it, is flaky at best. I've noticed if `df` hangs because of another NFS mount having timed-out the agent will die. That's not a good sign.. this was what actually caused my hosted-engine to run twice in one case. Thanks, Bob I think wdmd or sanlock are causing the reboot instead of poweroff Joop Great to have your feedback guys! So just to clarify some of the issues you mentioned; Hosted engine wasn't designed for a 'single node' use case, as we do want it to be highly available. This is why it's being restarted elsewhere or even on the same server if no better alternative. Having said that, it is possible to set global maintenance mode as a first step (in the UI: right click engine vm and choose ha-maintenance). Then you can ssh into the engine vm and init 0. After a short while, the qemu process should gracefully end and release its sanlock lease as well as any other resource, which means you can reboot your hypervisor peacefully. What about in a 2 host cluster. Lets say we want to take down 1 host for maintenance, so 50% chance it could be running the engine. Would setting maintenance-mode local do the same thing and allow a clean shutdown/reboot? Yes. That's the idea behind of local (aka host) maintenance[1]. Starting 3.4 all you need to do is move the host to maintenance in the UI and this will also set the local maintenance mode for this host. So you should be able to do everything with it, and use 'activate' in the UI to get it into production. [1] http://www.ovirt.org/Features/Self_Hosted_Engine#Maintenance_Flows ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Can't Install/Upgrade host
Hi Alon, That has sorted it out. The permissions got messed up in between restoring from previous backups etc. Thank you very much, greatly appreciated. Regards. Neil Wilson On Wed, May 28, 2014 at 9:11 AM, Alon Bar-Lev alo...@redhat.com wrote: - Original Message - From: Neil nwilson...@gmail.com To: Alon Bar-Lev alo...@redhat.com Cc: users@ovirt.org Sent: Wednesday, May 28, 2014 10:04:00 AM Subject: Re: [ovirt-users] Can't Install/Upgrade host Hi Alon, Thanks for the reply, below is the output. Something changed the file attributes of ca.pem (two places) to be incorrect. [root@engine01 ovirt-engine]# ls -lR /etc/pki/ovirt-engine/ /etc/pki/ovirt-engine/: total 80 lrwxrwxrwx. 1 root root 6 May 16 13:56 apache-ca.pem - ca.pem -rw-r--r--. 1 root root 570 May 16 13:56 cacert.conf -rw-r--r--. 1 root root 519 May 16 13:56 cacert.template -rw-r--r--. 1 root root 384 Mar 24 12:47 cacert.template.in -rw-r--r--. 1 root root 482 May 16 13:56 cacert.template.rpmnew -rwxr-x---. 1 root root 3362 May 16 13:56 ca.pem this ^ should be world readable, not executable. -rw-r--r--. 1 root root 585 May 16 13:56 cert.conf drwxr-xr-x. 2 ovirt ovirt 4096 Mar 24 12:47 certs -rw-r--r--. 1 root root 572 May 16 13:56 cert.template -rw-r--r--. 1 root root 483 Mar 24 12:47 cert.template.in -rw-r--r--. 1 root root 534 May 16 13:56 cert.template.rpmnew -rw-r--r--. 1 ovirt ovirt 950 May 22 20:07 database.txt -rw-r--r--. 1 ovirt ovirt 20 May 22 20:07 database.txt.attr -rw-r--r--. 1 ovirt ovirt 20 May 16 13:56 database.txt.attr.old -rw-r--r--. 1 ovirt ovirt 885 May 16 13:56 database.txt.old drwxr-xr-x. 2 root root 4096 Mar 24 12:47 keys -rw-r--r--. 1 root root 548 Mar 24 12:47 openssl.conf drwxr-x---. 2 ovirt ovirt 4096 Mar 24 12:47 private drwxr-xr-x. 2 ovirt ovirt 4096 May 27 13:16 requests -rw-r--r--. 1 ovirt ovirt3 May 22 20:07 serial.txt -rw-r--r--. 1 ovirt ovirt3 May 16 13:56 serial.txt.old /etc/pki/ovirt-engine/certs: total 100 -rw-r--r--. 1 root root 3362 May 16 13:56 01.pem -rw-r--r--. 1 root root 3509 May 16 13:56 02.pem -rw-r--r--. 1 root root 3466 May 16 13:56 03.pem -rw-r--r--. 1 root root 3466 May 16 13:56 04.pem -rw-r--r--. 1 root root 3362 May 16 13:56 05.pem -rw-r--r--. 1 root root 3509 May 16 13:56 06.pem -rw-r--r--. 1 root root 3362 May 16 13:56 07.pem -rw-r--r--. 1 root root 3509 May 16 13:56 08.pem -rw-r--r--. 1 root root 3466 May 16 13:56 09.pem -rw-r--r--. 1 root root 3467 May 16 13:56 0A.pem -rw-r--r--. 1 root root 3467 May 16 13:56 0B.pem -rw-r--r--. 1 root root 3467 May 16 13:56 0C.pem -rw-r--r--. 1 root root 3467 May 16 13:56 0D.pem -rw-r--r--. 1 root root 3070 May 16 13:56 0E.pem -rw-r--r--. 1 root root 3070 May 16 13:56 0F.pem -rw-r--r--. 1 root root 3070 May 16 13:56 10.251.193.8cert.pem -rw-r--r--. 1 root root 3070 May 16 13:56 10.251.193.9cert.pem these two are strange as I expect to be owned by ovirt user as engine created. -rw-r--r--. 1 root root 4267 May 22 20:07 10.pem -rw-r-. 1 root root 3509 May 16 13:56 apache.cer -rw-r--r--. 1 root root 763 May 16 13:56 ca.der -rw-r--r--. 1 root root 3509 May 16 13:56 engine.cer -rw-r--r--. 1 root root 784 May 16 13:56 engine.der -rw-r--r--. 1 root root 4267 May 22 20:07 websocket-proxy.cer /etc/pki/ovirt-engine/keys: total 36 -rw-r-. 1 root root 916 May 16 13:56 apache.key.nopass -rw-r-. 1 root root 2786 May 16 13:56 apache.p12 -rw---. 1 root root 1054 May 22 20:07 engine_id_rsa -rw---. 1 root root 916 May 16 13:56 engine_id_rsa.20140522200739 -rw---. 1 root root 912 May 16 13:56 engine_id_rsa.old -rw-r-. 1 ovirt ovirt 2786 May 16 13:56 engine.p12 -rw-r--r--. 1 root root 220 May 16 13:56 engine.ssh.key.txt -rw---. 1 ovirt ovirt 1832 May 22 20:07 websocket-proxy.key.nopass -rw---. 1 root root 2517 May 22 20:07 websocket-proxy.p12 /etc/pki/ovirt-engine/private: total 4 -rwxr-x---. 1 root root 887 May 16 13:56 ca.pem this should be owned by ovirt user and not be executable. /etc/pki/ovirt-engine/requests: total 24 -rw-r--r--. 1 root root 862 May 16 13:56 10.251.193.8req.pem -rw-r--r--. 1 ovirt ovirt 862 May 27 17:35 10.251.193.9.req -rw-r--r--. 1 root root 862 May 16 13:56 10.251.193.9req.pem -rw-r--r--. 1 root root 603 May 16 13:56 ca.csr -rw-r--r--. 1 root root 597 May 16 13:56 engine.req -rw-r--r--. 1 root root 863 May 22 20:07 websocket-proxy.req On Wed, May 28, 2014 at 8:19 AM, Alon Bar-Lev alo...@redhat.com wrote: Please send the output of: # ls -lR /etc/pki/ovirt-engine/ - Original Message - From: Neil nwilson...@gmail.com To: users@ovirt.org Sent: Wednesday, May 28, 2014 9:04:57 AM Subject: [ovirt-users] Can't Install/Upgrade host Hi guys, I'm trying to upgrade/re-install a host running Centos 6.5, but even after removing the host completely and trying to re-add it, I keep getting a Certificate
Re: [ovirt-users] Server 2012 R2 no drive found
Hi guys, Is anyone able to assist here? I still can't install 2012 R2, whether I use IDE, virtio, or virtio-scsi, I don't see a drive during the first install. I've tried the virtio-win-1.6.8/vioserial/2k12R2/amd64 as a test and this also doesn't work, so it doesn't seem like a driver issue, more of a cluster issue. I've also tried changing my Datacenter compatibility and Cluster to 3.4, but this seemed to make no difference. Both my hosts are upgraded to Centos 6.5 all updates, as well as my ovirt and VDSM is updated to the latest stable 3.4 packages. I'm at a loss here, but desperately need to get this R2 installed. Further to what Paul mentioned below, this was upgraded from 3.1 so it doesn't just appear to happen to new 3.4 installs. Any help is greatly appreciated. On Mon, May 26, 2014 at 12:45 PM, Neil nwilson...@gmail.com wrote: Hi guys, Thanks for the replies. What's strange is that even when choosing an IDE disk I don't see any hard drive showing up when I try to install 2012R2, is this normal? I can understand why R2 won't see the virtio scsi disk, but to me it should be showing up when using IDE, or am I wrong here? I see that in the virtio drivers from RHEL supplementary there is a folder virtio-win-1.6.8/vioserial/2k12R2/amd64 but the license seems to indicate that you need a valid subscription in order to use these drivers... if this is true then is no one using server 2012 R2 on oVirt without a valid subscription? I see with the drivers from http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/src/; there is only a Win8 driver, and trying to use this on my 2012 R2 doesn't find a matching driver. Can anyone clarify this from Redhat? If you using RHEV, presumably you can use R2, but it seems using oVirt you aren't allowed to? Thanks. Regards. Neil Wilson. On Fri, May 23, 2014 at 10:40 PM, Paul.LKW paul@gmail.com wrote: Hi guys: Please do not just say your one is working it is helpless in fact there already some guys reported issues in Win platform (including me) and there is no way to report that, do your think paid version in Redhat would be the same or the client will already fxxked. I noted this seems occured only in newly installed ovirt and old installation is fine. Paul.LKW 於 2014/5/23 下午11:02，Neil nwilson...@gmail.com 寫道： Hi guys, I've been trying to install 2012 R2 onto my ovirt 3.4 but no matter what I do, it either doesn't find an IDE drive or a Virtio drive (when using the virtio ISO). ovirt-engine-lib-3.4.0-1.el6.noarch ovirt-engine-restapi-3.4.0-1.el6.noarch ovirt-engine-setup-plugin-ovirt-engine-3.4.0-1.el6.noarch ovirt-engine-3.4.0-1.el6.noarch ovirt-engine-setup-plugin-websocket-proxy-3.4.0-1.el6.noarch ovirt-host-deploy-java-1.2.0-1.el6.noarch ovirt-engine-cli-3.2.0.10-1.el6.noarch ovirt-engine-setup-3.4.0-1.el6.noarch ovirt-host-deploy-1.2.0-1.el6.noarch ovirt-engine-backend-3.4.0-1.el6.noarch ovirt-image-uploader-3.4.0-1.el6.noarch ovirt-engine-tools-3.4.0-1.el6.noarch ovirt-engine-sdk-python-3.4.0.7-1.el6.noarch ovirt-engine-webadmin-portal-3.4.0-1.el6.noarch ovirt-engine-setup-base-3.4.0-1.el6.noarch ovirt-iso-uploader-3.4.0-1.el6.noarch ovirt-engine-userportal-3.4.0-1.el6.noarch ovirt-log-collector-3.4.1-1.el6.noarch ovirt-engine-websocket-proxy-3.4.0-1.el6.noarch ovirt-engine-setup-plugin-ovirt-engine-common-3.4.0-1.el6.noarch ovirt-engine-dbscripts-3.4.0-1.el6.noarch vdsm-4.14.6-0.el6.x86_64 vdsm-xmlrpc-4.14.6-0.el6.noarch vdsm-cli-4.14.6-0.el6.noarch vdsm-python-zombiereaper-4.14.6-0.el6.noarch vdsm-python-4.14.6-0.el6.x86_64 qemu-img-0.12.1.2-2.415.el6_5.8.x86_64 qemu-kvm-tools-0.12.1.2-2.415.el6_5.8.x86_64 qemu-kvm-0.12.1.2-2.415.el6_5.8.x86_64 gpxe-roms-qemu-0.9.7-6.9.el6.noarch Is there a special trick to get this working, or could something be wrong? When it comes to creating a guest I don't see a Server 2012 R2 64bit in the drop down list? Thanks. Regards. Neil Wilson. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] oVirt introduction slide in FUDConf APAC 2014 Beijing
Hi： Every oVirt users, Last weekend, I introduce oVirt in FUDConf APAC 2014 Beijing. all event is here: http://fedoraproject.org/wiki/FUDCon:Beijing_2014 I just upload my slide, URL: http://www.ovirt.org/File:OVirt-Overview-FUDCon2014.odp Feel free for this. -- 独立之思想，自由之精神。 --陈寅恪 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Nova- oVirt Driver : Adding NIC to VM
Hi All, I am working on Nova - oVirt driver. I was able to test the VM life cycle successfully - spawn, suspend, resume, shuttof, start and terminate. I am now exploring the Neutron integration in oVirt. I have imported the Network (Net1) form Openstack to oVirt. I get the below error when I try to add a NIC (for imported Net1) to the VM (created by Nova-oVirt driver), having the same MAC address which is assigned in Openstack (Port Details page). Error while executing action Add NIC to VM: Failed to communicate with the external provider. However, I am able to add a NIC with different MAC address. What changes needs to be done to add a NIC with MAC address as assigned by Neutron? Please suggest. I am using oVirt 3.4.0-1.fc19. Thank you. Regards, Udaya Kiran___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Nova- oVirt Driver : Adding NIC to VM
- Original Message - From: Udaya Kiran P ukiran...@yahoo.in To: users users@ovirt.org Sent: Wednesday, May 28, 2014 2:46:00 PM Subject: [ovirt-users] Nova- oVirt Driver : Adding NIC to VM Hi All, I am working on Nova - oVirt driver. I was able to test the VM life cycle successfully - spawn, suspend, resume, shuttof, start and terminate. I am now exploring the Neutron integration in oVirt. I have imported the Network (Net1) form Openstack to oVirt. I get the below error when I try to add a NIC (for imported Net1) to the VM (created by Nova-oVirt driver), having the same MAC address which is assigned in Openstack (Port Details page). Error while executing action Add NIC to VM: Failed to communicate with the external provider. However, I am able to add a NIC with different MAC address. What changes needs to be done to add a NIC with MAC address as assigned by Neutron? Please suggest. Could you attach the neutron server log (/etc/neutron/server.log) from the external network provider ? I am using oVirt 3.4.0-1.fc19. Thank you. Regards, Udaya Kiran ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] ovirt step by step support
Hi, I will keep in mind. Thanks you. Regards 2014-05-27 13:27 GMT+02:00 René Koch rk...@linuxland.at: On 05/26/2014 08:36 PM, JvR O wrote: Hi, Where can I get step by step support for installation and configuration of oVirt on my centos server? My company provides consulting for oVirt and RHEV and we help customers installing (and maintaining) their environment. We're located in Austria and Germany (but other countries are possible, too :) ). Any kind of support subscription? Sure - we can provide a support contract. Just drop me an email (off-list) if you're interested... -- Best Regards René Koch Senior Solution Architect LIS-Linuxland GmbH Brünner Straße 163, A-1210 Vienna Phone: +43 1 236 91 60 Mobile: +43 660 / 512 21 31 E-Mail: rk...@linuxland.at Regards. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Server 2012 R2 no drive found
Hi Neil, I'll test Windows Server 2012 R2 again with IDE and VirtIO disks (and e1000 and VirtIO network cards) with VirtIO-drivers from RHEL channel and drivers bundles with spice guest agent and will let you know the results. Please keep in mind that it will take some time... Btw, I will use Windows 2012 R2 english, 180-days trial... Regards, René On 05/28/2014 01:11 PM, Neil wrote: Hi guys, Is anyone able to assist here? I still can't install 2012 R2, whether I use IDE, virtio, or virtio-scsi, I don't see a drive during the first install. I've tried the virtio-win-1.6.8/vioserial/2k12R2/amd64 as a test and this also doesn't work, so it doesn't seem like a driver issue, more of a cluster issue. I've also tried changing my Datacenter compatibility and Cluster to 3.4, but this seemed to make no difference. Both my hosts are upgraded to Centos 6.5 all updates, as well as my ovirt and VDSM is updated to the latest stable 3.4 packages. I'm at a loss here, but desperately need to get this R2 installed. Further to what Paul mentioned below, this was upgraded from 3.1 so it doesn't just appear to happen to new 3.4 installs. Any help is greatly appreciated. On Mon, May 26, 2014 at 12:45 PM, Neil nwilson...@gmail.com wrote: Hi guys, Thanks for the replies. What's strange is that even when choosing an IDE disk I don't see any hard drive showing up when I try to install 2012R2, is this normal? I can understand why R2 won't see the virtio scsi disk, but to me it should be showing up when using IDE, or am I wrong here? I see that in the virtio drivers from RHEL supplementary there is a folder virtio-win-1.6.8/vioserial/2k12R2/amd64 but the license seems to indicate that you need a valid subscription in order to use these drivers... if this is true then is no one using server 2012 R2 on oVirt without a valid subscription? I see with the drivers from http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/src/; there is only a Win8 driver, and trying to use this on my 2012 R2 doesn't find a matching driver. Can anyone clarify this from Redhat? If you using RHEV, presumably you can use R2, but it seems using oVirt you aren't allowed to? Thanks. Regards. Neil Wilson. On Fri, May 23, 2014 at 10:40 PM, Paul.LKW paul@gmail.com wrote: Hi guys: Please do not just say your one is working it is helpless in fact there already some guys reported issues in Win platform (including me) and there is no way to report that, do your think paid version in Redhat would be the same or the client will already fxxked. I noted this seems occured only in newly installed ovirt and old installation is fine. Paul.LKW 於 2014/5/23 下午11:02，Neil nwilson...@gmail.com 寫道： Hi guys, I've been trying to install 2012 R2 onto my ovirt 3.4 but no matter what I do, it either doesn't find an IDE drive or a Virtio drive (when using the virtio ISO). ovirt-engine-lib-3.4.0-1.el6.noarch ovirt-engine-restapi-3.4.0-1.el6.noarch ovirt-engine-setup-plugin-ovirt-engine-3.4.0-1.el6.noarch ovirt-engine-3.4.0-1.el6.noarch ovirt-engine-setup-plugin-websocket-proxy-3.4.0-1.el6.noarch ovirt-host-deploy-java-1.2.0-1.el6.noarch ovirt-engine-cli-3.2.0.10-1.el6.noarch ovirt-engine-setup-3.4.0-1.el6.noarch ovirt-host-deploy-1.2.0-1.el6.noarch ovirt-engine-backend-3.4.0-1.el6.noarch ovirt-image-uploader-3.4.0-1.el6.noarch ovirt-engine-tools-3.4.0-1.el6.noarch ovirt-engine-sdk-python-3.4.0.7-1.el6.noarch ovirt-engine-webadmin-portal-3.4.0-1.el6.noarch ovirt-engine-setup-base-3.4.0-1.el6.noarch ovirt-iso-uploader-3.4.0-1.el6.noarch ovirt-engine-userportal-3.4.0-1.el6.noarch ovirt-log-collector-3.4.1-1.el6.noarch ovirt-engine-websocket-proxy-3.4.0-1.el6.noarch ovirt-engine-setup-plugin-ovirt-engine-common-3.4.0-1.el6.noarch ovirt-engine-dbscripts-3.4.0-1.el6.noarch vdsm-4.14.6-0.el6.x86_64 vdsm-xmlrpc-4.14.6-0.el6.noarch vdsm-cli-4.14.6-0.el6.noarch vdsm-python-zombiereaper-4.14.6-0.el6.noarch vdsm-python-4.14.6-0.el6.x86_64 qemu-img-0.12.1.2-2.415.el6_5.8.x86_64 qemu-kvm-tools-0.12.1.2-2.415.el6_5.8.x86_64 qemu-kvm-0.12.1.2-2.415.el6_5.8.x86_64 gpxe-roms-qemu-0.9.7-6.9.el6.noarch Is there a special trick to get this working, or could something be wrong? When it comes to creating a guest I don't see a Server 2012 R2 64bit in the drop down list? Thanks. Regards. Neil Wilson. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Server 2012 R2 no drive found
Thank you Rene, greatly appreciated. I'm using the Server 2012 R2 Standard edition and at this point I haven't even got a NIC added to the VM. Another piece of info which might be useful (or not) is I'm using a FC SAN for storage, not sure if this would have any affect. Thanks. Regards. Neil Wilson. On Wed, May 28, 2014 at 2:42 PM, René Koch rk...@linuxland.at wrote: Hi Neil, I'll test Windows Server 2012 R2 again with IDE and VirtIO disks (and e1000 and VirtIO network cards) with VirtIO-drivers from RHEL channel and drivers bundles with spice guest agent and will let you know the results. Please keep in mind that it will take some time... Btw, I will use Windows 2012 R2 english, 180-days trial... Regards, René On 05/28/2014 01:11 PM, Neil wrote: Hi guys, Is anyone able to assist here? I still can't install 2012 R2, whether I use IDE, virtio, or virtio-scsi, I don't see a drive during the first install. I've tried the virtio-win-1.6.8/vioserial/2k12R2/amd64 as a test and this also doesn't work, so it doesn't seem like a driver issue, more of a cluster issue. I've also tried changing my Datacenter compatibility and Cluster to 3.4, but this seemed to make no difference. Both my hosts are upgraded to Centos 6.5 all updates, as well as my ovirt and VDSM is updated to the latest stable 3.4 packages. I'm at a loss here, but desperately need to get this R2 installed. Further to what Paul mentioned below, this was upgraded from 3.1 so it doesn't just appear to happen to new 3.4 installs. Any help is greatly appreciated. On Mon, May 26, 2014 at 12:45 PM, Neil nwilson...@gmail.com wrote: Hi guys, Thanks for the replies. What's strange is that even when choosing an IDE disk I don't see any hard drive showing up when I try to install 2012R2, is this normal? I can understand why R2 won't see the virtio scsi disk, but to me it should be showing up when using IDE, or am I wrong here? I see that in the virtio drivers from RHEL supplementary there is a folder virtio-win-1.6.8/vioserial/2k12R2/amd64 but the license seems to indicate that you need a valid subscription in order to use these drivers... if this is true then is no one using server 2012 R2 on oVirt without a valid subscription? I see with the drivers from http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/src/; there is only a Win8 driver, and trying to use this on my 2012 R2 doesn't find a matching driver. Can anyone clarify this from Redhat? If you using RHEV, presumably you can use R2, but it seems using oVirt you aren't allowed to? Thanks. Regards. Neil Wilson. On Fri, May 23, 2014 at 10:40 PM, Paul.LKW paul@gmail.com wrote: Hi guys: Please do not just say your one is working it is helpless in fact there already some guys reported issues in Win platform (including me) and there is no way to report that, do your think paid version in Redhat would be the same or the client will already fxxked. I noted this seems occured only in newly installed ovirt and old installation is fine. Paul.LKW 於 2014/5/23 下午11:02，Neil nwilson...@gmail.com 寫道： Hi guys, I've been trying to install 2012 R2 onto my ovirt 3.4 but no matter what I do, it either doesn't find an IDE drive or a Virtio drive (when using the virtio ISO). ovirt-engine-lib-3.4.0-1.el6.noarch ovirt-engine-restapi-3.4.0-1.el6.noarch ovirt-engine-setup-plugin-ovirt-engine-3.4.0-1.el6.noarch ovirt-engine-3.4.0-1.el6.noarch ovirt-engine-setup-plugin-websocket-proxy-3.4.0-1.el6.noarch ovirt-host-deploy-java-1.2.0-1.el6.noarch ovirt-engine-cli-3.2.0.10-1.el6.noarch ovirt-engine-setup-3.4.0-1.el6.noarch ovirt-host-deploy-1.2.0-1.el6.noarch ovirt-engine-backend-3.4.0-1.el6.noarch ovirt-image-uploader-3.4.0-1.el6.noarch ovirt-engine-tools-3.4.0-1.el6.noarch ovirt-engine-sdk-python-3.4.0.7-1.el6.noarch ovirt-engine-webadmin-portal-3.4.0-1.el6.noarch ovirt-engine-setup-base-3.4.0-1.el6.noarch ovirt-iso-uploader-3.4.0-1.el6.noarch ovirt-engine-userportal-3.4.0-1.el6.noarch ovirt-log-collector-3.4.1-1.el6.noarch ovirt-engine-websocket-proxy-3.4.0-1.el6.noarch ovirt-engine-setup-plugin-ovirt-engine-common-3.4.0-1.el6.noarch ovirt-engine-dbscripts-3.4.0-1.el6.noarch vdsm-4.14.6-0.el6.x86_64 vdsm-xmlrpc-4.14.6-0.el6.noarch vdsm-cli-4.14.6-0.el6.noarch vdsm-python-zombiereaper-4.14.6-0.el6.noarch vdsm-python-4.14.6-0.el6.x86_64 qemu-img-0.12.1.2-2.415.el6_5.8.x86_64 qemu-kvm-tools-0.12.1.2-2.415.el6_5.8.x86_64 qemu-kvm-0.12.1.2-2.415.el6_5.8.x86_64 gpxe-roms-qemu-0.9.7-6.9.el6.noarch Is there a special trick to get this working, or could something be wrong? When it comes to creating a guest I don't see a Server 2012 R2 64bit in the drop down list? Thanks. Regards. Neil Wilson. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing
Re: [ovirt-users] Persisting glusterfs configs on an oVirt node
Thanks for the replies. I cannot get glusterd to start on boot and I lose all gluster config every reboot. The following shows what I did on the node to start glusterd, create a volume etc, followed by the state of the node after a reboot. [root@ovirt_node]# service glusterd status glusterd is stopped [root@ovirt_node]# chkconfig --list glusterd glusterd0:off 1:off 2:off 3:off 4:off 5:off 6:off [root@ovirt_node]# service glusterd start Starting glusterd:[ OK ] gluster volume create vmstore 10.22.8.46:/data/glusterfs/vmstore volume create: vmstore: success: please start the volume to access data gluster vol start vmstore volume start: vmstore: success gluster vol info Volume Name: vmstore Type: Distribute Volume ID: 5bd01043-1352-4014-88ca-e632e264d088 Status: Started Number of Bricks: 1 Transport-type: tcp Bricks: Brick1: 10.22.8.46:/data/glusterfs/vmstore [root@ovirt_node]# ls -1 /var/lib/glusterd/vols/vmstore/ bricks node_state.info trusted-vmstore-fuse.vol cksum rbstate vmstore.10.22.8.46.data-glusterfs-vmstore.vol info run vmstore-fuse.vol [root@ovirt_node]# grep gluster /etc/rwtab.d/* /etc/rwtab.d/ovirt:files /var/lib/glusterd [root@ovirt_node]# chkconfig glusterd on [root@ovirt_node]# chkconfig --list glusterd glusterd0:off 1:off 2:on3:on4:on5:on6:off I then reboot the node and see the following: [root@ovirt_node]# service glusterd status glusterd is stopped [root@ovirt_node]# chkconfig --list glusterd glusterd0:off 1:off 2:off 3:off 4:off 5:off 6:off [root@ovirt_node]# ls -l /var/lib/glusterd/vols/ total 0 No more gluster volume configuration files. I've taken a look through http://www.ovirt.org/Node_Troubleshooting#Making_changes_last_.2F_Persisting_changes but I'm unsure what needs to be done to persist this configuration. To get glusterd to start on boot, do I need to manually persist /etc/rc* files? I see files /var/lib/glusterd mentioned in /etc/rwtab.d/ovirt. Is this a list of the files/dirs that should be persisted automatically? If so, is it recursive and should it include everything in /var/lib/glusterd/vols? TIA for any help with this. Simon -Original Message- From: Ryan Barry [mailto:rba...@redhat.com] Sent: 27 May 2014 14:01 To: Fabian Deutsch; Doron Fediuck; Simon Barrett Cc: users@ovirt.org Subject: Re: [ovirt-users] Persisting glusterfs configs on an oVirt node On 05/26/2014 04:14 AM, Fabian Deutsch wrote: Am Sonntag, den 25.05.2014, 08:18 -0400 schrieb Doron Fediuck: - Original Message - From: Simon Barrett simon.barr...@tradingscreen.com To: users@ovirt.org Sent: Friday, May 23, 2014 11:29:39 AM Subject: [ovirt-users] Persisting glusterfs configs on an oVirt node I am working through the setup of oVirt node for a 3.4.1 deployment. I setup some glusterfs volumes/bricks on oVirt Node Hypervisor release 3.0.4 (1.0.201401291204.el6) and created a storage domain. All was working OK until I rebooted the node and found that the glusterfs configuration had not been retained. Is there something I should be doing to persist any glusterfs configuration so it survives a node reboot? Many thanks, Simon Hi Simon, it actually sounds like a bug to me, as node are supposed to support gluster. Ryan / Fabian- thoughts? Hey, I vaguely remember that we were seeing a bug like this some time ago. We fixed /var/lib/glusterd to be writable (using tmpfs), but it can actually be that we need to persist those contents. But Simon, can you give details which configuration files are missing and why glusterd is not starting? Is glusterd starting? I'm getting the impression that it's starting, but that it has no configuration. As far as I know, Gluster keeps most of the configuration on the brick itself, but it finds brick information in /var/lib/glusterd. The last patch simply opened the firewall, and it's entirely possible that we need to persist this. It may be a good idea to just persist the entire directory from the get-go, unless we want to try to have a thread watching /var/lib/glusterd for relevant files, but then we're stuck trying to keep up with what's happening with gluster itself... Can we Thanks fabian Either way I suggest you take a look in the below link- http://www.ovirt.org/Node_Troubleshooting#Making_changes_last_.2F_Per sisting_changes Let s know how it works. Doron ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] ovirt step by step support
Don't know if you can use this, but I created a short installation guide for my work once: Install oVirt Engine oVirt Engine is the control center of the oVirt environment. It allows you to define hosts, configure data centers, add storage, define networks, create virtual machines, manage user permissions and use templates from one central location. update all the packages on it. Run: yum -y update Reboot your server for the updates to be applied. Add the oVirt repo: vim /etc/yum.repos.d/el6-ovirt.repo •copy/paste: [ovirt-stable] name=Stable builds of the oVirt project baseurl=http://ovirt.org/releases/stable/rpm/EL/$releasever/ enabled=1 skip_if_unavailable=1 gpgcheck=0 [ovirt-updates-testing] name=Stable builds of the oVirt project baseurl=http://ovirt.org/releases/updates-testing/rpm/EL/$releasever/ enabled=0 skip_if_unavailable=1 gpgcheck=0 [ovirt-beta] name=Beta builds of the oVirt project baseurl=http://ovirt.org/releases/beta/rpm/EL/$releasever/ enabled=0 skip_if_unavailable=1 gpgcheck=0 [ovirt-nightly] name=Nightly builds of the oVirt project baseurl=http://ovirt.org/releases/nightly/rpm/EL/$releasever/ enabled=0 skip_if_unavailable=1 gpgcheck=0 You are now ready to install the oVirt Engine. Run the following command: yum -y install ovirt-engine This command will download the oVirt Engine installation software and resolve all dependencies. When the packages have finished downloading, run the installer: engine-setup Answer the following questions (Normally default is OK): •Host fully qualified DNS name of this server [localhost.localdomain]: •Where is the database located? (Local, Remote) [Local]: •Would you like Setup to automatically configure postgresql, or prefer to perform that manually? (Automatic, Manual) [Automatic]: •Engine admin password: Confirm engine admin password: •Application mode (Both, Virt, Gluster) [Both]: •Default storage type: (NFS, FC, ISCSI, POSIXFS) [NFS]: •Organization name for certificate [localdomain]: •Setup can configure the default page of the web server to present the application home page. This may conflict with existing applications. Do you wish to set the application as the default page of the web server? (Yes, No) [Yes]: •Configure an NFS share on this server to be used as an ISO Domain? (Yes, No) [Yes]: •Local ISO domain path [/var/lib/exports/iso]: •Local ISO domain name [ISO_DOMAIN]: Your oVirt Engine is now up and running. You can log in to the oVirt Engine's web administration portal with the username admin (the administrative user configured during installation) in the internal domain 2014-05-28 14:31 GMT+02:00 JvR O jvr...@gmail.com: Hi, I will keep in mind. Thanks you. Regards 2014-05-27 13:27 GMT+02:00 René Koch rk...@linuxland.at: On 05/26/2014 08:36 PM, JvR O wrote: Hi, Where can I get step by step support for installation and configuration of oVirt on my centos server? My company provides consulting for oVirt and RHEV and we help customers installing (and maintaining) their environment. We're located in Austria and Germany (but other countries are possible, too :) ). Any kind of support subscription? Sure - we can provide a support contract. Just drop me an email (off-list) if you're interested... -- Best Regards René Koch Senior Solution Architect LIS-Linuxland GmbH Brünner Straße 163, A-1210 Vienna Phone: +43 1 236 91 60 Mobile: +43 660 / 512 21 31 E-Mail: rk...@linuxland.at Regards. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Removing VM disk issue
We have this same issue also once in a while. Most of the times it is solved by just restarting the ovirt engine. If this doesn't work, try to restart your vdsm service. Kind regards 2014-05-26 10:07 GMT+02:00 Maor Lipchuk mlipc...@redhat.com: On 05/19/2014 05:57 PM, Neil wrote: Hi Maor, Sorry for the late reply. Unfortunately I don't have much in the way of older logs, but can confirm that the VM has been shutdown for about 3 months so there really shouldn't be any tasks running. My version is ovirt-engine-3.3.3-2.el6.noarch I presume running the command won't have any affect on any other VM's so it should be safe to do this? hi Neil, The command should not affect other VMs (Make sure to run the command with vm_names ='proxy02'). Just to be sure use SELECT before running the command to check that only one image is returned: SELECT * FROM images where image_guid = (SELECT image_guid from all_disks where disk_alias = 'proxy02_Disk0' and vm_names ='proxy02'); Thank you! Regards. Neil Wilson. On Thu, May 15, 2014 at 11:52 AM, Maor Lipchuk mlipc...@redhat.com wrote: Hi Neil, I have been looking at your logs but it seems that there is no indication of any operation being done on this specific disk. I also see that there are no running tasks in VDSM, so the disk should not be locked. If you have any older engine logs please send them so we can investigate the problem more better. What is the engine version you are running? If you want to unlock the disk, you can run this query in your postgres: UPDATE images set imagestatus = 1 where image_guid = (SELECT image_guid from all_disks where disk_alias = 'proxy02_Disk0' and vm_names ='proxy02'); regards, Maor On 05/14/2014 05:30 PM, Neil wrote: Hi Maor, Attached are the logs, and below is a screenshot of the event log, I removed the two disks that were attached to the proxy previously which completed. Thank you! Regards. Neil Wilson. On Wed, May 14, 2014 at 2:43 PM, Maor Lipchuk mlipc...@redhat.com wrote: Hi Neil, Can u please attach the logs of engine and VDSM. What there is in the event log, was there any operation being done on the disk before? regards, Maor On 05/14/2014 03:35 PM, Neil wrote: Hi guys, I'm trying to remove a VM and reclaim the space that the VM was using. This particular VM had a thin provisioned disk attached as well as fat provisioned, the fat disks I managed to detach, however when I try to remove the VM, it says The following disks are locked: Please try again in a few minutes. Attached is a screenshot from the GUI side, showing the proxy disk being locked, any ideas? I'm wanting to completely remove the VM and reclaim the space for the datacenter. Thank you. Regards. Neil Wilson ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Removing VM disk issue (Solved)
Thanks Maor and Koen, Koen: I tried the engine restart and vdsm restart, but that didn't work unfortunately. Maor: I ran... psql -U postgres engine then... UPDATE images set imagestatus = 1 where image_guid = (SELECT image_guid from all_disks where disk_alias = 'proxy02_Disk0' and vm_names ='proxy02'); UPDATE 1 This then unlocked the disk and it allowed me to remove the entire VM and disk thereafter. Thank you very much for your assistance. Kind regard. Neil Wilson. On Wed, May 28, 2014 at 3:18 PM, Koen Vanoppen vanoppen.k...@gmail.com wrote: We have this same issue also once in a while. Most of the times it is solved by just restarting the ovirt engine. If this doesn't work, try to restart your vdsm service. Kind regards 2014-05-26 10:07 GMT+02:00 Maor Lipchuk mlipc...@redhat.com: On 05/19/2014 05:57 PM, Neil wrote: Hi Maor, Sorry for the late reply. Unfortunately I don't have much in the way of older logs, but can confirm that the VM has been shutdown for about 3 months so there really shouldn't be any tasks running. My version is ovirt-engine-3.3.3-2.el6.noarch I presume running the command won't have any affect on any other VM's so it should be safe to do this? hi Neil, The command should not affect other VMs (Make sure to run the command with vm_names ='proxy02'). Just to be sure use SELECT before running the command to check that only one image is returned: SELECT * FROM images where image_guid = (SELECT image_guid from all_disks where disk_alias = 'proxy02_Disk0' and vm_names ='proxy02'); Thank you! Regards. Neil Wilson. On Thu, May 15, 2014 at 11:52 AM, Maor Lipchuk mlipc...@redhat.com wrote: Hi Neil, I have been looking at your logs but it seems that there is no indication of any operation being done on this specific disk. I also see that there are no running tasks in VDSM, so the disk should not be locked. If you have any older engine logs please send them so we can investigate the problem more better. What is the engine version you are running? If you want to unlock the disk, you can run this query in your postgres: UPDATE images set imagestatus = 1 where image_guid = (SELECT image_guid from all_disks where disk_alias = 'proxy02_Disk0' and vm_names ='proxy02'); regards, Maor On 05/14/2014 05:30 PM, Neil wrote: Hi Maor, Attached are the logs, and below is a screenshot of the event log, I removed the two disks that were attached to the proxy previously which completed. Thank you! Regards. Neil Wilson. On Wed, May 14, 2014 at 2:43 PM, Maor Lipchuk mlipc...@redhat.com wrote: Hi Neil, Can u please attach the logs of engine and VDSM. What there is in the event log, was there any operation being done on the disk before? regards, Maor On 05/14/2014 03:35 PM, Neil wrote: Hi guys, I'm trying to remove a VM and reclaim the space that the VM was using. This particular VM had a thin provisioned disk attached as well as fat provisioned, the fat disks I managed to detach, however when I try to remove the VM, it says The following disks are locked: Please try again in a few minutes. Attached is a screenshot from the GUI side, showing the proxy disk being locked, any ideas? I'm wanting to completely remove the VM and reclaim the space for the datacenter. Thank you. Regards. Neil Wilson ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Persisting glusterfs configs on an oVirt node
I did a persist /var/lib/glusterd and things are looking better. The gluster config is now still in place after a reboot. As a workaround to getting glusterd running on boot, I added service glusterd start to /etc/rc.local and ran persist /etc/rc.local. It appears to be working but feels like a bit of a hack. Does anyone have any other suggestions as to the correct way to do this? Thanks, Simon -Original Message- From: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On Behalf Of Simon Barrett Sent: 28 May 2014 14:12 To: Ryan Barry; Fabian Deutsch; Doron Fediuck Cc: users@ovirt.org Subject: Re: [ovirt-users] Persisting glusterfs configs on an oVirt node Thanks for the replies. I cannot get glusterd to start on boot and I lose all gluster config every reboot. The following shows what I did on the node to start glusterd, create a volume etc, followed by the state of the node after a reboot. [root@ovirt_node]# service glusterd status glusterd is stopped [root@ovirt_node]# chkconfig --list glusterd glusterd0:off 1:off 2:off 3:off 4:off 5:off 6:off [root@ovirt_node]# service glusterd start Starting glusterd:[ OK ] gluster volume create vmstore 10.22.8.46:/data/glusterfs/vmstore volume create: vmstore: success: please start the volume to access data gluster vol start vmstore volume start: vmstore: success gluster vol info Volume Name: vmstore Type: Distribute Volume ID: 5bd01043-1352-4014-88ca-e632e264d088 Status: Started Number of Bricks: 1 Transport-type: tcp Bricks: Brick1: 10.22.8.46:/data/glusterfs/vmstore [root@ovirt_node]# ls -1 /var/lib/glusterd/vols/vmstore/ bricks node_state.info trusted-vmstore-fuse.vol cksum rbstate vmstore.10.22.8.46.data-glusterfs-vmstore.vol info run vmstore-fuse.vol [root@ovirt_node]# grep gluster /etc/rwtab.d/* /etc/rwtab.d/ovirt:files /var/lib/glusterd [root@ovirt_node]# chkconfig glusterd on [root@ovirt_node]# chkconfig --list glusterd glusterd0:off 1:off 2:on3:on4:on5:on6:off I then reboot the node and see the following: [root@ovirt_node]# service glusterd status glusterd is stopped [root@ovirt_node]# chkconfig --list glusterd glusterd0:off 1:off 2:off 3:off 4:off 5:off 6:off [root@ovirt_node]# ls -l /var/lib/glusterd/vols/ total 0 No more gluster volume configuration files. I've taken a look through http://www.ovirt.org/Node_Troubleshooting#Making_changes_last_.2F_Persisting_changes but I'm unsure what needs to be done to persist this configuration. To get glusterd to start on boot, do I need to manually persist /etc/rc* files? I see files /var/lib/glusterd mentioned in /etc/rwtab.d/ovirt. Is this a list of the files/dirs that should be persisted automatically? If so, is it recursive and should it include everything in /var/lib/glusterd/vols? TIA for any help with this. Simon -Original Message- From: Ryan Barry [mailto:rba...@redhat.com] Sent: 27 May 2014 14:01 To: Fabian Deutsch; Doron Fediuck; Simon Barrett Cc: users@ovirt.org Subject: Re: [ovirt-users] Persisting glusterfs configs on an oVirt node On 05/26/2014 04:14 AM, Fabian Deutsch wrote: Am Sonntag, den 25.05.2014, 08:18 -0400 schrieb Doron Fediuck: - Original Message - From: Simon Barrett simon.barr...@tradingscreen.com To: users@ovirt.org Sent: Friday, May 23, 2014 11:29:39 AM Subject: [ovirt-users] Persisting glusterfs configs on an oVirt node I am working through the setup of oVirt node for a 3.4.1 deployment. I setup some glusterfs volumes/bricks on oVirt Node Hypervisor release 3.0.4 (1.0.201401291204.el6) and created a storage domain. All was working OK until I rebooted the node and found that the glusterfs configuration had not been retained. Is there something I should be doing to persist any glusterfs configuration so it survives a node reboot? Many thanks, Simon Hi Simon, it actually sounds like a bug to me, as node are supposed to support gluster. Ryan / Fabian- thoughts? Hey, I vaguely remember that we were seeing a bug like this some time ago. We fixed /var/lib/glusterd to be writable (using tmpfs), but it can actually be that we need to persist those contents. But Simon, can you give details which configuration files are missing and why glusterd is not starting? Is glusterd starting? I'm getting the impression that it's starting, but that it has no configuration. As far as I know, Gluster keeps most of the configuration on the brick itself, but it finds brick information in /var/lib/glusterd. The last patch simply opened the firewall, and it's entirely possible that we need to persist this. It may be a good idea to just persist the entire directory from the get-go, unless we want to try to have a thread watching /var/lib/glusterd for relevant files, but then we're stuck trying to keep up
Re: [ovirt-users] [ovirt-devel] [QE][ACTION NEEDED] oVirt 3.5.0 Second Alpha status
- Original Message - From: Sandro Bonazzola sbona...@redhat.com To: users users@ovirt.org, de...@ovirt.org Sent: Wednesday, May 28, 2014 10:13:06 AM Subject: [ovirt-devel] [QE][ACTION NEEDED] oVirt 3.5.0 Second Alpha status Hi, We're preparing for feature freeze scheduled for 2014-05-30. We're going to compose a Second Alpha on Firday *2014-05-30 08:00 UTC*. Maintainers: - Please be sure that master snapshot allow to create VMs before *2014-05-29 15:00 UTC* Hi Sandro, oVirt RESTful API project's main maintainer is not available, and will be back (I think) on Monday (6/2). I personally have 2 pending long going major issues that awaits for him (ack merge) for coming feature freeze. I want my features to slip in 3.5 without breaking any rules, ideas? Thanks, Gilad. The bug tracker [1] shows the following proposed blockers to be reviewed: Bug IDWhiteboard Status Summary 1001100 integration NEW Add log gathering for a new ovirt module (External scheduler) 1073944 integration ASSIGNEDAdd log gathering for a new ovirt module (External scheduler) 1060198 integration NEW [RFE] add support for Fedora 20 1100236 integration NEW all-in-one setup should configure cluster compatibility as max common between vdsm and engine Feature freeze has been postponed to 2014-05-30 and the following features should be testable in 3.5.0 Alpha according to Features Status Table [2] Group oVirt BZTitle gluster 1096713 Monitoring (UI plugin) Dashboard (Integrated with Nagios monitoring) infra 1090530 [RFE] Please add host count and guest count columns to Clusters tab in webadmin infra 1078738 [RFE] make ovirt easy configurable to allow redirection of all logs to syslog infra 1054778 [RFE] Allow to perform fence operations from a host in another DC infra 1090803 [RFE] Change the Slot field to Service Profile when cisco_ucs is selected as the fencing type infra 1090511 [RFE] Improve fencing robustness by retrying failed attempts infra 1090800 [RFE] Add periodic power management health check to detect/warn about link-down detection of power management LAN infra 1090794 [RFE] Search VMs based on MAC address from web-admin portal infra 1090793 consider the event type while printing events to engine.log infra 1090796 [RFE] Re-work engine ovirt-node host-deploy sequence infra 1090798 [RFE] Admin GUI - Add host uptime information to the General tab infra 1090808 [RFE] Ability to dismiss alerts and events from web-admin portal infra 1058737 [RFE] Restart HA VMs ASAP infra-api 1090797 [RFE] RESTAPI: Add /tags sub-collection for Template resource infra-dwh 1091686 prevent OutOfMemoryError after starting the dwh service. infra-dwh 1091687 History DB should sync user's first and last name for user usage tables network 1078836 Add a warning when adding display network network 1079719 Display of NIC Slave/Bond fault on Event Log network 1080984 Support bridging_opts functionality within oVirt network 1080987 Support ethtool_opts functionality within oVirt network 1078862 Providing Neutron Applience storage Store OVF on any domains storage 1083312 Disk alias recycling in web-admin portal storage 1086181 [RFE] Snapshot overview in webadmin portal ux1064543 oVirt new look and feel [PatternFly adoption] - phase #1 virt 1058832 Allow to clone a (down) VM without snapshot/template virt 1031040 can't set different keymap for vnc via runonce option virt 1043471 oVirt guest agent for SLES virt 1073453 Debian 7 support (incl. 1043474 oVirt guest agent for Debian) virt 1072313 Edit Running Vm virt 1083049 add progress bar for vm migration virt 1083065 EL 7 guest compatibility virt Allow guest serial number to be configurable virt 1047624 [RFE] support BIOS boot device menu virt 1083129 allows setting netbios name, locale, language and keyboard settings for windows vm's virt 1038632 spice-html5 button to show debug console/output window virt 1080002 [RFE] Enable user defined Windows Sysprep file Some more features may be included since they were near to be completed on last sync meeting. The table will be updated on next
Re: [ovirt-users] post glusterfs 3.4 - 3.5 upgrade issue in ovirt (3.4.0-1.fc19): bricks unavailable
Hi Alastair,
This could be a mismatch in the hostname identified in ovirt and gluster.
You could check for any exceptions from GlusterSyncJob in engine.log.
Also, what version of ovirt are you using. And the compatibility version
of your cluster?
On 05/28/2014 12:40 AM, Alastair Neil wrote:
Hi thanks for the reply. Here is an extract from a grep I ran on the
vdsm log grepping for the volume name vm-store. It seems to indicate
the bricks are ONLINE.
I am uncertain how to extract meaningful information from the
engine.log can you provide some guidance?
Thanks,
Alastair
Thread-100::DEBUG::2014-05-27
15:01:06,335::BindingXMLRPC::1067::vds::(wrapper) client
[129.174.94.239]::call volumeStatus with ('vm-store', '', '') {}
Thread-100::DEBUG::2014-05-27
15:01:06,356::BindingXMLRPC::1074::vds::(wrapper) return
volumeStatus with {'volumeStatus': {'bricks': [{'status':
'ONLINE', 'brick': 'gluster0:/export/brick0', 'pid': '2675',
'port': '49158', 'hostuuid':
'bcff5245-ea86-4384-a1bf-9219c8be8001'}, {'status': 'ONLINE',
'brick': 'gluster1:/export/brick4/vm-store', 'pid': '2309',
'port': '49158', 'hostuuid':
'54d39ae4-91ae-410b-828c-67031f3d8a68'}], 'nfs': [{'status':
'ONLINE', 'hostname': '129.174.126.56', 'pid': '27012', 'port':
'2049', 'hostuuid': '54d39ae4-91ae-410b-828c-67031f3d8a68'},
{'status': 'ONLINE', 'hostname': 'gluster0', 'pid': '12875',
'port': '2049', 'hostuuid':
'bcff5245-ea86-4384-a1bf-9219c8be8001'}], 'shd': [{'status':
'ONLINE', 'hostname': '129.174.126.56', 'pid': '27019',
'hostuuid': '54d39ae4-91ae-410b-828c-67031f3d8a68'}, {'status':
'ONLINE', 'hostname': 'gluster0', 'pid': '12882', 'hostuuid':
'bcff5245-ea86-4384-a1bf-9219c8be8001'}], 'name': 'vm-store'},
'status': {'message': 'Done', 'code': 0}}
Thread-16::DEBUG::2014-05-27
15:01:15,339::fileSD::225::Storage.Misc.excCmd::(getReadDelay)
'/bin/dd iflag=direct
if=/rhev/data-center/mnt/glusterSD/gluster0:vm-store/6d637c7f-a4ab-4510-a0d9-63a04c55d6d8/dom_md/metadata
bs=4096 count=1' (cwd None)
Thread-16::DEBUG::2014-05-27
15:01:25,381::fileSD::225::Storage.Misc.excCmd::(getReadDelay)
'/bin/dd iflag=direct
if=/rhev/data-center/mnt/glusterSD/gluster0:vm-store/6d637c7f-a4ab-4510-a0d9-63a04c55d6d8/dom_md/metadata
bs=4096 count=1' (cwd None)
Thread-16::DEBUG::2014-05-27
15:01:35,423::fileSD::225::Storage.Misc.excCmd::(getReadDelay)
'/bin/dd iflag=direct
if=/rhev/data-center/mnt/glusterSD/gluster0:vm-store/6d637c7f-a4ab-4510-a0d9-63a04c55d6d8/dom_md/metadata
bs=4096 count=1' (cwd None)
Thread-16::DEBUG::2014-05-27
15:01:45,465::fileSD::225::Storage.Misc.excCmd::(getReadDelay)
'/bin/dd iflag=direct
if=/rhev/data-center/mnt/glusterSD/gluster0:vm-store/6d637c7f-a4ab-4510-a0d9-63a04c55d6d8/dom_md/metadata
bs=4096 count=1' (cwd None)
Thread-16::DEBUG::2014-05-27
15:01:55,507::fileSD::225::Storage.Misc.excCmd::(getReadDelay)
'/bin/dd iflag=direct
if=/rhev/data-center/mnt/glusterSD/gluster0:vm-store/6d637c7f-a4ab-4510-a0d9-63a04c55d6d8/dom_md/metadata
bs=4096 count=1' (cwd None)
Thread-16::DEBUG::2014-05-27
15:02:05,549::fileSD::225::Storage.Misc.excCmd::(getReadDelay)
'/bin/dd iflag=direct
if=/rhev/data-center/mnt/glusterSD/gluster0:vm-store/6d637c7f-a4ab-4510-a0d9-63a04c55d6d8/dom_md/metadata
bs=4096 count=1' (cwd None)
Thread-16::DEBUG::2014-05-27
15:02:15,590::fileSD::225::Storage.Misc.excCmd::(getReadDelay)
'/bin/dd iflag=direct
if=/rhev/data-center/mnt/glusterSD/gluster0:vm-store/6d637c7f-a4ab-4510-a0d9-63a04c55d6d8/dom_md/metadata
bs=4096 count=1' (cwd None)
Thread-16::DEBUG::2014-05-27
15:02:25,657::fileSD::225::Storage.Misc.excCmd::(getReadDelay)
'/bin/dd iflag=direct
if=/rhev/data-center/mnt/glusterSD/gluster0:vm-store/6d637c7f-a4ab-4510-a0d9-63a04c55d6d8/dom_md/metadata
bs=4096 count=1' (cwd None)
Thread-16::DEBUG::2014-05-27
15:02:35,698::fileSD::225::Storage.Misc.excCmd::(getReadDelay)
'/bin/dd iflag=direct
if=/rhev/data-center/mnt/glusterSD/gluster0:vm-store/6d637c7f-a4ab-4510-a0d9-63a04c55d6d8/dom_md/metadata
bs=4096 count=1' (cwd None)
Thread-16::DEBUG::2014-05-27
15:02:45,740::fileSD::225::Storage.Misc.excCmd::(getReadDelay)
'/bin/dd iflag=direct
if=/rhev/data-center/mnt/glusterSD/gluster0:vm-store/6d637c7f-a4ab-4510-a0d9-63a04c55d6d8/dom_md/metadata
bs=4096 count=1' (cwd None)
Thread-16::DEBUG::2014-05-27
15:02:55,784::fileSD::225::Storage.Misc.excCmd::(getReadDelay)
'/bin/dd iflag=direct
if=/rhev/data-center/mnt/glusterSD/gluster0:vm-store/6d637c7f-a4ab-4510-a0d9-63a04c55d6d8/dom_md/metadata
bs=4096 count=1' (cwd None)
Thread-16::DEBUG::2014-05-27
15:03:05,827::fileSD::225::Storage.Misc.excCmd::(getReadDelay)
'/bin/dd iflag=direct
Re: [ovirt-users] Persisting glusterfs configs on an oVirt node
Am Mittwoch, den 28.05.2014, 14:14 + schrieb Simon Barrett: I did a persist /var/lib/glusterd and things are looking better. The gluster config is now still in place after a reboot. As a workaround to getting glusterd running on boot, I added service glusterd start to /etc/rc.local and ran persist /etc/rc.local. It appears to be working but feels like a bit of a hack. Does anyone have any other suggestions as to the correct way to do this? Hey Simon, I was also investigating both the steps you did. And was also about to recommend them :) They are more a workaround. We basically need some patches to change the defaults on Node, to let gluster work out of the box. This would include persisting the correct paths and enabling glusterd if enabled. - fabian Thanks, Simon -Original Message- From: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On Behalf Of Simon Barrett Sent: 28 May 2014 14:12 To: Ryan Barry; Fabian Deutsch; Doron Fediuck Cc: users@ovirt.org Subject: Re: [ovirt-users] Persisting glusterfs configs on an oVirt node Thanks for the replies. I cannot get glusterd to start on boot and I lose all gluster config every reboot. The following shows what I did on the node to start glusterd, create a volume etc, followed by the state of the node after a reboot. [root@ovirt_node]# service glusterd status glusterd is stopped [root@ovirt_node]# chkconfig --list glusterd glusterd0:off 1:off 2:off 3:off 4:off 5:off 6:off [root@ovirt_node]# service glusterd start Starting glusterd:[ OK ] gluster volume create vmstore 10.22.8.46:/data/glusterfs/vmstore volume create: vmstore: success: please start the volume to access data gluster vol start vmstore volume start: vmstore: success gluster vol info Volume Name: vmstore Type: Distribute Volume ID: 5bd01043-1352-4014-88ca-e632e264d088 Status: Started Number of Bricks: 1 Transport-type: tcp Bricks: Brick1: 10.22.8.46:/data/glusterfs/vmstore [root@ovirt_node]# ls -1 /var/lib/glusterd/vols/vmstore/ bricks node_state.info trusted-vmstore-fuse.vol cksum rbstate vmstore.10.22.8.46.data-glusterfs-vmstore.vol info run vmstore-fuse.vol [root@ovirt_node]# grep gluster /etc/rwtab.d/* /etc/rwtab.d/ovirt:files /var/lib/glusterd [root@ovirt_node]# chkconfig glusterd on [root@ovirt_node]# chkconfig --list glusterd glusterd0:off 1:off 2:on3:on4:on5:on6:off I then reboot the node and see the following: [root@ovirt_node]# service glusterd status glusterd is stopped [root@ovirt_node]# chkconfig --list glusterd glusterd0:off 1:off 2:off 3:off 4:off 5:off 6:off [root@ovirt_node]# ls -l /var/lib/glusterd/vols/ total 0 No more gluster volume configuration files. I've taken a look through http://www.ovirt.org/Node_Troubleshooting#Making_changes_last_.2F_Persisting_changes but I'm unsure what needs to be done to persist this configuration. To get glusterd to start on boot, do I need to manually persist /etc/rc* files? I see files /var/lib/glusterd mentioned in /etc/rwtab.d/ovirt. Is this a list of the files/dirs that should be persisted automatically? If so, is it recursive and should it include everything in /var/lib/glusterd/vols? TIA for any help with this. Simon -Original Message- From: Ryan Barry [mailto:rba...@redhat.com] Sent: 27 May 2014 14:01 To: Fabian Deutsch; Doron Fediuck; Simon Barrett Cc: users@ovirt.org Subject: Re: [ovirt-users] Persisting glusterfs configs on an oVirt node On 05/26/2014 04:14 AM, Fabian Deutsch wrote: Am Sonntag, den 25.05.2014, 08:18 -0400 schrieb Doron Fediuck: - Original Message - From: Simon Barrett simon.barr...@tradingscreen.com To: users@ovirt.org Sent: Friday, May 23, 2014 11:29:39 AM Subject: [ovirt-users] Persisting glusterfs configs on an oVirt node I am working through the setup of oVirt node for a 3.4.1 deployment. I setup some glusterfs volumes/bricks on oVirt Node Hypervisor release 3.0.4 (1.0.201401291204.el6) and created a storage domain. All was working OK until I rebooted the node and found that the glusterfs configuration had not been retained. Is there something I should be doing to persist any glusterfs configuration so it survives a node reboot? Many thanks, Simon Hi Simon, it actually sounds like a bug to me, as node are supposed to support gluster. Ryan / Fabian- thoughts? Hey, I vaguely remember that we were seeing a bug like this some time ago. We fixed /var/lib/glusterd to be writable (using tmpfs), but it can actually be that we need to persist those contents. But Simon, can you give details which configuration files are missing and why glusterd is not starting?
Re: [ovirt-users] Persisting glusterfs configs on an oVirt node
I just wasn't sure if I was missing something in the configuration to enable this. I'll stick with the workarounds I have for now and see how it goes. Thanks again. Simon -Original Message- From: Fabian Deutsch [mailto:fdeut...@redhat.com] Sent: 28 May 2014 15:20 To: Simon Barrett Cc: Ryan Barry; Doron Fediuck; users@ovirt.org Subject: Re: [ovirt-users] Persisting glusterfs configs on an oVirt node Am Mittwoch, den 28.05.2014, 14:14 + schrieb Simon Barrett: I did a persist /var/lib/glusterd and things are looking better. The gluster config is now still in place after a reboot. As a workaround to getting glusterd running on boot, I added service glusterd start to /etc/rc.local and ran persist /etc/rc.local. It appears to be working but feels like a bit of a hack. Does anyone have any other suggestions as to the correct way to do this? Hey Simon, I was also investigating both the steps you did. And was also about to recommend them :) They are more a workaround. We basically need some patches to change the defaults on Node, to let gluster work out of the box. This would include persisting the correct paths and enabling glusterd if enabled. - fabian Thanks, Simon -Original Message- From: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On Behalf Of Simon Barrett Sent: 28 May 2014 14:12 To: Ryan Barry; Fabian Deutsch; Doron Fediuck Cc: users@ovirt.org Subject: Re: [ovirt-users] Persisting glusterfs configs on an oVirt node Thanks for the replies. I cannot get glusterd to start on boot and I lose all gluster config every reboot. The following shows what I did on the node to start glusterd, create a volume etc, followed by the state of the node after a reboot. [root@ovirt_node]# service glusterd status glusterd is stopped [root@ovirt_node]# chkconfig --list glusterd glusterd0:off 1:off 2:off 3:off 4:off 5:off 6:off [root@ovirt_node]# service glusterd start Starting glusterd:[ OK ] gluster volume create vmstore 10.22.8.46:/data/glusterfs/vmstore volume create: vmstore: success: please start the volume to access data gluster vol start vmstore volume start: vmstore: success gluster vol info Volume Name: vmstore Type: Distribute Volume ID: 5bd01043-1352-4014-88ca-e632e264d088 Status: Started Number of Bricks: 1 Transport-type: tcp Bricks: Brick1: 10.22.8.46:/data/glusterfs/vmstore [root@ovirt_node]# ls -1 /var/lib/glusterd/vols/vmstore/ bricks node_state.info trusted-vmstore-fuse.vol cksum rbstate vmstore.10.22.8.46.data-glusterfs-vmstore.vol info run vmstore-fuse.vol [root@ovirt_node]# grep gluster /etc/rwtab.d/* /etc/rwtab.d/ovirt:files /var/lib/glusterd [root@ovirt_node]# chkconfig glusterd on [root@ovirt_node]# chkconfig --list glusterd glusterd0:off 1:off 2:on3:on4:on5:on6:off I then reboot the node and see the following: [root@ovirt_node]# service glusterd status glusterd is stopped [root@ovirt_node]# chkconfig --list glusterd glusterd0:off 1:off 2:off 3:off 4:off 5:off 6:off [root@ovirt_node]# ls -l /var/lib/glusterd/vols/ total 0 No more gluster volume configuration files. I've taken a look through http://www.ovirt.org/Node_Troubleshooting#Making_changes_last_.2F_Persisting_changes but I'm unsure what needs to be done to persist this configuration. To get glusterd to start on boot, do I need to manually persist /etc/rc* files? I see files /var/lib/glusterd mentioned in /etc/rwtab.d/ovirt. Is this a list of the files/dirs that should be persisted automatically? If so, is it recursive and should it include everything in /var/lib/glusterd/vols? TIA for any help with this. Simon -Original Message- From: Ryan Barry [mailto:rba...@redhat.com] Sent: 27 May 2014 14:01 To: Fabian Deutsch; Doron Fediuck; Simon Barrett Cc: users@ovirt.org Subject: Re: [ovirt-users] Persisting glusterfs configs on an oVirt node On 05/26/2014 04:14 AM, Fabian Deutsch wrote: Am Sonntag, den 25.05.2014, 08:18 -0400 schrieb Doron Fediuck: - Original Message - From: Simon Barrett simon.barr...@tradingscreen.com To: users@ovirt.org Sent: Friday, May 23, 2014 11:29:39 AM Subject: [ovirt-users] Persisting glusterfs configs on an oVirt node I am working through the setup of oVirt node for a 3.4.1 deployment. I setup some glusterfs volumes/bricks on oVirt Node Hypervisor release 3.0.4 (1.0.201401291204.el6) and created a storage domain. All was working OK until I rebooted the node and found that the glusterfs configuration had not been retained. Is there something I should be doing to persist any glusterfs configuration so it survives a node reboot? Many thanks, Simon Hi Simon,
Re: [ovirt-users] Persisting glusterfs configs on an oVirt node
Am Mittwoch, den 28.05.2014, 14:22 + schrieb Simon Barrett: I just wasn't sure if I was missing something in the configuration to enable this. I'll stick with the workarounds I have for now and see how it goes. Hey Simon, it would be great if you could let us know about more issues, which will help us to improve the situation even more. Greetings fabian Thanks again. Simon -Original Message- From: Fabian Deutsch [mailto:fdeut...@redhat.com] Sent: 28 May 2014 15:20 To: Simon Barrett Cc: Ryan Barry; Doron Fediuck; users@ovirt.org Subject: Re: [ovirt-users] Persisting glusterfs configs on an oVirt node Am Mittwoch, den 28.05.2014, 14:14 + schrieb Simon Barrett: I did a persist /var/lib/glusterd and things are looking better. The gluster config is now still in place after a reboot. As a workaround to getting glusterd running on boot, I added service glusterd start to /etc/rc.local and ran persist /etc/rc.local. It appears to be working but feels like a bit of a hack. Does anyone have any other suggestions as to the correct way to do this? Hey Simon, I was also investigating both the steps you did. And was also about to recommend them :) They are more a workaround. We basically need some patches to change the defaults on Node, to let gluster work out of the box. This would include persisting the correct paths and enabling glusterd if enabled. - fabian Thanks, Simon -Original Message- From: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On Behalf Of Simon Barrett Sent: 28 May 2014 14:12 To: Ryan Barry; Fabian Deutsch; Doron Fediuck Cc: users@ovirt.org Subject: Re: [ovirt-users] Persisting glusterfs configs on an oVirt node Thanks for the replies. I cannot get glusterd to start on boot and I lose all gluster config every reboot. The following shows what I did on the node to start glusterd, create a volume etc, followed by the state of the node after a reboot. [root@ovirt_node]# service glusterd status glusterd is stopped [root@ovirt_node]# chkconfig --list glusterd glusterd0:off 1:off 2:off 3:off 4:off 5:off 6:off [root@ovirt_node]# service glusterd start Starting glusterd:[ OK ] gluster volume create vmstore 10.22.8.46:/data/glusterfs/vmstore volume create: vmstore: success: please start the volume to access data gluster vol start vmstore volume start: vmstore: success gluster vol info Volume Name: vmstore Type: Distribute Volume ID: 5bd01043-1352-4014-88ca-e632e264d088 Status: Started Number of Bricks: 1 Transport-type: tcp Bricks: Brick1: 10.22.8.46:/data/glusterfs/vmstore [root@ovirt_node]# ls -1 /var/lib/glusterd/vols/vmstore/ bricks node_state.info trusted-vmstore-fuse.vol cksum rbstate vmstore.10.22.8.46.data-glusterfs-vmstore.vol info run vmstore-fuse.vol [root@ovirt_node]# grep gluster /etc/rwtab.d/* /etc/rwtab.d/ovirt:files /var/lib/glusterd [root@ovirt_node]# chkconfig glusterd on [root@ovirt_node]# chkconfig --list glusterd glusterd0:off 1:off 2:on3:on4:on5:on6:off I then reboot the node and see the following: [root@ovirt_node]# service glusterd status glusterd is stopped [root@ovirt_node]# chkconfig --list glusterd glusterd0:off 1:off 2:off 3:off 4:off 5:off 6:off [root@ovirt_node]# ls -l /var/lib/glusterd/vols/ total 0 No more gluster volume configuration files. I've taken a look through http://www.ovirt.org/Node_Troubleshooting#Making_changes_last_.2F_Persisting_changes but I'm unsure what needs to be done to persist this configuration. To get glusterd to start on boot, do I need to manually persist /etc/rc* files? I see files /var/lib/glusterd mentioned in /etc/rwtab.d/ovirt. Is this a list of the files/dirs that should be persisted automatically? If so, is it recursive and should it include everything in /var/lib/glusterd/vols? TIA for any help with this. Simon -Original Message- From: Ryan Barry [mailto:rba...@redhat.com] Sent: 27 May 2014 14:01 To: Fabian Deutsch; Doron Fediuck; Simon Barrett Cc: users@ovirt.org Subject: Re: [ovirt-users] Persisting glusterfs configs on an oVirt node On 05/26/2014 04:14 AM, Fabian Deutsch wrote: Am Sonntag, den 25.05.2014, 08:18 -0400 schrieb Doron Fediuck: - Original Message - From: Simon Barrett simon.barr...@tradingscreen.com To: users@ovirt.org Sent: Friday, May 23, 2014 11:29:39 AM Subject: [ovirt-users] Persisting glusterfs configs on an oVirt node I am working through the setup of oVirt node for a 3.4.1 deployment. I setup some glusterfs volumes/bricks on oVirt Node
Re: [ovirt-users] Persisting glusterfs configs on an oVirt node
Am Mittwoch, den 28.05.2014, 14:22 + schrieb Simon Barrett: I just wasn't sure if I was missing something in the configuration to enable this. I'll stick with the workarounds I have for now and see how it goes. Thanks again. You are welcome! :) Simon -Original Message- From: Fabian Deutsch [mailto:fdeut...@redhat.com] Sent: 28 May 2014 15:20 To: Simon Barrett Cc: Ryan Barry; Doron Fediuck; users@ovirt.org Subject: Re: [ovirt-users] Persisting glusterfs configs on an oVirt node Am Mittwoch, den 28.05.2014, 14:14 + schrieb Simon Barrett: I did a persist /var/lib/glusterd and things are looking better. The gluster config is now still in place after a reboot. As a workaround to getting glusterd running on boot, I added service glusterd start to /etc/rc.local and ran persist /etc/rc.local. It appears to be working but feels like a bit of a hack. Does anyone have any other suggestions as to the correct way to do this? Hey Simon, I was also investigating both the steps you did. And was also about to recommend them :) They are more a workaround. We basically need some patches to change the defaults on Node, to let gluster work out of the box. This would include persisting the correct paths and enabling glusterd if enabled. - fabian Thanks, Simon -Original Message- From: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On Behalf Of Simon Barrett Sent: 28 May 2014 14:12 To: Ryan Barry; Fabian Deutsch; Doron Fediuck Cc: users@ovirt.org Subject: Re: [ovirt-users] Persisting glusterfs configs on an oVirt node Thanks for the replies. I cannot get glusterd to start on boot and I lose all gluster config every reboot. The following shows what I did on the node to start glusterd, create a volume etc, followed by the state of the node after a reboot. [root@ovirt_node]# service glusterd status glusterd is stopped [root@ovirt_node]# chkconfig --list glusterd glusterd0:off 1:off 2:off 3:off 4:off 5:off 6:off [root@ovirt_node]# service glusterd start Starting glusterd:[ OK ] gluster volume create vmstore 10.22.8.46:/data/glusterfs/vmstore volume create: vmstore: success: please start the volume to access data gluster vol start vmstore volume start: vmstore: success gluster vol info Volume Name: vmstore Type: Distribute Volume ID: 5bd01043-1352-4014-88ca-e632e264d088 Status: Started Number of Bricks: 1 Transport-type: tcp Bricks: Brick1: 10.22.8.46:/data/glusterfs/vmstore [root@ovirt_node]# ls -1 /var/lib/glusterd/vols/vmstore/ bricks node_state.info trusted-vmstore-fuse.vol cksum rbstate vmstore.10.22.8.46.data-glusterfs-vmstore.vol info run vmstore-fuse.vol [root@ovirt_node]# grep gluster /etc/rwtab.d/* /etc/rwtab.d/ovirt:files /var/lib/glusterd [root@ovirt_node]# chkconfig glusterd on [root@ovirt_node]# chkconfig --list glusterd glusterd0:off 1:off 2:on3:on4:on5:on6:off I then reboot the node and see the following: [root@ovirt_node]# service glusterd status glusterd is stopped [root@ovirt_node]# chkconfig --list glusterd glusterd0:off 1:off 2:off 3:off 4:off 5:off 6:off [root@ovirt_node]# ls -l /var/lib/glusterd/vols/ total 0 No more gluster volume configuration files. I've taken a look through http://www.ovirt.org/Node_Troubleshooting#Making_changes_last_.2F_Persisting_changes but I'm unsure what needs to be done to persist this configuration. To get glusterd to start on boot, do I need to manually persist /etc/rc* files? I see files /var/lib/glusterd mentioned in /etc/rwtab.d/ovirt. Is this a list of the files/dirs that should be persisted automatically? If so, is it recursive and should it include everything in /var/lib/glusterd/vols? TIA for any help with this. Simon -Original Message- From: Ryan Barry [mailto:rba...@redhat.com] Sent: 27 May 2014 14:01 To: Fabian Deutsch; Doron Fediuck; Simon Barrett Cc: users@ovirt.org Subject: Re: [ovirt-users] Persisting glusterfs configs on an oVirt node On 05/26/2014 04:14 AM, Fabian Deutsch wrote: Am Sonntag, den 25.05.2014, 08:18 -0400 schrieb Doron Fediuck: - Original Message - From: Simon Barrett simon.barr...@tradingscreen.com To: users@ovirt.org Sent: Friday, May 23, 2014 11:29:39 AM Subject: [ovirt-users] Persisting glusterfs configs on an oVirt node I am working through the setup of oVirt node for a 3.4.1 deployment. I setup some glusterfs volumes/bricks on oVirt Node Hypervisor release 3.0.4 (1.0.201401291204.el6) and created a storage domain. All was working OK until I rebooted the
[ovirt-users] oVirt Weekly Meeting Minutes -- 2014-05-28
Minutes:http://ovirt.org/meetings/ovirt/2014/ovirt.2014-05-28-14.01.html Minutes (text): http://ovirt.org/meetings/ovirt/2014/ovirt.2014-05-28-14.01.txt Log: http://ovirt.org/meetings/ovirt/2014/ovirt.2014-05-28-14.01.log.html = #ovirt: oVirt Weekly Sync = Meeting started by doron at 14:01:38 UTC. The full logs are available at http://ovirt.org/meetings/ovirt/2014/ovirt.2014-05-28-14.01.log.html . Meeting summary --- * Agenda and roll Call (doron, 14:01:50) * infra update (doron, 14:01:51) * 3.4.z updates (doron, 14:01:53) * 3.5 status (doron, 14:01:54) * conferences and workshops (doron, 14:01:56) * other topics (doron, 14:01:57) * infra update (doron, 14:02:00) * some jenkins jobs are giving 404 when running. mail in...@ovirt.org or ping dcaro if you hit it. (doron, 14:05:08) * 3.4.z updates (doron, 14:05:28) * 3.4.2: no blockers, we should be on track. RC published yesterday (doron, 14:06:32) * 3.5 status (doron, 14:08:46) * gluster missing 2 features for 3.5 plan, and require additional ~2 weeks to complete. (doron, 14:14:25) * infra 3.5 missing 4 features and require additional 2 weeks to conclude (Mid June). (doron, 14:19:07) * integration 3.5 updates: Websocket proxy, DWH and Reports on separate hosts will need additional 2 weeks as well to conclude. (doron, 14:20:36) * network 3.5 updates: all features ready but 2. (doron, 14:25:46) * node 3.5 updates: 2 features mostly done, but additional 1.5 weeks will be beneficial. (doron, 14:29:34) * All SLA features are mostly done, but need additional time to conclude; so 2 weeks will help here as well. (doron, 14:30:49) * UX team ready for 3.5 feature freeze. (doron, 14:33:34) * virt 3.5 is mostly done. 3 last features needs some more time to converge. Probably less than a week. (doron, 14:40:41) * ACTION: doron to post a suggestion to push feature freeze by 2 weeks in order to allow converging the last features. (doron, 14:43:33) * conferences and workshops (doron, 14:43:53) * events conferences: OpenStack Israel in June 2nd and oVirt will have a presence at OSCON in mid-July. (doron, 14:45:10) * LinuxCon/CloudOpen in mid-August, as well as LinuxCon/CloudOpen/KVM Forum in October. (doron, 14:45:28) * oVirt will be at USENIX LISA in September, though no talks were accepted. (doron, 14:45:47) * bkp is oordinating with Fedora, CentOS communities to find local meetups that we might speak at and ideally seed our own meetup events. (doron, 14:46:26) * other topics (doron, 14:46:42) * bkp finished a new oVirt feature article that will on Linux Weekly News (lwn.net) possibly as early as today (doron, 14:48:23) Meeting ended at 14:50:12 UTC. Action Items * doron to post a suggestion to push feature freeze by 2 weeks in order to allow converging the last features. Action Items, by person --- * doron * doron to post a suggestion to push feature freeze by 2 weeks in order to allow converging the last features. * **UNASSIGNED** * (none) People Present (lines said) --- * doron (109) * oved (14) * mskrivanek (13) * lvernia (12) * bkp (12) * fabiand (9) * awels (5) * sahina (5) * dcaro (2) * ovirtbot (2) * everyone (1) * lvernia_ (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] post glusterfs 3.4 - 3.5 upgrade issue in ovirt (3.4.0-1.fc19): bricks unavailable
ovirt version is 3.4. I did have a slightly older version of vdsm on
gluster0 but I have updated it and the issue persists. The compatibility
version on the storage cluster is 3.3.
I checked the logs for GlusterSyncJob notifications and there are none.
On 28 May 2014 10:19, Sahina Bose sab...@redhat.com wrote:
Hi Alastair,
This could be a mismatch in the hostname identified in ovirt and gluster.
You could check for any exceptions from GlusterSyncJob in engine.log.
Also, what version of ovirt are you using. And the compatibility version
of your cluster?
On 05/28/2014 12:40 AM, Alastair Neil wrote:
Hi thanks for the reply. Here is an extract from a grep I ran on the
vdsm log grepping for the volume name vm-store. It seems to indicate the
bricks are ONLINE.
I am uncertain how to extract meaningful information from the engine.log
can you provide some guidance?
Thanks,
Alastair
Thread-100::DEBUG::2014-05-27
15:01:06,335::BindingXMLRPC::1067::vds::(wrapper) client
[129.174.94.239]::call volumeStatus with ('vm-store', '', '') {}
Thread-100::DEBUG::2014-05-27
15:01:06,356::BindingXMLRPC::1074::vds::(wrapper) return volumeStatus with
{'volumeStatus': {'bricks': [{'status': 'ONLINE', 'brick':
'gluster0:/export/brick0', 'pid': '2675', 'port': '49158', 'hostuuid':
'bcff5245-ea86-4384-a1bf-9219c8be8001'}, {'status': 'ONLINE', 'brick':
'gluster1:/export/brick4/vm-store', 'pid': '2309', 'port': '49158',
'hostuuid': '54d39ae4-91ae-410b-828c-67031f3d8a68'}], 'nfs': [{'status':
'ONLINE', 'hostname': '129.174.126.56', 'pid': '27012', 'port': '2049',
'hostuuid': '54d39ae4-91ae-410b-828c-67031f3d8a68'}, {'status': 'ONLINE',
'hostname': 'gluster0', 'pid': '12875', 'port': '2049', 'hostuuid':
'bcff5245-ea86-4384-a1bf-9219c8be8001'}], 'shd': [{'status': 'ONLINE',
'hostname': '129.174.126.56', 'pid': '27019', 'hostuuid':
'54d39ae4-91ae-410b-828c-67031f3d8a68'}, {'status': 'ONLINE', 'hostname':
'gluster0', 'pid': '12882', 'hostuuid':
'bcff5245-ea86-4384-a1bf-9219c8be8001'}], 'name': 'vm-store'}, 'status':
{'message': 'Done', 'code': 0}}
Thread-16::DEBUG::2014-05-27
15:01:15,339::fileSD::225::Storage.Misc.excCmd::(getReadDelay) '/bin/dd
iflag=direct
if=/rhev/data-center/mnt/glusterSD/gluster0:vm-store/6d637c7f-a4ab-4510-a0d9-63a04c55d6d8/dom_md/metadata
bs=4096 count=1' (cwd None)
Thread-16::DEBUG::2014-05-27
15:01:25,381::fileSD::225::Storage.Misc.excCmd::(getReadDelay) '/bin/dd
iflag=direct
if=/rhev/data-center/mnt/glusterSD/gluster0:vm-store/6d637c7f-a4ab-4510-a0d9-63a04c55d6d8/dom_md/metadata
bs=4096 count=1' (cwd None)
Thread-16::DEBUG::2014-05-27
15:01:35,423::fileSD::225::Storage.Misc.excCmd::(getReadDelay) '/bin/dd
iflag=direct
if=/rhev/data-center/mnt/glusterSD/gluster0:vm-store/6d637c7f-a4ab-4510-a0d9-63a04c55d6d8/dom_md/metadata
bs=4096 count=1' (cwd None)
Thread-16::DEBUG::2014-05-27
15:01:45,465::fileSD::225::Storage.Misc.excCmd::(getReadDelay) '/bin/dd
iflag=direct
if=/rhev/data-center/mnt/glusterSD/gluster0:vm-store/6d637c7f-a4ab-4510-a0d9-63a04c55d6d8/dom_md/metadata
bs=4096 count=1' (cwd None)
Thread-16::DEBUG::2014-05-27
15:01:55,507::fileSD::225::Storage.Misc.excCmd::(getReadDelay) '/bin/dd
iflag=direct
if=/rhev/data-center/mnt/glusterSD/gluster0:vm-store/6d637c7f-a4ab-4510-a0d9-63a04c55d6d8/dom_md/metadata
bs=4096 count=1' (cwd None)
Thread-16::DEBUG::2014-05-27
15:02:05,549::fileSD::225::Storage.Misc.excCmd::(getReadDelay) '/bin/dd
iflag=direct
if=/rhev/data-center/mnt/glusterSD/gluster0:vm-store/6d637c7f-a4ab-4510-a0d9-63a04c55d6d8/dom_md/metadata
bs=4096 count=1' (cwd None)
Thread-16::DEBUG::2014-05-27
15:02:15,590::fileSD::225::Storage.Misc.excCmd::(getReadDelay) '/bin/dd
iflag=direct
if=/rhev/data-center/mnt/glusterSD/gluster0:vm-store/6d637c7f-a4ab-4510-a0d9-63a04c55d6d8/dom_md/metadata
bs=4096 count=1' (cwd None)
Thread-16::DEBUG::2014-05-27
15:02:25,657::fileSD::225::Storage.Misc.excCmd::(getReadDelay) '/bin/dd
iflag=direct
if=/rhev/data-center/mnt/glusterSD/gluster0:vm-store/6d637c7f-a4ab-4510-a0d9-63a04c55d6d8/dom_md/metadata
bs=4096 count=1' (cwd None)
Thread-16::DEBUG::2014-05-27
15:02:35,698::fileSD::225::Storage.Misc.excCmd::(getReadDelay) '/bin/dd
iflag=direct
if=/rhev/data-center/mnt/glusterSD/gluster0:vm-store/6d637c7f-a4ab-4510-a0d9-63a04c55d6d8/dom_md/metadata
bs=4096 count=1' (cwd None)
Thread-16::DEBUG::2014-05-27
15:02:45,740::fileSD::225::Storage.Misc.excCmd::(getReadDelay) '/bin/dd
iflag=direct
if=/rhev/data-center/mnt/glusterSD/gluster0:vm-store/6d637c7f-a4ab-4510-a0d9-63a04c55d6d8/dom_md/metadata
bs=4096 count=1' (cwd None)
Thread-16::DEBUG::2014-05-27
15:02:55,784::fileSD::225::Storage.Misc.excCmd::(getReadDelay) '/bin/dd
iflag=direct
if=/rhev/data-center/mnt/glusterSD/gluster0:vm-store/6d637c7f-a4ab-4510-a0d9-63a04c55d6d8/dom_md/metadata
bs=4096 count=1' (cwd None)
Thread-16::DEBUG::2014-05-27
15:03:05,827::fileSD::225::Storage.Misc.excCmd::(getReadDelay) '/bin/dd
Re: [ovirt-users] post glusterfs 3.4 - 3.5 upgrade issue in ovirt (3.4.0-1.fc19): bricks unavailable
I just noticed this in the console and I don't know if it is relevant.
When I look at the General tab on the hosts under GlusterFS Version it
shows N/A.
On 28 May 2014 11:03, Alastair Neil ajneil.t...@gmail.com wrote:
ovirt version is 3.4. I did have a slightly older version of vdsm on
gluster0 but I have updated it and the issue persists. The compatibility
version on the storage cluster is 3.3.
I checked the logs for GlusterSyncJob notifications and there are none.
On 28 May 2014 10:19, Sahina Bose sab...@redhat.com wrote:
Hi Alastair,
This could be a mismatch in the hostname identified in ovirt and gluster.
You could check for any exceptions from GlusterSyncJob in engine.log.
Also, what version of ovirt are you using. And the compatibility version
of your cluster?
On 05/28/2014 12:40 AM, Alastair Neil wrote:
Hi thanks for the reply. Here is an extract from a grep I ran on the
vdsm log grepping for the volume name vm-store. It seems to indicate the
bricks are ONLINE.
I am uncertain how to extract meaningful information from the
engine.log can you provide some guidance?
Thanks,
Alastair
Thread-100::DEBUG::2014-05-27
15:01:06,335::BindingXMLRPC::1067::vds::(wrapper) client
[129.174.94.239]::call volumeStatus with ('vm-store', '', '') {}
Thread-100::DEBUG::2014-05-27
15:01:06,356::BindingXMLRPC::1074::vds::(wrapper) return volumeStatus with
{'volumeStatus': {'bricks': [{'status': 'ONLINE', 'brick':
'gluster0:/export/brick0', 'pid': '2675', 'port': '49158', 'hostuuid':
'bcff5245-ea86-4384-a1bf-9219c8be8001'}, {'status': 'ONLINE', 'brick':
'gluster1:/export/brick4/vm-store', 'pid': '2309', 'port': '49158',
'hostuuid': '54d39ae4-91ae-410b-828c-67031f3d8a68'}], 'nfs': [{'status':
'ONLINE', 'hostname': '129.174.126.56', 'pid': '27012', 'port': '2049',
'hostuuid': '54d39ae4-91ae-410b-828c-67031f3d8a68'}, {'status': 'ONLINE',
'hostname': 'gluster0', 'pid': '12875', 'port': '2049', 'hostuuid':
'bcff5245-ea86-4384-a1bf-9219c8be8001'}], 'shd': [{'status': 'ONLINE',
'hostname': '129.174.126.56', 'pid': '27019', 'hostuuid':
'54d39ae4-91ae-410b-828c-67031f3d8a68'}, {'status': 'ONLINE', 'hostname':
'gluster0', 'pid': '12882', 'hostuuid':
'bcff5245-ea86-4384-a1bf-9219c8be8001'}], 'name': 'vm-store'}, 'status':
{'message': 'Done', 'code': 0}}
Thread-16::DEBUG::2014-05-27
15:01:15,339::fileSD::225::Storage.Misc.excCmd::(getReadDelay) '/bin/dd
iflag=direct
if=/rhev/data-center/mnt/glusterSD/gluster0:vm-store/6d637c7f-a4ab-4510-a0d9-63a04c55d6d8/dom_md/metadata
bs=4096 count=1' (cwd None)
Thread-16::DEBUG::2014-05-27
15:01:25,381::fileSD::225::Storage.Misc.excCmd::(getReadDelay) '/bin/dd
iflag=direct
if=/rhev/data-center/mnt/glusterSD/gluster0:vm-store/6d637c7f-a4ab-4510-a0d9-63a04c55d6d8/dom_md/metadata
bs=4096 count=1' (cwd None)
Thread-16::DEBUG::2014-05-27
15:01:35,423::fileSD::225::Storage.Misc.excCmd::(getReadDelay) '/bin/dd
iflag=direct
if=/rhev/data-center/mnt/glusterSD/gluster0:vm-store/6d637c7f-a4ab-4510-a0d9-63a04c55d6d8/dom_md/metadata
bs=4096 count=1' (cwd None)
Thread-16::DEBUG::2014-05-27
15:01:45,465::fileSD::225::Storage.Misc.excCmd::(getReadDelay) '/bin/dd
iflag=direct
if=/rhev/data-center/mnt/glusterSD/gluster0:vm-store/6d637c7f-a4ab-4510-a0d9-63a04c55d6d8/dom_md/metadata
bs=4096 count=1' (cwd None)
Thread-16::DEBUG::2014-05-27
15:01:55,507::fileSD::225::Storage.Misc.excCmd::(getReadDelay) '/bin/dd
iflag=direct
if=/rhev/data-center/mnt/glusterSD/gluster0:vm-store/6d637c7f-a4ab-4510-a0d9-63a04c55d6d8/dom_md/metadata
bs=4096 count=1' (cwd None)
Thread-16::DEBUG::2014-05-27
15:02:05,549::fileSD::225::Storage.Misc.excCmd::(getReadDelay) '/bin/dd
iflag=direct
if=/rhev/data-center/mnt/glusterSD/gluster0:vm-store/6d637c7f-a4ab-4510-a0d9-63a04c55d6d8/dom_md/metadata
bs=4096 count=1' (cwd None)
Thread-16::DEBUG::2014-05-27
15:02:15,590::fileSD::225::Storage.Misc.excCmd::(getReadDelay) '/bin/dd
iflag=direct
if=/rhev/data-center/mnt/glusterSD/gluster0:vm-store/6d637c7f-a4ab-4510-a0d9-63a04c55d6d8/dom_md/metadata
bs=4096 count=1' (cwd None)
Thread-16::DEBUG::2014-05-27
15:02:25,657::fileSD::225::Storage.Misc.excCmd::(getReadDelay) '/bin/dd
iflag=direct
if=/rhev/data-center/mnt/glusterSD/gluster0:vm-store/6d637c7f-a4ab-4510-a0d9-63a04c55d6d8/dom_md/metadata
bs=4096 count=1' (cwd None)
Thread-16::DEBUG::2014-05-27
15:02:35,698::fileSD::225::Storage.Misc.excCmd::(getReadDelay) '/bin/dd
iflag=direct
if=/rhev/data-center/mnt/glusterSD/gluster0:vm-store/6d637c7f-a4ab-4510-a0d9-63a04c55d6d8/dom_md/metadata
bs=4096 count=1' (cwd None)
Thread-16::DEBUG::2014-05-27
15:02:45,740::fileSD::225::Storage.Misc.excCmd::(getReadDelay) '/bin/dd
iflag=direct
if=/rhev/data-center/mnt/glusterSD/gluster0:vm-store/6d637c7f-a4ab-4510-a0d9-63a04c55d6d8/dom_md/metadata
bs=4096 count=1' (cwd None)
Thread-16::DEBUG::2014-05-27
15:02:55,784::fileSD::225::Storage.Misc.excCmd::(getReadDelay) '/bin/dd
iflag=direct
Re: [ovirt-users] Persisting glusterfs configs on an oVirt node
- Original Message - From: Simon Barrett simon.barr...@tradingscreen.com To: Fabian Deutsch fdeut...@redhat.com Cc: Ryan Barry rba...@redhat.com, Doron Fediuck dfedi...@redhat.com, users@ovirt.org Sent: Wednesday, May 28, 2014 5:22:17 PM Subject: RE: [ovirt-users] Persisting glusterfs configs on an oVirt node I just wasn't sure if I was missing something in the configuration to enable this. I'll stick with the workarounds I have for now and see how it goes. Thanks again. Simon -Original Message- From: Fabian Deutsch [mailto:fdeut...@redhat.com] Sent: 28 May 2014 15:20 To: Simon Barrett Cc: Ryan Barry; Doron Fediuck; users@ovirt.org Subject: Re: [ovirt-users] Persisting glusterfs configs on an oVirt node Am Mittwoch, den 28.05.2014, 14:14 + schrieb Simon Barrett: I did a persist /var/lib/glusterd and things are looking better. The gluster config is now still in place after a reboot. As a workaround to getting glusterd running on boot, I added service glusterd start to /etc/rc.local and ran persist /etc/rc.local. It appears to be working but feels like a bit of a hack. Does anyone have any other suggestions as to the correct way to do this? Hey Simon, I was also investigating both the steps you did. And was also about to recommend them :) They are more a workaround. We basically need some patches to change the defaults on Node, to let gluster work out of the box. This would include persisting the correct paths and enabling glusterd if enabled. - fabian Thanks, Simon -Original Message- From: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On Behalf Of Simon Barrett Sent: 28 May 2014 14:12 To: Ryan Barry; Fabian Deutsch; Doron Fediuck Cc: users@ovirt.org Subject: Re: [ovirt-users] Persisting glusterfs configs on an oVirt node Thanks for the replies. I cannot get glusterd to start on boot and I lose all gluster config every reboot. The following shows what I did on the node to start glusterd, create a volume etc, followed by the state of the node after a reboot. [root@ovirt_node]# service glusterd status glusterd is stopped [root@ovirt_node]# chkconfig --list glusterd glusterd0:off 1:off 2:off 3:off 4:off 5:off 6:off [root@ovirt_node]# service glusterd start Starting glusterd:[ OK ] gluster volume create vmstore 10.22.8.46:/data/glusterfs/vmstore volume create: vmstore: success: please start the volume to access data gluster vol start vmstore volume start: vmstore: success gluster vol info Volume Name: vmstore Type: Distribute Volume ID: 5bd01043-1352-4014-88ca-e632e264d088 Status: Started Number of Bricks: 1 Transport-type: tcp Bricks: Brick1: 10.22.8.46:/data/glusterfs/vmstore [root@ovirt_node]# ls -1 /var/lib/glusterd/vols/vmstore/ bricks node_state.info trusted-vmstore-fuse.vol cksum rbstate vmstore.10.22.8.46.data-glusterfs-vmstore.vol info run vmstore-fuse.vol [root@ovirt_node]# grep gluster /etc/rwtab.d/* /etc/rwtab.d/ovirt:files /var/lib/glusterd [root@ovirt_node]# chkconfig glusterd on [root@ovirt_node]# chkconfig --list glusterd glusterd0:off 1:off 2:on3:on4:on5:on6:off I then reboot the node and see the following: [root@ovirt_node]# service glusterd status glusterd is stopped [root@ovirt_node]# chkconfig --list glusterd glusterd0:off 1:off 2:off 3:off 4:off 5:off 6:off [root@ovirt_node]# ls -l /var/lib/glusterd/vols/ total 0 No more gluster volume configuration files. I've taken a look through http://www.ovirt.org/Node_Troubleshooting#Making_changes_last_.2F_Persisting_changes but I'm unsure what needs to be done to persist this configuration. To get glusterd to start on boot, do I need to manually persist /etc/rc* files? I see files /var/lib/glusterd mentioned in /etc/rwtab.d/ovirt. Is this a list of the files/dirs that should be persisted automatically? If so, is it recursive and should it include everything in /var/lib/glusterd/vols? TIA for any help with this. Simon -Original Message- From: Ryan Barry [mailto:rba...@redhat.com] Sent: 27 May 2014 14:01 To: Fabian Deutsch; Doron Fediuck; Simon Barrett Cc: users@ovirt.org Subject: Re: [ovirt-users] Persisting glusterfs configs on an oVirt node On 05/26/2014 04:14 AM, Fabian Deutsch wrote: Am Sonntag, den 25.05.2014, 08:18 -0400 schrieb Doron Fediuck: - Original Message - From: Simon Barrett simon.barr...@tradingscreen.com To: users@ovirt.org Sent: Friday, May 23, 2014 11:29:39 AM Subject: [ovirt-users] Persisting glusterfs configs on an oVirt node I am working through the setup of oVirt node for a 3.4.1 deployment.
Re: [ovirt-users] Persisting glusterfs configs on an oVirt node
Will do. Thanks -Original Message- From: Doron Fediuck [mailto:dfedi...@redhat.com] Sent: 28 May 2014 16:17 To: Simon Barrett Cc: Fabian Deutsch; Ryan Barry; users@ovirt.org Subject: Re: [ovirt-users] Persisting glusterfs configs on an oVirt node - Original Message - From: Simon Barrett simon.barr...@tradingscreen.com To: Fabian Deutsch fdeut...@redhat.com Cc: Ryan Barry rba...@redhat.com, Doron Fediuck dfedi...@redhat.com, users@ovirt.org Sent: Wednesday, May 28, 2014 5:22:17 PM Subject: RE: [ovirt-users] Persisting glusterfs configs on an oVirt node I just wasn't sure if I was missing something in the configuration to enable this. I'll stick with the workarounds I have for now and see how it goes. Thanks again. Simon -Original Message- From: Fabian Deutsch [mailto:fdeut...@redhat.com] Sent: 28 May 2014 15:20 To: Simon Barrett Cc: Ryan Barry; Doron Fediuck; users@ovirt.org Subject: Re: [ovirt-users] Persisting glusterfs configs on an oVirt node Am Mittwoch, den 28.05.2014, 14:14 + schrieb Simon Barrett: I did a persist /var/lib/glusterd and things are looking better. The gluster config is now still in place after a reboot. As a workaround to getting glusterd running on boot, I added service glusterd start to /etc/rc.local and ran persist /etc/rc.local. It appears to be working but feels like a bit of a hack. Does anyone have any other suggestions as to the correct way to do this? Hey Simon, I was also investigating both the steps you did. And was also about to recommend them :) They are more a workaround. We basically need some patches to change the defaults on Node, to let gluster work out of the box. This would include persisting the correct paths and enabling glusterd if enabled. - fabian Thanks, Simon -Original Message- From: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On Behalf Of Simon Barrett Sent: 28 May 2014 14:12 To: Ryan Barry; Fabian Deutsch; Doron Fediuck Cc: users@ovirt.org Subject: Re: [ovirt-users] Persisting glusterfs configs on an oVirt node Thanks for the replies. I cannot get glusterd to start on boot and I lose all gluster config every reboot. The following shows what I did on the node to start glusterd, create a volume etc, followed by the state of the node after a reboot. [root@ovirt_node]# service glusterd status glusterd is stopped [root@ovirt_node]# chkconfig --list glusterd glusterd0:off 1:off 2:off 3:off 4:off 5:off 6:off [root@ovirt_node]# service glusterd start Starting glusterd:[ OK ] gluster volume create vmstore 10.22.8.46:/data/glusterfs/vmstore volume create: vmstore: success: please start the volume to access data gluster vol start vmstore volume start: vmstore: success gluster vol info Volume Name: vmstore Type: Distribute Volume ID: 5bd01043-1352-4014-88ca-e632e264d088 Status: Started Number of Bricks: 1 Transport-type: tcp Bricks: Brick1: 10.22.8.46:/data/glusterfs/vmstore [root@ovirt_node]# ls -1 /var/lib/glusterd/vols/vmstore/ bricks node_state.info trusted-vmstore-fuse.vol cksum rbstate vmstore.10.22.8.46.data-glusterfs-vmstore.vol info run vmstore-fuse.vol [root@ovirt_node]# grep gluster /etc/rwtab.d/* /etc/rwtab.d/ovirt:files /var/lib/glusterd [root@ovirt_node]# chkconfig glusterd on [root@ovirt_node]# chkconfig --list glusterd glusterd0:off 1:off 2:on3:on4:on5:on6:off I then reboot the node and see the following: [root@ovirt_node]# service glusterd status glusterd is stopped [root@ovirt_node]# chkconfig --list glusterd glusterd0:off 1:off 2:off 3:off 4:off 5:off 6:off [root@ovirt_node]# ls -l /var/lib/glusterd/vols/ total 0 No more gluster volume configuration files. I've taken a look through http://www.ovirt.org/Node_Troubleshooting#Making_changes_last_.2F_Pe rsisting_changes but I'm unsure what needs to be done to persist this configuration. To get glusterd to start on boot, do I need to manually persist /etc/rc* files? I see files /var/lib/glusterd mentioned in /etc/rwtab.d/ovirt. Is this a list of the files/dirs that should be persisted automatically? If so, is it recursive and should it include everything in /var/lib/glusterd/vols? TIA for any help with this. Simon -Original Message- From: Ryan Barry [mailto:rba...@redhat.com] Sent: 27 May 2014 14:01 To: Fabian Deutsch; Doron Fediuck; Simon Barrett Cc: users@ovirt.org Subject: Re: [ovirt-users] Persisting glusterfs configs on an oVirt node On 05/26/2014 04:14 AM, Fabian Deutsch wrote: Am Sonntag, den 25.05.2014, 08:18 -0400 schrieb Doron Fediuck: - Original
Re: [ovirt-users] Persisting glusterfs configs on an oVirt node
On 05/28/2014 10:23 AM, Fabian Deutsch wrote:
Am Mittwoch, den 28.05.2014, 14:22 + schrieb Simon Barrett:
I just wasn't sure if I was missing something in the configuration to enable
this.
I'll stick with the workarounds I have for now and see how it goes.
Thanks again.
You are welcome! :)
Simon
-Original Message-
From: Fabian Deutsch [mailto:fdeut...@redhat.com]
Sent: 28 May 2014 15:20
To: Simon Barrett
Cc: Ryan Barry; Doron Fediuck; users@ovirt.org
Subject: Re: [ovirt-users] Persisting glusterfs configs on an oVirt node
Am Mittwoch, den 28.05.2014, 14:14 + schrieb Simon Barrett:
I did a persist /var/lib/glusterd and things are looking better. The gluster
config is now still in place after a reboot.
As a workaround to getting glusterd running on boot, I added service glusterd
start to /etc/rc.local and ran persist /etc/rc.local. It appears to be working but
feels like a bit of a hack.
Does anyone have any other suggestions as to the correct way to do this?
Hey Simon,
I was also investigating both the steps you did. And was also about to
recommend them :) They are more a workaround.
We basically need some patches to change the defaults on Node, to let gluster
work out of the box.
This would include persisting the correct paths and enabling glusterd if
enabled.
- fabian
Thanks,
Simon
-Original Message-
From: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On
Behalf Of Simon Barrett
Sent: 28 May 2014 14:12
To: Ryan Barry; Fabian Deutsch; Doron Fediuck
Cc: users@ovirt.org
Subject: Re: [ovirt-users] Persisting glusterfs configs on an oVirt
node
Thanks for the replies.
I cannot get glusterd to start on boot and I lose all gluster config every
reboot.
The following shows what I did on the node to start glusterd, create a volume
etc, followed by the state of the node after a reboot.
[root@ovirt_node]# service glusterd status glusterd is stopped
[root@ovirt_node]# chkconfig --list glusterd
glusterd0:off 1:off 2:off 3:off 4:off 5:off 6:off
[root@ovirt_node]# service glusterd start Starting glusterd:[ OK ]
gluster volume create vmstore 10.22.8.46:/data/glusterfs/vmstore
volume create: vmstore: success: please start the volume to access
data
gluster vol start vmstore
volume start: vmstore: success
gluster vol info
Volume Name: vmstore
Type: Distribute
Volume ID: 5bd01043-1352-4014-88ca-e632e264d088
Status: Started
Number of Bricks: 1
Transport-type: tcp
Bricks:
Brick1: 10.22.8.46:/data/glusterfs/vmstore
[root@ovirt_node]# ls -1 /var/lib/glusterd/vols/vmstore/ bricks node_state.info
trusted-vmstore-fuse.vol cksum
rbstate
vmstore.10.22.8.46.data-glusterfs-vmstore.vol
info
run
vmstore-fuse.vol
[root@ovirt_node]# grep gluster /etc/rwtab.d/*
/etc/rwtab.d/ovirt:files /var/lib/glusterd
[root@ovirt_node]# chkconfig glusterd on [root@ovirt_node]# chkconfig --list
glusterd
glusterd0:off 1:off 2:on3:on4:on5:on6:off
I then reboot the node and see the following:
[root@ovirt_node]# service glusterd status glusterd is stopped
[root@ovirt_node]# chkconfig --list glusterd
glusterd0:off 1:off 2:off 3:off 4:off 5:off 6:off
[root@ovirt_node]# ls -l /var/lib/glusterd/vols/ total 0
I believe that we intentionally do not start glusterd, since glusterfsd
is all that's required for the engine to manage volumes, but I could be
mis-remembering this, and I don't have any real arguments to starting
glusterd at boot unless somebody speaks up against it.
No more gluster volume configuration files.
I've taken a look through
http://www.ovirt.org/Node_Troubleshooting#Making_changes_last_.2F_Persisting_changes
but I'm unsure what needs to be done to persist this configuration.
To get glusterd to start on boot, do I need to manually persist /etc/rc* files?
I see files /var/lib/glusterd mentioned in /etc/rwtab.d/ovirt. Is this a list
of the files/dirs that should be persisted automatically? If so, is it recursive and
should it include everything in /var/lib/glusterd/vols?
rwtab is a mechanism from readonly-root, which walks through the
filesystem and says copy these files to
/var/lib/stateless/writable/${path} and bind mount them back in their
original location. So you can write files there, but they don't survive
reboots on Node.
Since Node is booting from the same ramdisk every time (essentially the
ISO copied to the hard drive), this mechanism doesn't really work for
us, and persistence is a different mechanism entirely.
TIA for any help with this.
Simon
-Original Message-
From: Ryan Barry [mailto:rba...@redhat.com]
Sent: 27 May 2014 14:01
To: Fabian Deutsch; Doron Fediuck; Simon Barrett
Cc: users@ovirt.org
Subject: Re: [ovirt-users] Persisting glusterfs configs on an oVirt
node
On 05/26/2014 04:14 AM, Fabian Deutsch wrote:
Am Sonntag, den 25.05.2014, 08:18 -0400 schrieb Doron
Re: [ovirt-users] SLA : RAM scheduling
Hi Gilad, I followed your instructions, but it didn't work for me, I think for many reasons. Le 26/05/2014 16:22, Gilad Chaplik a écrit : Hi Nathanaël, happy to assist :) hope it will work in first run: 1) install the proxy and ovirtsdk. yum install -y ovirt-scheduler-proxy 2) put attached file in the right place (according to docs: .../plugins), according to the docs (http://www.ovirt.org/Features/oVirt_External_Scheduling_Proxy), the place should be plugins_path=$PYTHONPATH/ovirt_scheduler/plugins, which is should be mentionned in Scheduler conf file (/etc/ovirt/scheduler/scheduler.conf), but none of them exists in the filesystem!!! I've only found /usr/share/ovirt-scheduler-proxy/plugins for placing the python file and no scheduler.conf is present where I could change that path. make sure to edit the file with your ovirt's ip, user@domain and PW. My engine API can't be reached in http, so there is some work to do this with https. Here is what I did : according to /usr/lib/python2.6/site-packages/ovirtsdk/api.py, I add insecure=True to the chain connection = API(url='http*s*://host:port', username='user@domain', password=''*insecure='True'*) Maybe it is not enough and it would be useful to add validate_cert_chain=False... 3) restart proxy service. 3) use config tool to configure ovirt-engine: * ExternalSchedulerServiceURL=http://ip:18781/ The scheduler proxy listens to localhost:18781, none of ips that can be filled here will be reached on that port. * ExternalSchedulerEnabled=true 4) restart ovirt-engine service. 5) under configure-cluster_policy see that weight function memory_even_distribution was added (should be in manage policy units or /sth- you will see it in the main dialog as well). 6) clone/copy currernt cluster's used cluster policy (probably none - prefer it to have no balancing modules to avoid conflicts), name it 'your_name' and attach memory_even_distribution weight (you can leave it as the only weight module in weight section to avoid configuring factors). 7) replace cluster's cluster policy with newly created one. try it out and let me know how goes :-) Thanks, Gilad. If all above is tru, should be a good idea to update the wiki... - Original Message - From: Nathanaël Blanchet blanc...@abes.fr To: Gilad Chaplik gchap...@redhat.com Cc: Karli Sjöberg karli.sjob...@slu.se, users users@ovirt.org Sent: Monday, May 26, 2014 12:12:41 PM Subject: Re: [ovirt-users] SLA : RAM scheduling Hi Gilad, Yes, I'm interested in that feature, I'vebegun to read this following your advices http://www.ovirt.org/Features/oVirt_External_Scheduling_Proxy, I don't think I will have time enough to get it work quickly, I'm not experienced enough with this kind of feature, unless you help me. Le 24/05/2014 10:49, Gilad Chaplik a écrit : Hi Nathanaël, You have 2 ways to get what you're after (quick/slow): 1) install 'oVirt's external scheduling proxy', and write an extremely simple weight function that orders hosts by used memory, then add that to your cluster policy. 2) open an RFE for oVirt 3.4 to have that in (https://bugzilla.redhat.com/enter_bug.cgi?product=oVirt). let me know if you consider (1), and I'll assist. anyway I suggest you'll open an RFE for 3.5. Thanks, Gilad. - Original Message - From: Nathanaël Blanchet blanc...@abes.fr To: Karli Sjöberg karli.sjob...@slu.se Cc: users users@ovirt.org Sent: Friday, May 23, 2014 7:38:40 PM Subject: Re: [ovirt-users] SLA : RAM scheduling even distribution is for cpu only Le 23/05/2014 17:48, Karli Sjöberg a écrit : Den 23 maj 2014 17:13 skrev =?ISO-8859-1?Q?Nathana=EBl_Blanchet?= blanc...@abes.fr : Le 23/05/2014 17:11, Nathanaël Blanchet a écrit : Hello, On ovirt 3.4, is it possible to schedule vms distribution depending on host RAM availibility? Concretly, I had to manually move vms all the vms to the second host of the cluster, this lead to reach 90% occupation of memory on the destination host. When my first host has rebooted, none vms of the second host automatically migrated to the first one which had full RAM. How to make this happen? ... so as to both hosts be RAM evenly distributed... hope to be enough clear... Sounds like you just want to apply the cluster policy for even distribution. Have you assigned any policy for that cluster? /K -- Nathanaël Blanchet Supervision réseau Pôle exploitation et maintenance Département des systèmes d'information 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanc...@abes.fr ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users -- Nathanaël Blanchet Supervision réseau Pôle exploitation et maintenance Département des systèmes d'information 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanc...@abes.fr
Re: [ovirt-users] SLA : RAM scheduling
- Original Message - From: Nathanaël Blanchet blanc...@abes.fr To: Gilad Chaplik gchap...@redhat.com Cc: Karli Sjöberg karli.sjob...@slu.se, users users@ovirt.org Sent: Wednesday, May 28, 2014 6:26:16 PM Subject: Re: [ovirt-users] SLA : RAM scheduling Hi Gilad, I followed your instructions, but it didn't work for me, I think for many reasons. Le 26/05/2014 16:22, Gilad Chaplik a écrit : Hi Nathanaël, happy to assist :) hope it will work in first run: 1) install the proxy and ovirtsdk. yum install -y ovirt-scheduler-proxy 2) put attached file in the right place (according to docs: .../plugins), according to the docs (http://www.ovirt.org/Features/oVirt_External_Scheduling_Proxy), the place should be plugins_path=$PYTHONPATH/ovirt_scheduler/plugins, which is should be mentionned in Scheduler conf file (/etc/ovirt/scheduler/scheduler.conf), but none of them exists in the filesystem!!! I've only found /usr/share/ovirt-scheduler-proxy/plugins for placing the python file and no scheduler.conf is present where I could change that path. could be a bug in docs or installation - once we'll get it working for you I'll see to it. btw, change 'abs(0 - engine_host.max_scheduling_memory)' to 'sys.maxsize - engine_host.max_scheduling_memory' make sure to edit the file with your ovirt's ip, user@domain and PW. My engine API can't be reached in http, so there is some work to do this with https. Here is what I did : according to /usr/lib/python2.6/site-packages/ovirtsdk/api.py, I add insecure=True to the chain connection = API(url='http*s*://host:port', username='user@domain', password=''*insecure='True'*) Maybe it is not enough and it would be useful to add validate_cert_chain=False... Martin? 3) restart proxy service. 3) use config tool to configure ovirt-engine: * ExternalSchedulerServiceURL=http://ip:18781/ The scheduler proxy listens to localhost:18781, none of ips that can be filled here will be reached on that port. you config ovirt engine with the ip of the proxy, or I'm missing sth. ovirt communicates with the proxy and not the other way around. * ExternalSchedulerEnabled=true 4) restart ovirt-engine service. 5) under configure-cluster_policy see that weight function memory_even_distribution was added (should be in manage policy units or /sth- you will see it in the main dialog as well). 6) clone/copy currernt cluster's used cluster policy (probably none - prefer it to have no balancing modules to avoid conflicts), name it 'your_name' and attach memory_even_distribution weight (you can leave it as the only weight module in weight section to avoid configuring factors). 7) replace cluster's cluster policy with newly created one. try it out and let me know how goes :-) Thanks, Gilad. If all above is tru, should be a good idea to update the wiki... - Original Message - From: Nathanaël Blanchet blanc...@abes.fr To: Gilad Chaplik gchap...@redhat.com Cc: Karli Sjöberg karli.sjob...@slu.se, users users@ovirt.org Sent: Monday, May 26, 2014 12:12:41 PM Subject: Re: [ovirt-users] SLA : RAM scheduling Hi Gilad, Yes, I'm interested in that feature, I'vebegun to read this following your advices http://www.ovirt.org/Features/oVirt_External_Scheduling_Proxy, I don't think I will have time enough to get it work quickly, I'm not experienced enough with this kind of feature, unless you help me. Le 24/05/2014 10:49, Gilad Chaplik a écrit : Hi Nathanaël, You have 2 ways to get what you're after (quick/slow): 1) install 'oVirt's external scheduling proxy', and write an extremely simple weight function that orders hosts by used memory, then add that to your cluster policy. 2) open an RFE for oVirt 3.4 to have that in (https://bugzilla.redhat.com/enter_bug.cgi?product=oVirt). let me know if you consider (1), and I'll assist. anyway I suggest you'll open an RFE for 3.5. Thanks, Gilad. - Original Message - From: Nathanaël Blanchet blanc...@abes.fr To: Karli Sjöberg karli.sjob...@slu.se Cc: users users@ovirt.org Sent: Friday, May 23, 2014 7:38:40 PM Subject: Re: [ovirt-users] SLA : RAM scheduling even distribution is for cpu only Le 23/05/2014 17:48, Karli Sjöberg a écrit : Den 23 maj 2014 17:13 skrev =?ISO-8859-1?Q?Nathana=EBl_Blanchet?= blanc...@abes.fr : Le 23/05/2014 17:11, Nathanaël Blanchet a écrit : Hello, On ovirt 3.4, is it possible to schedule vms distribution depending on host RAM availibility? Concretly, I had to manually move vms all the vms to the second host of the cluster, this lead to reach 90% occupation of memory on the destination host. When my first host has rebooted, none vms of the second host automatically migrated to the first one which had full RAM. How to make this happen? ... so as to both hosts be RAM evenly distributed... hope to be enough
Re: [ovirt-users] Server 2012 R2 no drive found
You wrote that you migrated from 3.1 to 3.4. I imagine this is a new VM created from scratch when already in 3.4, correct? If I remember correctly 3.1 form ovirt repos was not available for CentOS 6.x, correct? So what was your upgrade path? Did you come from Dreyou repo and then updated from Dreyou repo for 3.1 to oVirt repo for 3.4? Did you verify if any package from that repo still remained and for any reason create inconsistencies with current environment? Just guessing ... Gianluca ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] post glusterfs 3.4 - 3.5 upgrade issue in ovirt (3.4.0-1.fc19): bricks unavailable
On 05/28/2014 08:36 PM, Alastair Neil wrote:
I just noticed this in the console and I don't know if it is relevant.
When I look at the General tab on the hosts under GlusterFS
Version it shows N/A.
That's not related. The GlusterFS version in UI is populated from the
getVdsCaps output from vdsm - looks like the vdsm running on your
gluster node is not returning that?
Could you share the engine.log so that we can look at how the gluster
status was interpreted and updated ? The log from the last 10 mins
should do.
thanks!
On 28 May 2014 11:03, Alastair Neil ajneil.t...@gmail.com
mailto:ajneil.t...@gmail.com wrote:
ovirt version is 3.4. I did have a slightly older version of vdsm
on gluster0 but I have updated it and the issue persists. The
compatibility version on the storage cluster is 3.3.
I checked the logs for GlusterSyncJob notifications and there are
none.
On 28 May 2014 10:19, Sahina Bose sab...@redhat.com
mailto:sab...@redhat.com wrote:
Hi Alastair,
This could be a mismatch in the hostname identified in ovirt
and gluster.
You could check for any exceptions from GlusterSyncJob in
engine.log.
Also, what version of ovirt are you using. And the
compatibility version of your cluster?
On 05/28/2014 12:40 AM, Alastair Neil wrote:
Hi thanks for the reply. Here is an extract from a grep I ran
on the vdsm log grepping for the volume name vm-store. It
seems to indicate the bricks are ONLINE.
I am uncertain how to extract meaningful information from the
engine.log can you provide some guidance?
Thanks,
Alastair
Thread-100::DEBUG::2014-05-27
15:01:06,335::BindingXMLRPC::1067::vds::(wrapper) client
[129.174.94.239]::call volumeStatus with ('vm-store', '',
'') {}
Thread-100::DEBUG::2014-05-27
15:01:06,356::BindingXMLRPC::1074::vds::(wrapper) return
volumeStatus with {'volumeStatus': {'bricks': [{'status':
'ONLINE', 'brick': 'gluster0:/export/brick0', 'pid':
'2675', 'port': '49158', 'hostuuid':
'bcff5245-ea86-4384-a1bf-9219c8be8001'}, {'status':
'ONLINE', 'brick': 'gluster1:/export/brick4/vm-store',
'pid': '2309', 'port': '49158', 'hostuuid':
'54d39ae4-91ae-410b-828c-67031f3d8a68'}], 'nfs':
[{'status': 'ONLINE', 'hostname': '129.174.126.56',
'pid': '27012', 'port': '2049', 'hostuuid':
'54d39ae4-91ae-410b-828c-67031f3d8a68'}, {'status':
'ONLINE', 'hostname': 'gluster0', 'pid': '12875', 'port':
'2049', 'hostuuid':
'bcff5245-ea86-4384-a1bf-9219c8be8001'}], 'shd':
[{'status': 'ONLINE', 'hostname': '129.174.126.56',
'pid': '27019', 'hostuuid':
'54d39ae4-91ae-410b-828c-67031f3d8a68'}, {'status':
'ONLINE', 'hostname': 'gluster0', 'pid': '12882',
'hostuuid': 'bcff5245-ea86-4384-a1bf-9219c8be8001'}],
'name': 'vm-store'}, 'status': {'message': 'Done',
'code': 0}}
Thread-16::DEBUG::2014-05-27
15:01:15,339::fileSD::225::Storage.Misc.excCmd::(getReadDelay)
'/bin/dd iflag=direct
if=/rhev/data-center/mnt/glusterSD/gluster0:vm-store/6d637c7f-a4ab-4510-a0d9-63a04c55d6d8/dom_md/metadata
bs=4096 count=1' (cwd None)
Thread-16::DEBUG::2014-05-27
15:01:25,381::fileSD::225::Storage.Misc.excCmd::(getReadDelay)
'/bin/dd iflag=direct
if=/rhev/data-center/mnt/glusterSD/gluster0:vm-store/6d637c7f-a4ab-4510-a0d9-63a04c55d6d8/dom_md/metadata
bs=4096 count=1' (cwd None)
Thread-16::DEBUG::2014-05-27
15:01:35,423::fileSD::225::Storage.Misc.excCmd::(getReadDelay)
'/bin/dd iflag=direct
if=/rhev/data-center/mnt/glusterSD/gluster0:vm-store/6d637c7f-a4ab-4510-a0d9-63a04c55d6d8/dom_md/metadata
bs=4096 count=1' (cwd None)
Thread-16::DEBUG::2014-05-27
15:01:45,465::fileSD::225::Storage.Misc.excCmd::(getReadDelay)
'/bin/dd iflag=direct
if=/rhev/data-center/mnt/glusterSD/gluster0:vm-store/6d637c7f-a4ab-4510-a0d9-63a04c55d6d8/dom_md/metadata
bs=4096 count=1' (cwd None)
Thread-16::DEBUG::2014-05-27
15:01:55,507::fileSD::225::Storage.Misc.excCmd::(getReadDelay)
'/bin/dd iflag=direct
if=/rhev/data-center/mnt/glusterSD/gluster0:vm-store/6d637c7f-a4ab-4510-a0d9-63a04c55d6d8/dom_md/metadata
bs=4096 count=1' (cwd None)
Thread-16::DEBUG::2014-05-27
15:02:05,549::fileSD::225::Storage.Misc.excCmd::(getReadDelay)
'/bin/dd iflag=direct
Re: [ovirt-users] Server 2012 R2 no drive found
Hi Gianluca, Quite correct on all counts, it was migrated from dreyou 3.1 and it was a new vm created in 3.4, so there could be inconsistencies from the upgrade but I've got no idea where to even start in trying to find them. I'll verify all the packages have been upgraded tomorrow and check from there. Thanks for the assistance. Regards. Neil Wilson On 28 May 2014 6:06 PM, Gianluca Cecchi gianluca.cec...@gmail.com wrote: You wrote that you migrated from 3.1 to 3.4. I imagine this is a new VM created from scratch when already in 3.4, correct? If I remember correctly 3.1 form ovirt repos was not available for CentOS 6.x, correct? So what was your upgrade path? Did you come from Dreyou repo and then updated from Dreyou repo for 3.1 to oVirt repo for 3.4? Did you verify if any package from that repo still remained and for any reason create inconsistencies with current environment? Just guessing ... Gianluca ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Selecting which host to run a VM on using ovirt-shell
Hi List, As per the subject, I have a desire to start a lot of VMs after a maintenance shutdown of our infrastructure and I would like to either evenly spread the load among the hosts or to restart the VMs on the host they were on before shutdown. Getting the list using ovirt-shell and transforming that to a 'action vm ABC start' is no problem but I can't find if its possible to specify the host to run the VM on. Is this possible using ovirt-shell and can someone point me to some docs? (Have read (all) the rhevm docs but either overlooked or its not there) Regards, Joop ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Selecting which host to run a VM on using ovirt-shell
Hi Joop, I also have thought about this because it's nice to have in design of your network. Didn't we discuss this earlier where you came up with some API script you were working on to start these VM's in this was ? Actually we should need something like start VM always here if host is online on the setup tabs. Cheers, Matt 2014-05-28 21:06 GMT+02:00 Joop jvdw...@xs4all.nl: Hi List, As per the subject, I have a desire to start a lot of VMs after a maintenance shutdown of our infrastructure and I would like to either evenly spread the load among the hosts or to restart the VMs on the host they were on before shutdown. Getting the list using ovirt-shell and transforming that to a 'action vm ABC start' is no problem but I can't find if its possible to specify the host to run the VM on. Is this possible using ovirt-shell and can someone point me to some docs? (Have read (all) the rhevm docs but either overlooked or its not there) Regards, Joop ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Selecting which host to run a VM on using ovirt-shell SOLVED
Joop wrote: Hi List, As per the subject, I have a desire to start a lot of VMs after a maintenance shutdown of our infrastructure and I would like to either evenly spread the load among the hosts or to restart the VMs on the host they were on before shutdown. Getting the list using ovirt-shell and transforming that to a 'action vm ABC start' is no problem but I can't find if its possible to specify the host to run the VM on. Is this possible using ovirt-shell and can someone point me to some docs? (Have read (all) the rhevm docs but either overlooked or its not there) Answering my own question: The help describes something about parent identifiers and references the examples below but there is no example of how to use parent identifiers. Extrapolating from disks belonging to a vm a reasoned that vms belong to a host so did 'list hosts' and copied the id. It says 'An object identifier is an option of the form '--typeid id' but it looks this is confusing, atleast to me. This is what worked: action vm VM_NAME start --type ID_OF_HOST The help has 2x id which confuses me. Joop ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Selecting which host to run a VM on using ovirt-shell SOLVED
Joop, I think you need to check if that is the same as Start Once , which I think it is. This does only start it there for once, you might want to set a default server too. 2014-05-28 22:57 GMT+02:00 Joop jvdw...@xs4all.nl: Joop wrote: Hi List, As per the subject, I have a desire to start a lot of VMs after a maintenance shutdown of our infrastructure and I would like to either evenly spread the load among the hosts or to restart the VMs on the host they were on before shutdown. Getting the list using ovirt-shell and transforming that to a 'action vm ABC start' is no problem but I can't find if its possible to specify the host to run the VM on. Is this possible using ovirt-shell and can someone point me to some docs? (Have read (all) the rhevm docs but either overlooked or its not there) Answering my own question: The help describes something about parent identifiers and references the examples below but there is no example of how to use parent identifiers. Extrapolating from disks belonging to a vm a reasoned that vms belong to a host so did 'list hosts' and copied the id. It says 'An object identifier is an option of the form '--typeid id' but it looks this is confusing, atleast to me. This is what worked: action vm VM_NAME start --type ID_OF_HOST The help has 2x id which confuses me. Joop ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] How do i use local storage of hosts with ovirt?
Um I missed the earlier part of this thread but I can tell you from experience not using shared storage of one kind or an other for virtualization is always a mistake you will regret latter. Its a common (almost default) mistake people who are just getting started with virtualization make. Fibre (which includes optical fiber and copper using the same protocols ) channel at best or a pNFS or Gluster solution will server you a lot better as long as you have a decent number of spindles and a lot of ram for cache on the storage servers/controllers. -- Sent from my HP Pre3On May 28, 2014 20:51, Grant Tailor therealwebg...@gmail.com wrote: I plan NOT to use shared storage or network storage and will be using local storage of hosts to provision storage for VMsHow do i do this?For example in this screenshot, no way to configure local storage Thanks ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] How do i use local storage of hosts with ovirt?
This is for a private cloud and no thanks..i am okay with my local storage..have the local storage in RAID 1 and have a dedicated backup server with bacula doing continuous backup. Having a network storage complicates things, and i dont want it..at least not now...maybe in 3 years i may want it but not now for what i am doing. So anyone willing to help with how to setup hosts to use local storage? Thanks On Wed, May 28, 2014 at 9:11 PM, Paul Robert Marino prmari...@gmail.comwrote: Um I missed the earlier part of this thread but I can tell you from experience not using shared storage of one kind or an other for virtualization is always a mistake you will regret latter. Its a common (almost default) mistake people who are just getting started with virtualization make. Fibre (which includes optical fiber and copper using the same protocols ) channel at best or a pNFS or Gluster solution will server you a lot better as long as you have a decent number of spindles and a lot of ram for cache on the storage servers/controllers. -- Sent from my HP Pre3 -- On May 28, 2014 20:51, Grant Tailor therealwebg...@gmail.com wrote: I plan NOT to use shared storage or network storage and will be using local storage of hosts to provision storage for VMs How do i do this? For example in this screenshot, no way to configure local storage Thanks ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] How do i use local storage of hosts with ovirt?
This is why i like Ganeti because they are the only one that understand there is a niche and support for clusters using local storage of hosts. I mean not everyone wants a Shared/network storage for crying out loud. On Wed, May 28, 2014 at 9:11 PM, Paul Robert Marino prmari...@gmail.comwrote: Um I missed the earlier part of this thread but I can tell you from experience not using shared storage of one kind or an other for virtualization is always a mistake you will regret latter. Its a common (almost default) mistake people who are just getting started with virtualization make. Fibre (which includes optical fiber and copper using the same protocols ) channel at best or a pNFS or Gluster solution will server you a lot better as long as you have a decent number of spindles and a lot of ram for cache on the storage servers/controllers. -- Sent from my HP Pre3 -- On May 28, 2014 20:51, Grant Tailor therealwebg...@gmail.com wrote: I plan NOT to use shared storage or network storage and will be using local storage of hosts to provision storage for VMs How do i do this? For example in this screenshot, no way to configure local storage Thanks ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
