1 / 31

Web Server Migration

Web Server Migration. April 30 th , 2004 Presented by Geoff Strom Information Technology Services. Topics. Reasons for Migration User and Web Site Changes Impact on Services Hosting Structure Directory Layout System Administration Schedule. Reasons for Migration. Concerns.

rhonda-gates
Download Presentation

Web Server Migration

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Web Server Migration April 30th, 2004 Presented by Geoff Strom Information Technology Services

  2. Topics • Reasons for Migration • User and Web Site Changes • Impact on Services • Hosting Structure • Directory Layout • System Administration • Schedule

  3. Reasons for Migration

  4. Concerns • WXA is unsupported at both the hardware and software level • Administration is minimal and done manually • Reliability and security are concerns

  5. Solutions • Future growth in web service offerings depends on an upgraded, secure, and manageable platform • Supported hardware is available (FXWEB1)

  6. User Changes

  7. Accounts • Will be named • Username same as SLU email • Initial quota will be 50MB • Will be verified nightly with system information • Accounts no longer in the system will be disabled immediately, pending removal

  8. Access • SFTP • SSH on request • No more insecure Telnet or FTP • Software upgrades will be necessary • Web based "control panel" containing account information and tools

  9. Web Site Changes

  10. Owner • Single defined owner • Will be able to assign group members • Web based "control panel" containing site information and tools • MySQL database server on request • PHP on request

  11. Groups • Named after the web site • Members have full read/write permissions • Only members will have access • Initial quota will be 100MB

  12. Impact on Services

  13. Services that will be migrated • All current web sites • phpMyAdmin (slumyadmin) • phpEasySurvey (EasySurvey) • Homefree (pages.slu.edu)

  14. Services that will not be migrated • ServletExec • TestPilot • UltimateBB

  15. By The Numbers • Approximately 300 user accounts will be migrated • Approximately 400 web sites will be migrated

  16. Hosting Structure Changes

  17. Current Hosting Structure • Three kinds of web sites • Domains • http://www.slucare.edu/ • Virtual Hosts • http://medschool.slu.edu/ • Everybody else • http://www.slu.edu/colleges/AS/ • http://www.slu.edu/centers/heartland/

  18. New Hosting Structure • Two kinds of web sites • Domains • http://www.slucare.edu/ • Virtual Hosts • http://medschool.slu.edu/ • All existing sites that are not already Domains or Virtual Hosts will be converted to Virtual Hosts

  19. Domains • Available via traditional addresses: • http://www.slucare.edu/

  20. Virtual Hosts • Available via traditional addresses: • http://medschool.slu.edu/ • Two alternative addresses will also be available: • http://www.medschool.slu.edu/ • http://www.slu.edu/medschool/

  21. Aliases • Redirects from the original address • http://www.slu.edu/colleges/medschool/ would redirect to http://medschool.slu.edu/ • Make transition easier but should expire • All converted web sites will be granted a temporary Alias to ease the transition

  22. Directory Layout

  23. Current Directory Layout

  24. New Directory Layout

  25. New Directory Layout • Home directories will have two sub directories: • files • public_html • Unable to modify home directory content • Access to web sites via symbolic links

  26. System Administration

  27. Current System Administration • Done manually • Small number of people with the skill and access to make changes

  28. New System Administration • Stored in a database • Easy to use front end • Increased number of administrators • Configuration files rebuilt automatically

  29. Schedule

  30. Schedule

  31. Questions?

More Related