Hi Pascal, > 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.
Yep. This isn't that much of a problem as I'm also setting up and maintaining the whole environment (including dashboard synchronisation) from Ansible. Announcements would be an issue, but I guess that can easily be worked around with rsync. That would also be my fallback solution for sessions, but given the fact that PHP can store sessions in the DB it seems quite clumsy. > 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. Ah, thanks - I've not run into it yet, but doubtlessly will :-) Cheers, Peter. _______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users
