vnick wrote > On Wed, Dec 4, 2019 at 5:47 AM alipawsey < > alizamani84@
> > wrote: > > For Guacamole Client, you should be able to deploy several Tomcat > instances, pointed at a single database, and then put a load balancer in > front of them, and balance the front-end connections as you so desire. > The > metric used for the front-end balancing can vary based on what the load > balancer can do - some load balancers will only do it based on number of > connections, some allow for feedback loops from the balanced hosts to > monitor load and such on the system, but you have several options. The > one > caveat, here, is that Guacamole Client currently lacks the ability to > share > active connection information among multiple deployed instances, so if you > are using any limits on concurrent connections you may not see expected > results. Other than that, as long as the load balancer persists the > client > connection to the correct back-end server and doesn't shuffle things > around > you should be fine. > > For Guacamole Server (guacd), you have a couple of different options: > - Deploy one guacd instance per Guacamole Client instance, and point each > Guacamole Client at its "own" guacd instance. This could live on the same > system as Guacamole Client, or could be a different system that is then > configured in each guacamole.properties file. > - Deploy several guacd instances behind a load balancer, and then point > all > of the Guacamole Client configs at the single load balancer. The caution, > here, is that, if you do this, you'll want to make sure that there is some > level of persistence for the requests coming from Guacamole Client to the > load balancer and then through to the back-end guacd system so that the > load balancer doesn't continuously try to switch packets for a given > connection to different guacd instances, which will result in pretty > immediate and severe problems with connections. > - You can also override the guacd system that is used on a per-connection > basis, which would allow you to spread out load based on connections, if > you so desired. Lets distinguish balancing into two items: "/Connection Balancer/" which refers to the number of connections per node and "/Workload Balancer/" which redirects new connection to the node with less workload meaning less cpu/ram usage. The first case is already possible in the /guacamole connection group/ as described here: https://guacamole.apache.org/doc/gug/administration.html#connection-group-management Could the load balancer you mentioned mange the workload balancing as well? > I guess I fail to see what value something like Slurm or FastX would have > over the possibilities I mentioned above for load balancing? I'm also not > sure why you'd have to worry about manually terminating user sessions - if > you go with the methods of load balancing that I mentioned above, the > Guacamole components will take care of cleaning up the connections, and > you > shouldn't have to do any manual cleanup. Furthermore, the limitations of > load balancing that exist within the Guacamole application (lack of > sharing > of active sessions between nodes and the need for the load balancer to > keep > track of the connections between clients and Guacamole Client, and between > Guacamole Client and guacd instances) would also exist within a load > manager. > > Is there something I'm missing on the value of such a system with > Guacamole > that isn't already possible, here?? Slurm has the capability to free resources. Any plugin for Guacamole to do similar thing once session killed? Even by killing a session manually, only connection has been terminated and still a job could run on the instance keeping the resource busy. -- Sent from: http://apache-guacamole-general-user-mailing-list.2363388.n4.nabble.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
