How To: Provision a new server

User Accounts, permissions and SSH Keys

In addition to root, the machine will need the following accounts added:

You will want to make sure that your SSH RSA Key is installed in these two accounts and possibly root. It is not strictly necessary to have your key in the root account, but you will need it to be in the interch and camp accounts for deploying the catalog from camp0 on dev1.

/home/camp and all of its files and sub-directories (except .ssh) need to be world readable.

Libraries and Scripts

Camp::Config

Copy the following from /home/camp on dev1 to the new server in the same location:

FNet::Config

FNet/Config.pm will need to be copied from its current location on dev1 to somewhere in Perl's PATH on the new server. It should be copied to a location on the new server analogous to its location on dev1. It is currently at

/usr/local/lib/perl5/site_perl/5.8.5/FNet/Config.pm

Services and Configurations

Apache

The Apache config files, httpd.conf and fnet.conf should be cloned from one of the web servers and tweaked to suite the new server if it is providing web services.

Interchange

The only part of interchange that should be unique to the server are interchange_local.cfg and bin/interchange (the interchange 'executable'). These will get create/overwritten during the deployment process, so if you are going to tweak them for the server, you need to be careful.

Perl Modules

Some Perl modules will probably be needed which do not come with a stock system.

Deployment

The deployment script is at:

/home/camp/bin/deploy.pl

You should add the new server to the list at the top of the script if you want deployments to go to the new server from now on. If you just want to deploy to the new server without adding the server to the script, you can use the -h flag.

deploy.pl -h new_server_name

Stuff Still in /usr/local/fnet

Some resources remain for the present in other parts of the filesystem, particularly /usr/local/fnet.