Home / server / Questions / 57092
Accepted
drAlberT
Asked: 2009-08-22 03:13:17 +0800 CST

What is the best process to automate Zimbra deploy using cobbler+puppet?

  • 772

I set up a fully working cobbler server on a RHEL5 machine. This is able to deploy a new server on bare metal machine, partitioning the disks, using LVM and creating as much virtual machines as I need. The virtual machines takes their install instructions, configurations, yum repositories and so on from the cobbler server too.

This is really exiting, but the next step is to provide a Full Zimbra server through this mechanism.

My goal is to have Zimbra running upon 2 virtual machines, one for the mail engine and another for the webmail interface (at least as a first step).

What is the best way to deploy them and configure the entire system using puppet?

The philosophy is to use cobbler for very minimal deployment of the machines (both bare-metal and virtualized ) and leave every configuration issue to puppet.

Thank you in advance to anyone will give me some structured info and suggestion on the topic

deployment puppet rhel5 zimbra cobbler

2 Answers

  1. Best Answer

    I'm answering my own question, as for a long time I'm not having any solution.

    I did the job, and my approach has been the following:

    • I choose to have a single machine setup for now (but the process can simply be tuned for every kind of setup)
    • deploy a bare metal machine using cobbler
    • make a cobbler snippet that downloads ZCS tarball
    • run via cobbler "post script" the zimbra install script via expect

    this means you follow the installation procedure by hand once, write the expect script and now you can make as many installation as you want in a totally automated and programmatic way()

    As zimbra is a quite self configuring beast I decided to not maintain confs via puppet, zimbra update scripts should do they job in case of upgrade or update.

    • 3

  2. Zimbra doesn't separate itself out in the way you have described here... The web interface is fairly closely tied into the MTA - it's best to treat it as one piece of software rather than multiple, unless you want to pull it apart yourself and put it back together again, which is not likely to work without much effort

    Basically in the Open Source edition, clustering is not supported at all - you are expected to run everything on one machine (virtual or not).

    In the Network editions, they support clustering, but basically as far as I understand all the machines run the same software stack, and load is distributed across that (see Product Editions)

    The clustering is implemented using Red Hat Cluster Suite "to provide M+N clustering of our mailbox servers." (see the zimbra wiki FAQ and Cluster_troubleshooting articles)

    • -1