guacamole-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thiago dos Santos Nunes (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GUACAMOLE-189) Add support for per-connection guacd
Date Mon, 03 Apr 2017 15:56:41 GMT

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

Thiago dos Santos Nunes commented on GUACAMOLE-189:
---------------------------------------------------

In this ticket we will have a option to create a High availability guacamole cluster? 

Many guacd and/or many tomcat to rely.

If we have the option to create an environment where we have several guacd and they count
the connections between them.

For example:

An environment with 2 tomcats of frontend and 2 guacd of backend and 1 MySQL of integrated
bank between them. It´s will be a VERY GREAT OPTION.

> Add support for per-connection guacd
> ------------------------------------
>
>                 Key: GUACAMOLE-189
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-189
>             Project: Guacamole
>          Issue Type: Improvement
>          Components: guacamole, guacamole-ext
>            Reporter: Michael Jumper
>            Assignee: Michael Jumper
>             Fix For: 0.9.13-incubating
>
>
> The web application currently assumes that one guacd will be used to provide access to
all connections. This assumption fails if:
> * Multiple guacd instances are spread out across different networks
> * Another component implementing the Guacamole protocol is being used instead of guacd
on a per-connection basis (like the X.Org driver of GUACAMOLE-168)
> Though no change is needed to the core APIs, as no such assumption is made at that level,
the web application and extension API should be modified such that the guacd (or other Guacamole
proxy) applicable to a connection can be specified explicitly for that connection.



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

Mime
View raw message