guacamole-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Couchman (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GUACAMOLE-102) Load balancing based on resource
Date Wed, 07 Jun 2017 14:05:18 GMT

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

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

{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.
{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.  If the rest of the request is out of scope of the Guacamole Client,
that's fine.

I'll submit a new issue and PR once I have RR AND WRR algorithms implemented so we can add
those.

{quote}
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}
Done, and PR submitted on the manual for that.

{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.
{quote}
That makes the most sense to me, too - seems like adding it to the client itself, though possible,
is a little out of scope of the client.

{quote}
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.
{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?  Or would that have to be implemented?  Also,
I was thinking about some sort of additional permission added for updating the connection
weight field such that you could have a specific user identified inside the JDBC authentication
extension, that would authenticate directly to the API and then would have permission to update
that field and only that field?

> 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)

Mime
View raw message