[
https://issues.apache.org/jira/browse/GUACAMOLE-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16039957#comment-16039957
]
Michael Jumper edited comment on GUACAMOLE-102 at 6/7/17 1:23 AM:
------------------------------------------------------------------
{quote}
Next steps, I think, are:
* Look at implementing additional algorithms - Round Robin and Weighted Round
Robin shouldn't be too hard to do. I'm not entirely sure where the proper place
is to start to break out the code for different LB algorithms - any thoughts?
{quote}
I would say, as far as this issue is concerned, scope is satisfied. RR and WRR
sound like great ideas, but that should probably be a separate issue.
I think the only thing remaining here before this issue can be reasonably
closed is the documentation for the new column in the manual
(http://guacamole.incubator.apache.org/doc/gug/jdbc-auth.html#jdbc-auth-schema).
{quote}
* Still have not settled on the best way for dynamically updating the weights
of the individual connections. Does this live within the Guacamole Client code?
Or is it a separate daemon or piece of code? Or maybe provide REST endpoints in
the Guacamole Client code for updating the weights, but leave it up to the end
user to implement the load checking/updating? Any opinions here?
{quote}
I think the only way would be for the service measurement component to live
separately, in this case updating the connection weights in the database based
on some measurement of load.
REST endpoints sound like a good option (and is possible now as of
GUACAMOLE-289), but that would need to be done carefully. You wouldn't want
unauthorized services/users to be able to update things.
was (Author: mike.jumper):
{quote}
Next steps, I think, are:
* Look at implementing additional algorithms - Round Robin and Weighted Round
Robin shouldn't be too hard to do. I'm not entirely sure where the proper place
is to start to break out the code for different LB algorithms - any thoughts?
{quote}
I would say, as far as this issue is concerned, scope is satisfied. RR and WRR
sound like great ideas, but that should probably be a separate issue.
I think the only thing remaining here before this issue can be reasonably
closed is the documentation for the new column in the manual
(http://guacamole.incubator.apache.org/doc/gug/jdbc-auth.html#jdbc-auth-schema).
{quote}
Still have not settled on the best way for dynamically updating the weights of
the individual connections. Does this live within the Guacamole Client code? Or
is it a separate daemon or piece of code? Or maybe provide REST endpoints in
the Guacamole Client code for updating the weights, but leave it up to the end
user to implement the load checking/updating? Any opinions here?
{quote}
I think the only way would be for the service measurement component to live
separately, in this case updating the connection weights in the database based
on some measurement of load.
REST endpoints sound like a good option (and is possible now as of
GUACAMOLE-289), but that would need to be done carefully. You wouldn't want
unauthorized services/users to be able to update things.
> 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
> Assignee: Nick Couchman
> 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)
