[Kolab-devel] Other kolab scalability issues

Gunnar Wrobel wrobel at pardus.de
Sun Oct 21 07:49:21 CEST 2007


Fabio Pietrosanti <lists at infosecurity.ch> writes:

> Dear all,
>
> i noticed one bad scalability issue of Kolab while you handle a lot of
> virtual domains.
>
> The main issues are the 'static' configuration that could be made
> dynamic of imapd.conf of Cyrus and main.cf of Postfix.
>
> For Cyrus imapd.conf the "loginrealms:" include the list of all virtual
> domains and it's generated by kolabd.
> If the list of loginrealms became too much long because you are using a
> lot of virtual domains bad things could appens.

What kind of limits are there and at which point are we going to hit
these limits? What would cyrus and postfix do if this limit gets
exceeded?

>
> Solution would be to add something like this loginrealms dynamic lookup
> described here:
> http://www.irbs.net/internet/info-cyrus/0601/0244.html
>
> or i am wondering which is the real reasons for which we are requiring
> loginrealms, because here they removed it and it worked
> http://www.nabble.com/Multidomain-support-in-Cyrus-eGroupware-with-LDAP--solved--t3665722s3741.html
>
> Now on my multiple-domains (a lot of domains) email servers, i commented
> out the loginrealms and it works fine, i can create users, change
> password, login, change permissions, etc, etc . It seems to work.
>
>
> For postfix's main.conf it's the same for the following configuration
> line that contains the list of domains:
> mydestination
> masquerade_domains
>
> Imho we hould map this lists to dynamic lookups to the ldap directory in
> order to scale better with a large number of virtual domains.

Would the lookup only happen when the services are started? Or would
the lookup occur associated with certain user actions? The second
scenario would slow things down so it might be better if this is
configurable or gets only activated if the server has more than a
defined number of virtual domains managed.

>
>
> If you agree i would be start making the ldap lookup files and send
> patch.

I think it would be good though to have this. I don't know if it
should be activated by default but if its optional it would be great.

Cheers,

Gunnar

>
> Fabio
>
> _______________________________________________
> Kolab-devel mailing list
> Kolab-devel at kolab.org
> https://kolab.org/mailman/listinfo/kolab-devel

-- 
______ http://kdab.com _______________ http://kolab-konsortium.com _

p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium

____ http://www.pardus.de _________________ http://gunnarwrobel.de _
E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
Tel.   : +49 40 432 72335                           Bundesstrasse 29
Fax    : +49 40 432 70855                            D-20146 Hamburg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   >> Mail at ease - Rent a kolab groupware server at p at rdus <<                 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~




More information about the devel mailing list