The system will be available for read access for most of this time but will not be available for update. <br><br>You may notice flakiness re: internet addresses as the DNS moves from the current server to the new one. I anticipate making the DNS change within 15 minutes of the transfer. (around 9:15 PM EST)<br>
<br>I'll post the status on the openwetware twitter feed.<br><br><br>Comments:<br><br>1. All user accounts on the current server should be migrated asap. Austin and Ilya are the only people who need to be concerned.<br>
2. If either Austin or Ilya are not available, contact me. I already have moved a backup of all /home directories to the new server.<br>3. Almost all of the packages formerly loaded and compiled manually have been loaded via the RHEL5 YUM facility.<br>
4. The database has moved from MySQL 4 to MySQL 5.<br>5. The MySQL files are still located in the /data directory as they are on the current server.<br>6. The stock PHP server is used rather than a custom compile.<br>7. All strategic historical log files have been migrated to the new server. This includes<br>
-openetware access/error logs for the last 2-3 years (none have been deleted)<br>-yeastpheromonemodel access/error logs (none have been deleted)<br>
-syntheticbiology access/error (none have been deleted)<br>-maillogs for <a href="http://openwetware.org">openwetware.org</a><br>8. All data and image files have been replicated to the new server. They will be re-synced before the final cut-over. <br>
This includes<br>- OWW and private wiki image files<br>- all source, extensions, etc.<br>9. All historical logfiles have been purged from the existing server. A final export will be done after the cut-over.<br>10. There may be a few extensions relying upon Tex support that will not immediately be functional. This will be addressed ASAP. Because of the nature of the system config, I've had a hard time testing all extensions on the new system.<br>
11. A set of script files now are used to manage the final sync of the systems.<br>12. I will test all private wikis to make sure they continue to work after the move. There should be no impact.<br>13. I will test the wordpress-mu blog software to make sure all is well with it. There should be no impact. <br>
<br>OWW Also moving to MediaWiki 1.12<br><br>This will be done during the same cut-over.<br>1. There should be no effect on existing users.<br>2. All extensions have been checked with 1.12. No problems are present. <br>3. All private wikis will be upgraded at the same time.<br>
<br>Issues<br><br>1. The web server's network address configuration is "challenging". I know it's just a text file and it can be modified if problems ensue. The complication in our case is the tight relationship between modifications to the MediaWiki source code and the network configuration. I've tested this to the extent that I can. I'm satisfied that making the server switch will work. <br>
<br>2. Because of the upgrade from the current Red Hat 4 to RedHat 5 Linux server release, there are issues that may crop up that I have not tested. I'll do my best to navigate these issues.<br><br>3. If the migration to 1.12 takes too long (not anticipated), I will re-enable access to the server with the existing 1.9 release. I do not foresee having to do this. There will be no effect on users regardless of the version.<br>
<br>I'm sorry I have to take it down this early; I've not managed to stay up late enough to do it safely over the last week. <br><br>Thanks!<br><br>Bill Flanagan<br><br>