Re: [ovirt-users] GUI node detail long delay

2017-02-07 Thread Sahina Bose
[Adding users] On Tue, Feb 7, 2017 at 7:52 PM, p...@email.cz wrote: > Dear Sahina, > > *Q:* > "Any reason why the Arbiter node will not be managed by oVirt? > > *A:* > 1) The arbiter node ( which running this oVirt too ) is not powerfull in > CPU/mem/lan sources to run VMs .

Re: [ovirt-users] GUI node detail long delay

2017-02-07 Thread Sahina Bose
On Mon, Feb 6, 2017 at 6:36 PM, p...@email.cz wrote: > Hello everybody, > > We are using oVirt Engine Version: 4.0.6.3-1.el7.centos on centos 7.3 > with gluster replica 3 arbiter = (1+1)+1 > > I'm confused with GUI delaying - if node details are wanted ( cluster -> > nodes ->

[ovirt-users] GUI node detail long delay

2017-02-06 Thread p...@email.cz
Hello everybody, We are using oVirt Engine Version: 4.0.6.3-1.el7.centos on centos 7.3 with gluster replica 3 arbiter = (1+1)+1 I'm confused with GUI delaying - if node details are wanted ( cluster -> nodes -> node detail = click on node raw ) then request generate over 10 min delay to