Distributed setup

[Alain Spineux]

On Thu, Jul 31, 2008 at 10:35 AM, Albrecht Dreß
<albrecht.dress at lios-tech.com> wrote:
> Hi all,
>
> I'm new to this list, so please excuse me if my questions are really dumb...
>
> I would like to install Kolab 2.2 on /two/ Ubuntu Hardy machines in a
> "distributed" way:  box #1 shall have the Cyrus, Postfix and Apache related
> stuff installed, and box #2 shall get all the rest.  Apart for a more
> equally distributed load, the services on #1 shall be visible to the outside
> world.  Obviously, this box must be treated with more care.  Are there any
> descriptions how to install such a scenario?

This mean ldap and Amavis will be on #2, this is a good balance !

>
> Related to this, it would be great if I could use the pre-built
> Apache/Horde, Postfix and Cyrus packages on #1.  The advantage is that (1) I
> can rely on the Ubuntu package management for security updates and

Not a good argument, because OpenPkg and Kolab have also security in mind !

> (2) it
> will probably be easier to write proper SELinux policies (or do policies
> already exist?).  Any opinion about this?

Do you know SELinux ? If so, just translate the exisiting rules to
openpkg environment !
If not will you really learn and adapt SELinux for kolab ?

This was some words in flavor of Openpkg!

>
> Connected to the distributed install question above, maybe I can do a "full"
> install on #2, install the "stock" Ubuntu packages on #1, and then just copy
> the configs and tweak a few connection settings?  Or is this a too
> simplified approach?

I things the best is to install a full install on both, make it works
on #1, then
transfer features from #1 to #2 one by one

>
> Thanks in advance,
> Albrecht.
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>
>



-- 
Alain Spineux
aspineux gmail com
May the sources be with you