I think the sessions is the least of the problems. We run load -balanced icingaweb2 setup and the re-login is not an issue. The major thing is the configs that are not yet database driven. ( dashboards, announcements, ). User pref can now be in database.
So if you don't have a mean to replicate files across all your web ( we use puppet to manage configs and dont allpow users to create dashboards for now, we only do global ones. ) , you'll stil have out of sync configs between webs. We did it some issues with Director when multiple people/system use the api and multiple commits are happening but we did mitigate with sticking the /director stuff to the same web. -- Pascal Larivée iWeb Hi, I'm planning to set up a redundant setup with two nodes running Icinga Web 2 behind a HAproxy instance. In the default configuration, PHP session storage is in the local file system on the Icinga Web 2 servers. This works very fine unless the load balancer decides to fail over to the other server, in which case the user needs to re-login. Has anyone tried to use the database (in this case, PostgreSQL) as the session store for the Icinga Web 2 PHP instance? That setup works perfectly for Grafana, so I think it would be worth a try with Icinga Web 2 as well. Peter. _______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org<mailto:icinga-users@lists.icinga.org> https://lists.icinga.org/mailman/listinfo/icinga-users
_______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users
