Page History

...

CCMR's web service shuts down and Freed's web site continues to work correctly.

Project status

5/12/13: Jack signed off on this project.

NOTES: Required spooling up a new project to migrate CCMR's FTP service.

Strategy

1A) Attempt migration to a CIT service.

1B) To the degree CIT hosting service technology works for ACERT, align near- and long-term support from IWS (of CIT) <http://www.it.cornell.edu/about/atsus/iws/>. IWS needs to know our timelines to migrate the site.  Request to IWS is for an estimate to help with:

• Migration coordination (to the degree needed)
• Documentation (of the infrastructure, including installation configuration)
  • Outcome: Sue (CTI) spent 2 hours on the review of the site and documentation, so a total of $152.
• On-going support, post-migration

2) Longer term, consider site re-write using contemporary tools and services. We may need to look harder into this if the above migration proves difficult.

• Identify options for hosting, and characterize trade-offs, including costs and administrative overhead.
• CIT's Academic Technologies (AT) group (Todd Maniscalco <tam42>) likely can provide free consultation, with free follow-up services. (CIT's IWS may also be able to do an initial consult for free, too.)

Project notes and efforts

Project completed.

Migration to CIT's LAMP service

5/1/13: Oliver asked Curt if project is completed so Jack can sign off on it.

...

• What is courses2 back-ups and recovery profile? Scenarios:
  • If systems crash, how recent a back-up?
  • If Dee wants a previous version of a file, what are her options and process?
    • Or, does she go through her own files instead? Other scenarios?

April 15, 2013, Monday: Oliver wrote to Curt requesting time estimate for cut-over, with link to above to-do's. And the work required if cut-over not for this week.

April 15, 2013,Monday: Pinged Curt re: CIT work closure.

4/5/13: The copy of web site is on CIT-hosted web server. All technologies seem to be working correctly on the new location, but must be further confirmed by Dee. Dee can connect and modify items in the new location.

...

• Dee to confirm functionality in new location.
• Dee to true-up content in new site with content added recently to current site so there are no differences in data or structure between the two sites.
• Curt and Dee to sign-off that new site looks and behaves like current site.
• Barry, with CIT, to cut-over domain name. Thus, ACERT URL to web site changes from pointing to current web site to pointing to the new location. Users should not notice a difference.
• Dee to continue verifying that new location is working as expected.
• Curt and Dee to sign-off on migration's success.
• Barry to turn off old web server.

Strategy

1A) Attempt migration to a CIT service.

1B) To the degree CIT hosting service technology works for ACERT, align near- and long-term support from IWS (of CIT) <http://www.it.cornell.edu/about/atsus/iws/>. IWS needs to know our timelines to migrate the site.  Request to IWS is for an estimate to help with:

• Migration coordination (to the degree needed)
• Documentation (of the infrastructure, including installation configuration)
  • Outcome: Sue (CTI) spent 2 hours on the review of the site and documentation, so a total of $152.
• On-going support, post-migration

2) Longer term, consider site re-write using contemporary tools and services. We may need to look harder into this if the above migration proves difficult.

• Identify options for hosting, and characterize trade-offs, including costs and administrative overhead.
• CIT's Academic Technologies (AT) group (Todd Maniscalco <tam42>) likely can provide free consultation, with free follow-up services. (CIT's IWS may also be able to do an initial consult for free, too.)

Project notes and efforts

Migration to CIT's LAMP service

April 15, 2013, Monday: Oliver wrote to Curt requesting time estimate for cut-over, with link to above to-do's. And the work required if cut-over not for this week.

...

• .

April 5, 2013, Friday: Oliver sent Curt a copy of this project's current status and to-do's, asking for time-frames for to-do's leading up to the domain name change Barry will need to do. Requested time-frame estimates within a week or so.

...