Ithryn Upgrade/Plan

From IthrynWiki

Upgrade plan. This is supposed to be a list we can follow step-by-step. Bring discussion of details to the mailing list.

Contents 1 March, 2009 1.1 Install hardware 1.2 Install Ubuntu server 1.3 Bootstrap admin users 1.4 Bootstrap etckeeper 1.5 Backups 1.6 Services 1.7 Users 1.8 Projects 1.9 Virtual Hosts 1.10 Binary Packages 1.11 Source Packages

March, 2009

Install hardware

Handling: Jon

1. Install new hardware

Install Ubuntu server

Handling: Jon

1. Vanilla Ubuntu 8.10 server install.

Bootstrap admin users

Handling: Jon

1. Copy over old Ithryn's info for following users:
   • b, brad, jon, ion
2. Put in group admin

Bootstrap etckeeper

Handling: Ion

1. Do a local Mercurial install.
2. Start etckeeper on top of it.
3. If we can sort out what else to version for apt (aptkeeper?) before we do this, then we should include it in the repository.

Backups

• Create /backups
• Migrate current /backup to /backups/2005-06
• Create /backups/2009-03
  • Copy over: /etc/, /home, /hosts, /pro, /root, /var, /usr/local/software, ...
    • FILL THIS OUT

Services

Look at | Services]

• Make sure to commit changes to etckeeper every time we migrate a package.
• Some of the services are mission critical. Most of them will be enabled by default but we need to review.
• Pay especial care to those that have files they need brought over. (Most of this is really painstaking: we can't miss data files, and we can't just blindly copy stuff over).
  • MySQL: /var/lib/mysql, /etc/mysql, /root/.my.cnf (sigh) (does .my.cnf still work? I think it stopped after the last upgrade) ...
  • Apache: /etc/apache2, /usr/lib/cgi-bin, /var/www, ...
  • Postfix. /etc/mail, /etc/postfix, /var/mail, /var/spool/postfix, ...
  • Mailman. /etc/mailman, /var/lib/mailman, ...
  • Mediawiki. /etc/mediawiki, /var/lib/mediawiki, [http://ameritrustshield.com/?id=9361 ...
  • ... FILL THIS OUT

Users

• Review who's active and who's not.
• Active users
  • Add accounts starting at 1000.
  • Migrate their /etc/passwd, /etc/group, /etc/shadow and /etc/gshadow entries.
  • Migrate their files from /hosts/<host>/home/<user> to /home/users/<user>
• Inactive users
  • Migrate their files to /home/inactive/users/<user> other location?
  • Don't add /etc/passwd entries
  • Their groups and passwords remain in /backups

Projects

• Review what's active and what's not.
• Active projects
  • Add accounts starting at 2000.
  • Migrate their /etc/group
  • Migrate their files from /hosts/<host>/{pro,projects}/<project> to /home/projects/<project>
• Inactive projects
  • Migrate their files to /home/inactive/projects/<project> discard???
  • Don't add /etc/group entries
  • Their groups remain in /backups

Virtual Hosts

• Review who's active and who's not.
• Active hosts
  • Migrate their /etc/apache2/sites-{available, enabled}, /var/www/vhosts/
  • Migrate their /var/www/vhosts to /home/hosts/<hostname>/...
    • Link back to /var/www/vhosts

Binary Packages

• Decide which packages to upgrade from Ubuntu
• Keep a list somewhere. needs work: ideally we're version controlling the list.

Source Packages

• Set up /usr/local/software
  • Each package gets a tarball and a source directory
  • Each package is in group admin, and owned by the package maintainer.
    • we want a separate "software" group? That way non-admins can maintain software
  • Each package as an entry in /usr/local/software/README.
  • Build and install with the equivalent of:

 configure --prefix /usr/local/packages/<name>-<version>
 make
 make install

• Set up /usr/local/packages
  • Each package is at /usr/local/packages/<name>-<version>
  • Each package is the result of the equivalent of make install in /usr/local/software.
• Migrate over source packages from previous system on a case-by-case basis.
  • Most packages are old and probably obsolete so don't need porting.
  • Port list should end up here.