You need some way to address HTTP sessions. Otherwise you will be randomly logged out if your request goes to a different dashboard host than the one you logged in on. One way is to set up a shared memcached cluster that each dashboard host talks to--configure the "CACHE" setting in the local_settings.py file. [1] Another way is to configure your load balancer with session stickiness/affinity. [1] https://github.com/openstack/horizon/blob/master/openstack_dashboard/local/local_settings.py.example On Wed, Feb 26, 2014 at 12:11 PM, matt <matt at nycresistor.com> wrote: > As horizon interfaces with OpenStack via the client apis primarily... > > should be as simple as deploying several instances and load balancing > between them properly. > > > On Wed, Feb 26, 2014 at 10:54 AM, Alvise Dorigo <alvise.dorigo at pd.infn.it>wrote: > >> Hi, >> I've read all the guide >> http://docs.openstack.org/high-availability-guide/high-availability-guide.pdf, >> but it seems that the HA configuration for the Dashboard is not covered. >> >> I wonder if it is worth to do it, or it is not treated because the >> Dashboard is a simple stateless service which can just be "mirrored" on >> another node without any particular setup. >> >> Could someone clarify ? >> >> many thanks! >> >> Alvise >> >> _______________________________________________ >> OpenStack-operators mailing list >> OpenStack-operators at lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >> >> > > _______________________________________________ > OpenStack-operators mailing list > OpenStack-operators at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20140227/bea74c57/attachment.html>