[D2l-alert] App Server Upgrade

[Meyer, Chris J.]

Anytime on or before 1/11/13 is fine on TEST. I would like to avoid any
work on TEST or PROD the week of 1/14/13 if possible. How soon were you
considering the work on TEST and PROD?

 

Chris

 

Chris Meyer | Dean, Learning Resources Center | Rose State College |
www.rose.edu <http://www.rose.edu>  
6420 S.E. 15th St. | Midwest City, OK 73110-2799 | v: 405.733.7913 | f:
405.733.7567 | e: cmeyer at rose.edu <mailto:cmeyer at rose.edu>  

 

From: d2l-alert-bounces at lists.onenet.net
[mailto:d2l-alert-bounces at lists.onenet.net] On Behalf Of Cary Smith
Sent: Wednesday, January 02, 2013 2:32 PM
To: Frank Hedges; d2l-alert
Subject: Re: [D2l-alert] App Server Upgrade

 

All, 

 

I received a followup message from D2L Services Team that the App Server
upgrade should not cause any downtime unless you're using Shibboleth
SSO.  If so, it's only expected to be a 10 minute downtime for this
upgrade. 

 

Regards, 

Cary

 

 

From: d2l-alert-bounces at lists.onenet.net
[mailto:d2l-alert-bounces at lists.onenet.net] On Behalf Of Frank Hedges
Sent: Wednesday, January 02, 2013 1:27 PM
To: d2l-alert
Subject: [D2l-alert] App Server Upgrade

 

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/b52e4540/attachment.html>