History

Groupware service deployment and configuration guide

Preparation

  • Download the image here.
  • Configure the virtual machine with the following parameters:
    • Volume size: 3GB
    • RAM: 256 MB
    • Name: egw
  vmcreate --size 3G --file egw-1.1_2.tgz --mem 256 --ip 192.168.69.25 egw
  • Boot the virtual machine.
  xm create -c /etc/xen/auto/egw
  • Login as root using the password passwd.root and change the default password.

Machine configuration

There are two configuration options available:
  • Centralised configuration: if the machine is going to be integrated in a ModularIT management structure.
  • Local configuration: if the machine is not going to be integrated in a ModularIT management structure.

Centralized configuration

On Puppet server

  • Create the entry of the ModularIT machine being installed:
  node "devel.egw" inherits "devel" {
        # First installation?
        $bootstrap = yes

        $modularit_name = "devel.egw" 
        $comment = "Development eGroupWare" 
        include modularit 
  }

Client configuration (The machine being installed)

  • puppetd is restarted in debug mode to ensure that it updates correctly:
  /etc/init.d/puppet stop
  puppetd --debug --no-daemonize --runinterval 60 --fqdn NOMBRE_MODULARIT --server PUPPET_MODULARIT
  • The parameters NOMBRE_MODULARIT and PUPPET_MODULARIT will be provided by the service manager (register with the mailing list if you have questions regarding this).
  • Puppet is started as a service after it has completed several cycles without generating errors:
  /etc/init.d/puppet restart
  • PIFIA should be executed to ensure that the notifications to Nagios are functioning correctly.
  /var/lib/pica/bin/scheduler Emergency
  /var/lib/pica/bin/scheduler Warning
  • Ensure that Nagios is not generating alerts that read OK. At this point critical AIDE alerts are expected.

Local configuration

The following installation mode is needed when the machine is not integrated in a centralized ModularIT management structure.
  • Go to the /opt directory.
  • Download the ModularIT configuration tree:
  links --source "http://git.modularit.org/?p=modularit.git;a=snapshot;h=HEAD;sf=tgz" | tar xvzf -

This will create the /opt/modularit directory.

  • A directory for the puppet modules is created:
  mkdir /etc/puppet/modules
  ln -s /opt/modularit/Puppet/modularit /etc/puppet/modules/
  • Edit the file /opt/modularit/Puppet/offline/variables.pp and modify it so that the correct configuration is used. This file will be common to all ModularIT installations.
  • Edit the file /opt/modularit/Puppet/offline/offline.pp to reflect the name and type of the ModularIT machine, in this case: egw. The file will be different for each machine (The name and type of machine are always different).
  • Once the configuration has been completed, execute puppet in off-line mode.
  puppet --debug /opt/modularit/Puppet/offline/offline.pp
  • The process should finish without errors.

Service preparation

  • Execute the eGW service initialization script.
  modularit-egw-init.rb
  • The script configures egw to use the central LDAP server.
  • Accessing the eGW with the LDAP admin user will allow administrative control.
  • Navigate to Administration -> User groups and configure the permissions for each group. It is recommended that a LDAP egw group is created and used as the default egroupware group. egroupware users should be in the egw group.
  • If administrator access is required in order to modify the configuration, the following details can be used: admin/modularit.

Also available in: HTML TXT