[
https://issues.apache.org/jira/browse/GUACAMOLE-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16041087#comment-16041087
]
Michael Jumper commented on GUACAMOLE-102:
------------------------------------------
{quote}
Okay - I wasn't sure, since the original request was "implementation of
resource-based balancing" - which isn't entirely satisfied. The framework has
been created for this to happen with the addition of the weight field, but it
doesn't totally satisfy the request to implement resource-based balancing.
{quote}
How so?
{quote}
Yes, definitely need to make sure security is addressed. With the current API
is it possible to authenticate individual requests - like passing either
username/password in a header, or passing a digest or authorization header?
{quote}
Yes, REST resources will inherently require an authenticated Guacamole session
if they are exposed via {{UserContext.getResource()}}.
> 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)
