Upload
earl-begley
View
129
Download
3
Embed Size (px)
Citation preview
About the University of KentuckyDemographics
30,000+ students
12,500 staff
2,300 faculty
Flagship UniversityLand Grant$992M Endowment784 AcresOffices in all 120 KY counties
IT Staff250+ Campus IT
250+ UK Healthcare IT200+ College/Department IT
Why make the move to the cloud?
McVey HallBuilt – 1928
Currently housesUKAT Data Center No generator backup Old wiring and power grid Difficult to maintain proper cooling & humidity levels Computing footprint at maximum Disaster Recovery plan no longer viable
University President & Provost wantspace for academic purposes
Shrinking operational budgetLonger gaps in hardware refresh
Limited opportunity to change architecture
Why make the move to the cloud?
Increasing labor time spent on maintenance functions vs new project/creative solution work
Infrastructure team not able to scale configurations to meet peak loads for critical academic events
Operational Challenges
Why make the move to the cloud?Other Risks
Natural disasters Security
Resource Management
Challenges
Challenges
Challenges
Shock
Denial
Anger
Bargaining
Depression
Acceptance
Positioning for Maneuvers
1.Define needs – How to position IT as a Service2.Contract a cloud broker3.Determine scope of cloud offerings4.Put RFPs on street
UKAT Maneuvers to get out of McVey HallManeuver Current State
1) Move ERP system to private cloud In strategy phase – determiningconfiguration requirements and scope
2) Move server and VM farms Documenting all servers and their purpose – evaluating VM strategy
3) Move High Performance Research Computing to co-location facility
In strategy phase – documenting research needs
4) Move email/office tools to Microsoft Office 365
In process
5) Everything else Not started
Impact to services
Lessons Learned (so far)
Lessons Learned (so far)
Contact Info:Earl BegleyTwitter: @earlbegleyLinkedIn: www.linkedin.com/in/earlbegleyBlog: earlbegley.comEmail: [email protected]
Questions?
Contact Info:Earl Begley
Twitter: @earlbegleyLinkedIn: www.linkedin.com/in/earlbegley
Blog: earlbegley.comEmail: [email protected]