From paf1 at email.cz Tue Jun 9 09:02:42 2015
Content-Type: multipart/mixed; boundary="===============3304940215006451966=="
MIME-Version: 1.0
From: paf1 at email.cz
To: users at ovirt.org
Subject: [ovirt-users] oVirt timeouts
Date: Tue, 09 Jun 2015 15:02:39 +0200
Message-ID: <5576E3EF.7000103@email.cz>
--===============3304940215006451966==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
This is a multi-part message in MIME format.
--------------090402070806020609030609
Content-Type: text/plain; charset=3Dutf-8; format=3Dflowed
Content-Transfer-Encoding: 7bit
Hello,
pls, howto change oVirt timeouts for status :
1) node ( brick) is power down / up
2) volume status for node(brick) is up/down
They are too long ( I'm expecting a few sec. not a lot of minutes )
If it has some spacial reason, let me know about, pls.
regs.
Pa.
--------------090402070806020609030609
Content-Type: text/html; charset=3Dutf-8
Content-Transfer-Encoding: 8bit
Hello,
pls, howto=C2=A0 change oVirt timeouts for status=C2=A0 :
1) node ( brick) is power down / up
2) volume status for node(brick) is up/down
They are too long ( I'm expecting a few sec. not a lot of minutes )
If it has some spacial reason, let me know about, pls.
regs.
Pa.
--------------090402070806020609030609--
--===============3304940215006451966==
Content-Type: multipart/alternative
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="attachment.bin"
VGhpcyBpcyBhIG11bHRpLXBhcnQgbWVzc2FnZSBpbiBNSU1FIGZvcm1hdC4KLS0tLS0tLS0tLS0t
LS0wOTA0MDIwNzA4MDYwMjA2MDkwMzA2MDkKQ29udGVudC1UeXBlOiB0ZXh0L3BsYWluOyBjaGFy
c2V0PXV0Zi04OyBmb3JtYXQ9Zmxvd2VkCkNvbnRlbnQtVHJhbnNmZXItRW5jb2Rpbmc6IDdiaXQK
CkhlbGxvLAoKcGxzLCBob3d0byAgY2hhbmdlIG9WaXJ0IHRpbWVvdXRzIGZvciBzdGF0dXMgIDoK
MSkgbm9kZSAoIGJyaWNrKSBpcyBwb3dlciBkb3duIC8gdXAKMikgdm9sdW1lIHN0YXR1cyBmb3Ig
bm9kZShicmljaykgaXMgdXAvZG93bgoKVGhleSBhcmUgdG9vIGxvbmcgKCBJJ20gZXhwZWN0aW5n
IGEgZmV3IHNlYy4gbm90IGEgbG90IG9mIG1pbnV0ZXMgKQpJZiBpdCBoYXMgc29tZSBzcGFjaWFs
IHJlYXNvbiwgbGV0IG1lIGtub3cgYWJvdXQsIHBscy4KCnJlZ3MuClBhLgoKLS0tLS0tLS0tLS0t
LS0wOTA0MDIwNzA4MDYwMjA2MDkwMzA2MDkKQ29udGVudC1UeXBlOiB0ZXh0L2h0bWw7IGNoYXJz
ZXQ9dXRmLTgKQ29udGVudC1UcmFuc2Zlci1FbmNvZGluZzogOGJpdAoKPGh0bWw+CiAgPGhlYWQ+
CgogICAgPG1ldGEgaHR0cC1lcXVpdj0iY29udGVudC10eXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7
IGNoYXJzZXQ9dXRmLTgiPgogIDwvaGVhZD4KICA8Ym9keSB0ZXh0PSIjMDAwMDY2IiBiZ2NvbG9y
PSIjRkZGRkZGIj4KICAgIEhlbGxvLCA8YnI+CiAgICA8YnI+CiAgICBwbHMsIGhvd3RvwqAgY2hh
bmdlIG9WaXJ0IHRpbWVvdXRzIGZvciBzdGF0dXPCoCA6PGJyPgogICAgMSkgbm9kZSAoIGJyaWNr
KSBpcyBwb3dlciBkb3duIC8gdXA8YnI+CiAgICAyKSB2b2x1bWUgc3RhdHVzIGZvciBub2RlKGJy
aWNrKSBpcyB1cC9kb3duIDxicj4KICAgIDxicj4KICAgIFRoZXkgYXJlIHRvbyBsb25nICggSSdt
IGV4cGVjdGluZyBhIGZldyBzZWMuIG5vdCBhIGxvdCBvZiBtaW51dGVzICk8YnI+CiAgICBJZiBp
dCBoYXMgc29tZSBzcGFjaWFsIHJlYXNvbiwgbGV0IG1lIGtub3cgYWJvdXQsIHBscy48YnI+CiAg
ICA8YnI+CiAgICByZWdzLjxicj4KICAgIFBhLjxicj4KICA8L2JvZHk+CjwvaHRtbD4KCi0tLS0t
LS0tLS0tLS0tMDkwNDAyMDcwODA2MDIwNjA5MDMwNjA5LS0K
--===============3304940215006451966==--
From jbelka at redhat.com Fri Jun 19 04:59:10 2015
Content-Type: multipart/mixed; boundary="===============1199131265128402259=="
MIME-Version: 1.0
From: Jiri Belka
To: users at ovirt.org
Subject: Re: [ovirt-users] oVirt timeouts
Date: Fri, 19 Jun 2015 04:58:55 -0400
Message-ID: <1628152610.20380275.1434704335332.JavaMail.zimbra@redhat.com>
In-Reply-To: 5576E3EF.7000103@email.cz
--===============1199131265128402259==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
> pls, howto change oVirt timeouts for status :
> 1) node ( brick) is power down / up
> 2) volume status for node(brick) is up/down
> =
> They are too long ( I'm expecting a few sec. not a lot of minutes )
> If it has some spacial reason, let me know about, pls.
I don't do glusterfs here but see *_options tables in the DB
or engine-config -a output.
j.
--===============1199131265128402259==--