Puppet configuration for LAMP servers

Goals

Manage in a centralized way all our servers.

Interact as less as posible with our servers.

Have “written” configuration so it’s replicable and we are able to use version controlling.

Deliverables:

A zip containing puppet 2.7 modules and manifests to build a LAMP production server with at least the following modules

MySql

Apache

PHP

Tomcat

SolR

Must work with centOS puppet clients. Tests will be done using [url removed, login to view]

MySql

For a node

We must be able to specify if MySql must be installed and running.

We must be able to specify the root password.

We must be able to specify in a directive the configuration file to use. The file must be in the puppet master server.

We must be able to specify in a directive to make periodic backups specifying peridocity and backup folder.

We must be able to specify databases with its own user and password. Puppet must ensure that the database and user are created and if not create them.

Apache

For a node

We must be able to specify if Apache must be installed and running.

We must be able to specify in a directive the configuration file to use. The file must be in the puppet master server.

We must be able to specify a Virtual Host in a directive specifying:

Name

Application Path

Server name

List of alias ([url removed, login to view], [url removed, login to view])

A list of redirects ([url removed, login to view], [url removed, login to view])

With the virtual host directive, a config file must be created through a template. Apache must load the configuration on changes.

We must be able to specify “proxys”

Exj. [url removed, login to view] -> [url removed, login to view]

This will generate a config file through a [url removed, login to view] must load the configuration on changes.

Tomcat

For a node

We must be able to specify if Tomcat must be installed and running.

We must be able to specify in a directive the configuration file to use. The file must be in the puppet master server.

We must be able to specify in a directive the users configuration file to use. The file must be in the puppet master server.

SolR

For a node

It must ensure tomcat is installed in a node.

We must be able to specifiy what war to use (they are in the master server)

We must be able to specify the home folder for solr

A config file must be created in /etc/tomcat6/Catalina/localhost/[url removed, login to view] based in a template.

We must be able to create solr slots with a name. It implies:

Creating folder with slot name in the SOLR home folder.

Assigning the folder writing permissions for solr user

Add a line <core name="nombre" instanceDir="name" /> to the HOME_SOLR/[url removed, login to view] file

PHP

For a node

We must be able to specify if PHP must be installed.

It must install version [url removed, login to view]

We must be able to specify in a directive the configuration file to use. The file must be in the puppet master server.

It must install a list of php modules commonly used for Drupal projects.

GD

XML

MCrypt

PEAR

mbstring

devel

The deliver will include a node configures with everything showing the usage of the modules and documented in a understandable way.

Administrator systemu

Numer ID Projektu: #1733838

O projekcie