[ 
https://issues.apache.org/jira/browse/GUACAMOLE-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nick Couchman updated GUACAMOLE-283:
------------------------------------
    Priority: Minor  (was: Major)

> HA in Guacamole
> ---------------
>
>                 Key: GUACAMOLE-283
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-283
>             Project: Guacamole
>          Issue Type: New Feature
>          Components: guacamole-client, guacamole-server
>            Reporter: Thiago dos Santos Nunes
>            Priority: Minor
>
> A great feature for guacamole would be high availability both on the client 
> (mainly) and on the server.
> In the client the ideal would be to be able to at least be able to block by 
> the number of simultaneous connections even having an environment with 
> several vms or containers.
> I currently have an environment with 3 guacamole servers with Tomcat 8 
> running behind a HAPROXY. But I lose the block by simultaneous connection (I 
> charge my clients for simultaneous connection) and I can not give up having 
> more than one vm, because if one falls I lose all. It would also be great if 
> the user does not need to log in again if they go to another server (session 
> permanence). Today I work with hundreds of simultaneous users from different 
> places.
> It would also be very good to be able to separate the client from the server 
> and be able to work on HA on the server as well.
> My Environment:
> 3x Guacamole server and client: 0.9.12
> Database and Authentication: MySQL (another vm)
> File Server: SFTP (another vm)
> I alread commented this on:
> https://issues.apache.org/jira/browse/GUACAMOLE-189



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to