[D2l-alert] App Server Upgrade

[Frank Hedges]

Hello Everyone, 

I hope everyone had a wonderful holiday.


Cary sent me the following information on the upgrade procedure for the new app servers. Based on this information it will have minimal impact doing the App server upgrade. I propose we establish a time to perform the upgrade on the test app server as soon as possible then schedule an 7am (Tues.-Fri.) cutover on the production app servers. I am fine with test and prod being on different levels for this upgrade since we are not modifying the application per se just the underlying OS. Please provide your input on this proposed upgrade and possible dates for both test and prod. 


Thanks


Frank



Hi Frank,

 

I hope this message finds you doing well and you had a great holiday break. Below you’ll find an explanation of the App Server upgrade process and expected downtime. Please let me know what questions come from this.

 

We have a standard formula for conversion projects. We estimate 6 hours for the first app server and 4 hours per app after. So, 6 for 1 app, 10 for 2, 14 for 3, 18 for 4, etc. The work is laid out as such:

 

(1) Client creates a blank application server with the necessary hardware.

(2) D2L performs server prep and verification.

(3) D2L performs application server migration.

(4) Client clones the application server using a method of their choosing.

(5) D2L will update the configuration of the new clones.

(6) D2L will verify the configuration of the application and ensure functionality where possible.

(7) Client will add new application servers to the load and monitor for any issues.

(8) Pending positive results, old application servers can be retired.

 

In the event of a failure, tickets should be logged with support noting their possible relation to the migration. If you have any further questions, please let me know.

 

Regards,

Cary

--


 
 
Frank Hedges - Systems Engineer
OneNet/Oklahoma State Regents for Higher Education
frank at onenet.net - Ph: 405-225-9183
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.onenet.net/pipermail/d2l-alert/attachments/20130102/01732e69/attachment.html>