Bug #4110


Server Upgrade

Added by Stephen Real over 8 years ago. Updated over 6 years ago.

Priority name:
Category name:
Target version:
Start date:
Due date:
% Done:


Estimated time:
Deployment actions:


There are a number of interconnected issues regarding the physical server the Commons is running on. We are using a very old version PHP for starters, so the question is what is the best path to upgrading. Should we go to a cloud style virtual platform etc? We need to work with IT to develop and implement a migration plan. We are likely to get the best support if we use a configuration that adheres to IT standards rather than implementing a custom one-off infrastructure.

Actions #1

Updated by Boone Gorges over 8 years ago

Note that this server migration (to a VM) has already taken place on cdev. Here is the initial proposal from Sandy in IT:

1. virtualize a RedHat physical server (similar to CDEV and Commons) to VMware on Tuesday 3/24/15; we have not done this before.
2. if successful and with your approval, at 9:15 AM on Friday morning 3/27/15, prevent data changes (access to) CDEV, virtualize CDEV to VMWare, and install VMware Tools. We will record the duration and estimate downtime for the future virtualization of the Commons server.
3. contact you sometime Friday afternoon and request your team test/evaluate the CDEV virtual server.
4. with your approval, move hard drives from CDEV to COMMONS, prepare a RAID5 on the COMMONS and formally retire CDEV -- this will not affect production on the COMMONS server
5. on the next working day following Change Management approval, expand the LVM on the Commons server with the additional RAID5 storage -- this will not affect production.
6. plan to virtualize the Commons server at some future date (next summer?) in a way that minimizes downtime.

From what I recall, the migration was pretty smooth, so a similar path seems fine to me for the production site. (The production site has a good deal more data, so a longer downtime will be required. We'll need to schedule carefully.)

Matt, do you want to take the next step of reaching out to Sandy?

Actions #2

Updated by Boone Gorges over 8 years ago

  • Assignee changed from Boone Gorges to Matt Gold
  • Target version set to Not tracked
Actions #3

Updated by Stephen Real almost 8 years ago

I know we are dependent on IT resources for this, but is there a project plan for this? Even a high level timeline might help us manage it.


Actions #4

Updated by Matt Gold almost 8 years ago

Hi Steve,

We'll be meeting with IT soon to discuss



Actions #5

Updated by Boone Gorges over 6 years ago

  • Status changed from New to Resolved

Also available in: Atom PDF