Hide Forgot
Description of problem: - have 2 instances of web-admin opened - make one of the instances in focus - perform action - like: deactivate storage domain - web-admin is not refreshed on second window (out of focus) till it being in focused again in user-portal - we had a refresh time of 60s for such operation.
I heard, that due to bandwidth optimization only focused webadmin refreshed itself. Could you please ad an option to override this behaviour? I can imagine two layered window e.g. when adding host there & waiting forever (as I actually did). Also I can imagine the poor guy on monitoring position with more application than webadmin in front of him - each minute clicking into grid to make sure he's actual state. Thank you for consideration.
Besides the reasons described in comment #1, an option to turn on auto-refresh globally will be highly appreciated also for automated testing purposes. Now, QE run automation on dedicated Selenium server, where multiple browser instances can operate in parallel at the same time. Unfortunately, due to this behavior, the number of concurrent instances had to be cut down to one, so more tests have to wait in a queue. This way the testing process takes much more time than running it in parallel.
Guys, this is a feature :) it works like this: When the application window is not in focus, for example: - you switched the active window focus from browser to other application - or you switched the current browser tab from WebAdmin to other tab then the auto-refresh feature is disabled for all WebAdmin data grids (each grid has its own timer which periodically polls the server for fresh data, and the poll frequency can be customized via refresh drop-down menu). When the application window gains focus again, the auto-refresh feature is enabled. The motivation behind this is to reduce client/server bandwidth at times when the application is not actively used (not in focus). I understand that this might not be what everyone expects. Maybe we could add some checkbox (hidden under some "Login Options" slide-out panel) to control this behavior globally for the application?
(In reply to comment #3) > Guys, this is a feature :) it works like this: > > When the application window is not in focus, for example: > - you switched the active window focus from browser to other application > - or you switched the current browser tab from WebAdmin to other tab > > then the auto-refresh feature is disabled for all WebAdmin data grids (each > grid has its own timer which periodically polls the server for fresh data, and > the poll frequency can be customized via refresh drop-down menu). > > When the application window gains focus again, the auto-refresh feature is > enabled. The motivation behind this is to reduce client/server bandwidth at > times when the application is not actively used (not in focus). > > I understand that this might not be what everyone expects. Maybe we could add > some checkbox (hidden under some "Login Options" slide-out panel) to control > this behavior globally for the application? I think that an extra option on login screen is a good idea. And also good compromise between reduction of network bandwidth load and use cases, where permanently enabled auto-refresh comes really useful.
Created attachment 573667 [details] WebAdmin new login option
Created attachment 573668 [details] UserPortal new login option
Patch submitted to Gerrit: http://gerrit.ovirt.org/3197 I've attached two screenshots, one for WebAdmin and one for UserPortal, to demonstrate the checkbox used to control refresh behavior.
I am not sure if people would understand what this check is used for and/or ever un-check it. We should keep in mind what is good for a typical use case (automated GUI tests launching multiple browsers in parallel on same machine is not a typical use case). I suggest to remove the check-box and have the refresh rate set to the minimal one when out of focus (just like the BZ subject actually suggests). As the next step, in order to also consider less typical use-cases, we can have all focus-refresh-rates and out-of-focus-refresh-rate as configurable/part of user preferences (you can open a BZ on that).
Agreed, I will update the patch in the following way: - revert UI changes (no additional check-box at the login screen) - apply minimal refresh rate [60s] when the application is out of focus I've discussed this with Pavel today, QE folks might open an RFE to customize the "out-of-focus-refresh-rate".
(In reply to comment #9) > Agreed, I will update the patch in the following way: > - revert UI changes (no additional check-box at the login screen) > - apply minimal refresh rate [60s] when the application is out of focus > > I've discussed this with Pavel today, QE folks might open an RFE to customize > the "out-of-focus-refresh-rate". That's right. New RFE opened: https://bugzilla.redhat.com/show_bug.cgi?id=811172
New patch set submitted to Gerrit: http://gerrit.ovirt.org/3197
The above patch set has been merged upstream.
closing ON_QA bugs as oVirt 3.1 was released: http://www.ovirt.org/get-ovirt/