This document is written as an aid for AgroClimate and FAWN personnel in migrating their web applications to a new location within OSG's hosting offerings.
Over the past three years the AgroClimate and FAWN projects have utilized physical servers co-located in the CNS SSRB Datacenter and managed by the CNS Open Systems Group. In May 2009 a proposal to migrate away from this old, unsupported infrastructure to current OSG hosting infrastructure was agreed upon. This document will address the steps that must be taken to move forward on this migration.
In order to understand the migration we will start by understanding the existing, old infrastructure and configuration.
The hardware is comprised of two IBM x346 servers running RedHat 5.2. These servers are configured to host both the AgroClimate website and database and the FAWN website and database and also provide shell access, cron, R statistical software, and anonymous FTP upload of datasets.
The current production websites live on the /nerdc/www/ NFS share at /nerdc/www/www.agclimate.org/ and /nerdc/www/fawn.ifas.ufl.edu/ respectively.
Each project has its own MySQL instance that runs on each physical server. AgroClimate's DB instance runs on port 3306 and FAWN's DB instance runs on port 3307. Currently the database instances on if-fwn-prdw01 are acting as the primary/master instance with the database instances on if-fwn-prdd01 acting as a slave/standby instance.
The infrastructure to replace the old IBM servers is based on more-or-less standard OSG hosting offerings- Apache web hosting with php fast-cgi, MySQL, and Vmware virtual machine resources. There are two differences, however, in that (1) OSG will provide fully managed hosting for Agro/FAWN's VM and (2) AgroClimate's MySQL presence will be on dedicated instances of MySQL.
A virtual machine that will be managed by CNS/OSG has been created and installed for use by the AgroClimate and FAWN projects. This system will primarily be used to run cron jobs, dataset uploads, anonymous ftp downloads for fawn, R statistical analysis, and general shell access for the projects' developers.
The hostname of this VM is agrofawn-prod01.osg.ufl.edu
The VM has been configured to allow Gatorlink login via SSH by the Ag/FAWN developers. Additionally this server will accept logins from the kerberos identities that were created as “service users” for AgroClimate and FAWN. The cnswww-* users will also be the file owners of the respective website contents.
The new websites will live in the same location as the old websites: on the /nerdc/www/ NFS share at /nerdc/www/www.agclimate.org/ and /nerdc/www/fawn.ifas.ufl.edu/ respectively.
FAWNs database will reside in our shared MySQL instance. This resource has already been created within our shared production MySQL environment- the DB name is fawn.
AgroClimate has a proliferation of databases within MySQL that they maintain in support of their application and its accompanying tools. To accommodate this we will provide them with two dedicated MySQL instances for their test and production environments. Because this is a non-standard offering a special price of $60/month/instance was agreed upon.
The production and test AgroClimate MySQL instances have already been created:
phpMyAdmin is available for all of these MySQL resources. This web interface is available at:
https://open-systems.ufl.edu/phpMyAdmin/<port>/
where <port> is the port number of the relevant MySQL database instance. Any access requires authentication with a valid Gatorlink credential followed by phpMyAdmin login using local MySQL credentials.
Pre-testing
Testing
Prior to AgroClimate's website redesign a year or two ago, the web app's framework depended on php's “register globals” setting being enabled; we are not sure if this is still true. This option is not enabled in the new environment and is a possible cause for migration problems.
Migration
The existing test server, elnino.agen.ufl.edu, will also no longer be supported by CNS OSG. Instead all testing should occur on the test resources provisioned in OSG's hosting infrastructure and the agrofawn-prod01.osg.ufl.edu VM.
Server Hostnames / IPs:
Dispatched Hostnames / Dedicated IPs: *
Non-dispatched Hostnames / Dedicated IPs: **
Other DNS names, not controlled by CNS:
NOTES:
* The virtual-<project>-web1 name/IP is the dispatched ip for each project's website.
** The virtual-ifas-db[12] names/IPs are manually moved between the servers as a consistent point of access to the MySQL databases- this was done to help ensure write consistency for data loads, etc.
Server Hostnames / IPs:
Test websites to use during migration:
Database resources: