[
https://issues.apache.org/jira/browse/GUACAMOLE-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042016#comment-16042016
]
Michael Jumper commented on GUACAMOLE-102:
------------------------------------------
{quote}
So, this, plus a permission specifically for updating connection weight should
do the trick, right?
{quote}
Yes, theoretically, though I'm not sure what form that would need to take. I'm
wary of adding an actual new type of permission to the extension API. It'd make
more sense if Guacamole's permission model was ACL-based, but it was based off
a traditional UNIX-style permission scheme. The database auth could certainly
do whatever it likes with its own permissions, but exposing those permissions
such that they are manageable via the UI would be tricky.
Maybe worth some discussion on the mailing list. Same probably for whether
implementing our own resource-tracking mechanism is a separate issue vs.
blocking.
> 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)
