Skip to content

OJS application and OS upgrade

Jump to bottom
Sean Crowe edited this page Oct 22, 2020 · 3 revisions

journals-qa.uc.edu:

1. - [x] Perform the app upgrade on the current QA server and verify all is well.

    • Allocate new server libojsqa2 QA server.
    • Copy/sftp the upgraded source code to the new QA server and verify all is well.
    • Run upgrade script/migration on the existing existing database.
    • Re-register journals-qa.uc.edu to the new server
    • Bring site up and notify the Press for review.

journals.uc.edu

    • Create the new journals production server with upgraded OS (Dennis can get a head start on this while the QA app is being upgraded)
    • Schedule, create change request, and notify stakeholders of downtime
    • Back up the application and the database
    • Perform the app upgrade on the current server and verify all is well.
    • Re-register journals.uc.edu to the new server
    • Move the Isilon mount to the new server
    • Package source code in github repo for deployment (merge changes from qa branch, etc).
    • Copy/sftp the upgraded source code to the new server and verify all is well. The app will use the existing database.
    • Run upgrade script/migration.
    • Bring site up and notify stakeholders.

Items 3-9 would all be done in the same day to minimize production downtime. If something goes wrong, we can quickly revert back to the old server and the backed-up app/database.

journals-dev.uc.edu

Suggestion: can we drop the dedicated server for journals-dev.uc.edu and just run it on libappstest? It’s a standard PHP app with no need for lots of storage.

Clone this wiki locally