Ceph » mgr » Dashboard

Good idea, I agree to both the overall idea and the implementation plan!

Hi Lenz and Ernesto,
I want to work on this issue,
Just one question, The default value for the refresh interval right now is 5 seconds which is the default interval for other services like summary service etc;
When you say, come from a single setting, I assume that you want to have a single interval variable which can be easily modified by the admin using an input. (Changing the selector to an input which will change the refresh interval)
Or are we trying to add this input to an already existing form?
Also, I cannot find a way to change the refresh interval of the summary service. Do we want to change that also?

Pranav Kulshrestha wrote:

Hi Lenz and Ernesto,
I want to work on this issue,
Just one question, The default value for the refresh interval right now is 5 seconds which is the default interval for other services like summary service etc;
When you say, come from a single setting, I assume that you want to have a single interval variable which can be easily modified by the admin using an input. (Changing the selector to an input which will change the refresh interval)
Or are we trying to add this input to an already existing form?
Also, I cannot find a way to change the refresh interval of the summary service. Do we want to change that also?

Hi Pranav,

Currently every Angular service polling the backend REST API features its own method of polling and period (recursive with setInterval, iterative with rxjs.timer, ...). To allow users easily tune polling interval for all services you would probably need to:

• Replace the different polling implementations & polling periods (5 secs, 10, 20, ...) with a single timing source. This could be, for example, a single Rxjs source/subject provided by a service, from which every service takes the 'master clock' reference. But there could exist other approaches.
• A few services (as the one you mention, SummaryService) can be a bit tricky, since they might need some 'refactoring', but don't be afraid of breaking it. There should be enough unit test and e2e test to detect any breaking change (and if not, that's also a good finding).
• Once all polling services are fed with the same timing source, you'd need to come up with a way of making that source period 'tunable' and expose that 'tunability' in a front-end component.
• Some questions remain open and might lead you to different solutions/approaches:
  • Is this setting somehow saved, so that the same user sees the last setting?
  • If it's persisted, where is that setting stored? Front-end? Back-end?

Let me know if you still have any questions!