Bug 8542 - Load details in tlwebadm are no longer relevant
Summary: Load details in tlwebadm are no longer relevant
Status: CLOSED FIXED
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Web Administration (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: 4.19.0
Assignee: Pierre Ossman
URL:
Keywords: prosaic, samuel_tester
Depends on:
Blocks: 4429
  Show dependency treegraph
 
Reported: 2025-03-12 10:08 CET by Pierre Ossman
Modified: 2025-03-21 09:43 CET (History)
1 user (show)

See Also:
Acceptance Criteria:
MUST: * tlwebadm doesn't rely on any information that will be removed in bug 4429 SHOULD: * tlwebadm shows all information used for the new load balancing from bug 4429


Attachments

Description Pierre Ossman cendio 2025-03-12 10:08:02 CET
We're simplifying the load balancer in bug 4429, which means there won't be the same kind of load details available. The UI in tlwebadm needs to be updated to reflect that.
Comment 4 Pierre Ossman cendio 2025-03-12 16:56:09 CET
Updated to only show the number of ThinLinc users on each agent (which is the planned load balancing criteria for bug 4429). Since we no longer track system users in any way, I opted to completely remove the 

It still also shows if an agent is down as it is not yet decided how/if that will be handled.

Everything else has been nuked.

> MUST:
> 
>  * tlwebadm doesn't rely on any information that will be removed in bug 4429

Yup, it's gone.

> SHOULD:
> 
>  * tlwebadm shows all information used for the new load balancing from bug 4429

Yes, it shows the number of ThinLinc users.
Comment 5 Samuel Mannehed cendio 2025-03-13 12:11:20 CET
I get a Error code: 500 and a traceback in the log when trying to view the status/load page. I installed server build 3945 from jenkins on a Fedora 41.
Comment 7 Samuel Mannehed cendio 2025-03-21 09:43:53 CET
Tested build 3953 on Fedora 41. Web Admin now only list number of logged-in ThinLinc users for each agent. There is no longer an detailed view to open for an agent, since all of that information will be obsolete.

I checked the following scenarios:

* single subcluster with multiple agents
* multiple subclusters
* working agent with sessions
* agent that can't be reached (DOWN)
* the "Users" number updates when a new ThinLinc session is created
* the "Users" number updates when a ThinLinc session is terminated

The commits look good. The acceptance criteria are both sane and are fulfilled.

Note You need to log in before you can comment on or make changes to this bug.