~13 year old system suffering from benign neglect. Public web server with few if any updates to OS or web server, on Chemistry's "trusted" network. Original re-write plans fell through.
Goal
Completion by end of August. What does success looks like?
- NMR Scheduler still works
- Current old hardware no longer being used.
- Current OS and Apache software no longer being used.
- System is not on Chemistry's trusted network.
- Chemistry IT continues not to have any responsibilities to the functioning of the server.
Process
- Ivan to make the migration happen.
- Chemistry IT to provide consultation services.
- Chemistry IT to provide this documentation so project moves forward efficiently and with fewer surprises.
- Chemistry IT to induce pressure to ensure the server moves off of Chemistry's trusted network in a timely manner.
- This will include organizing regular check–in meetings. And managerial escalation if pace or engagement not sufficient to move server off of Chemistry's trusted network.
To do's
| Date | Person | Task | Notes |
|---|---|---|---|
| 5/20/16 | Ivan | Review web-hosting services (Future task: Select and try moving a copy) |
|
| 5/20/16 | Oliver | Create calendar proposals for check-in meetings every other week, through August, to ensure on-track. | Must skip July since Oliver away that month. |
Completed tasks
Idea: Simply copy completed above items to here, specifying approx. date completed.
| Completion date (approx) | Original date | Person | Task | Notes |
|---|---|---|---|---|
Meeting notes (reverse chron)
5/20/16 Fri
Oliver and Ivan met. Reviewed Oliver's queries to CIT (IWS and CIT's AWS/ Docker folks).
Ivan can't afford web developer work so re-write not appropriate.
Learning Docker and associated abstraction layers also does not seem appropriate.
Instead, look for server hosting to host current Perl-based application (with server-side includes) such that someone else is maintaining current:
- OS
- Apache
We hope a migration "just works" with minimal input from Ivan. Oliver's concern is that this won't be a slam-dunk migration due to age of code (deprecated functions, etc) and configuration difference. Bluehost has experience with users doing this, and have written to this point here: