[jira] [Commented] (GUACAMOLE-102) Load balancing based on resource

["Nick Couchman (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/GUACAMOLE-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032330#comment-16032330 ] 

Nick Couchman commented on GUACAMOLE-102:
-----------------------------------------

Well, I went ahead and took a stab at an implementation of a WLC algorithm, here.  PR 161 has been opened up in the incubator-guacamole-client repo for this change.  I expect there are a LOT of things that need tweaking before that code actually gets merged, but it's a start.  Maybe :-).

Anyway, looking forward past the basic WLC implementation, there are a few things I'd like to do:
- Implement multiple load balancing algorithms, as described earlier in this issue, and give the user control over which ones gets used.  Should be able to basically pull out that compare() method into a separate class and then call whichever method is appropriate for the selected algorithm.
- Still have to figure out the best way to dynamically update the connection weight and implement some default methods for that.  At the moment the only real way to do this is to have something update the database directly...which may end up being an acceptable long-term route, but probably want some other options, too.

> Load balancing based on resource
> --------------------------------
>
>                 Key: GUACAMOLE-102
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-102
>             Project: Guacamole
>          Issue Type: New Feature
>          Components: guacamole, guacamole-auth-jdbc, guacamole-auth-jdbc-mysql, guacamole-auth-jdbc-postgresql, guacamole-client, RDP
>    Affects Versions: 0.9.10-incubating
>         Environment: CentOS Linux 7 (Core)
> Linux 3.10.0-327.10.1.el7.x86_64
>            Reporter: Werner Novak
>            Priority: Minor
>
> Implementation of an resource based (CPU, Memory, I/O, Loggedin User) balancing in opposite to the current implemented guacamole connections round robin. This is needed because of an large RDP infrastructure (300+ TS), where the terminal server been accessed via multiple RDP load balancers during migration.
> A prototype has been developed in a guacamole fork
> https://github.com/wnovak/incubator-guacamole-client.git



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)