Instant messaging service installation and deployment guide

Preparation

Download the image here.
Configure the virtual machine with the following parameters:
- Volume size: 2GB
- RAM: 128 MB
- Name: jabber

  vmcreate --size 3G --file jabber-1.1_1.tgz --mem 128 --ip 192.168.69.26 jabber

Boot the virtual machine.

  xm create -c /etc/xen/auto/jabber

Machine configuration

There are two configuration options:

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 the Puppet server

Create the entry of the ModularIT machine being installed:

  node "devel.jabber" inherits "devel" {
        # First installation?
        $bootstrap = yes

        $modularit_name = "devel.jabber" 
        $comment = "Development Jabber" 
        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).
Once the puppet completes several cycles without errors, it is then started as a service:

  /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 normal

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: jabber. 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 Jabber service initialization script.

  modularit-jabber-init.rb

The script does the following.
- Initializes the internal database.
- Establishes the initial parameters for LDAP validation.

The remaining configuration is done through a web console using http://jabber:9090/ with the LDAP admin account.
Enter the domain: jabber.dominio.com (eg. jabber.canarytek.com). If the server connects to other servers, the name must resolve to a valid IP.
Deactivate anonymous connections and the automatic registration of users within registrations and connections.
To share contacts from the server, go to "users/groups", select the group you want to share (ie. jabber) and select enable sharing. This way all users belonging to that group will wee each other. You can also share this group with other users/groups

Initializing AIDE

Once everything is functioning correctly, initialize the AIDE databases as described in the AIDE.

Also available in: HTML TXT

ModularIT