[
https://issues.apache.org/jira/browse/GUACAMOLE-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15953840#comment-15953840
]
Nick Couchman commented on GUACAMOLE-189:
-----------------------------------------
This particular ticket doesn't necessarily deal with high availability or
failing from one guacd server to another, just being able to assign a
connection to a particular guacd instance, as might be necessary to overcome
firewall issues and deal with distributed networks, and as is necessary for
implementing the X.org driver.
You're asking about two other things, which are probably good things to
implement, but separate from this particular ticket and probably separate from
each other:
- Ability to load-balance or at least fail over from one guacd instance to
another. guacd doesn't really care about where the client is getting its
connection information (MySQL, PostgreSQL, LDAP, etc.), it just receives the
Guacamole protocol information from the client and processes the translation of
the Guacamole protocol to whatever back-end you're connecting to (SSH, RDP,
etc.).
- Ability to load-balance the Guacamole client and share sessions and
configuration information between multiple instances of the client. This is
likely already possible to some degree, although I'm not entirely sure how safe
it is. There are some things that probably wouldn't work correctly - like
tracking active connections - and some others that might be unsafe - like
multiple admins editing the same connections.
Anyway, probably worth opening a couple of separate tickets for these issues.
> 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)
