User Tools

Site Tools


migration

This is an old revision of the document!


Purpose

We are moving production services from bud, at Primary, to amber, 'in the cloud'. This page is an attempt to list out everything that needs to run on amber, notes on moving from debian to CentOS, and notes for testing before turning amber live.

Currently running services

MySQL

MySQL supports a members DB, roundcube, a click-through monitor, and wordpress. Possibly the safest way to move from bud to amber is to make bud replicate to amber. Then when we're ready to migrate, we can turn off bud's services, and the database will be up to date. This procedure is documented at http://www.softwareprojects.com/resources/programming/t-how-to-move-copy-a-live-mysql-database-and-what-1257.html. We should review our application configurations to make sure that they will be able to use amber's mysql installation when we copy them over.

Mail

This includes postgrey, postfix, spamassassin, courier, mailscanner, and mailman.

NTP
Apache

CentOS uses user and group 'apache' instead of 'www' and 'www-data', like Debian. We'll need to set the file and directory ownerships under /home/www/ aproppriately. Then we should be able to copy the contents of /etc/apache2 from bud to /etc/httpd/ on amber, change the user and group statements in httpd.conf to 'apache', and have it start.

migration.1279226485.txt.gz · Last modified: 2010/07/15 15:41 by SLUUG Administration