Cloud Computing UW

1. Cloud Computing @ UW 07 October 2008 Terry Gray Associate Vice President, University Technology Strategy & Chief Technology Architect University of Washington

5. UW by the numbers (2007)

6. Key Challengesfor Central IT at UW Budget issues Political & cultural shifts(central ? decentral) Technology shifts... e.g. Cloud Computing

7. The rise of utility computing

8. CC Quote #1 �It's stupidity. It's worse than stupidity: it's a marketing hype campaign.� �Somebody is saying this is inevitable � and whenever you hear somebody saying that, it's very likely to be a set of businesses campaigning to make it true."

9. CC Quote #2 �The interesting thing about cloud computing is that we�ve redefined cloud computing to include everything that we already do.�

10. CC Quote #3 "When people talk about cloud computing, they're talking just about taking some stuff, putting it outside the firewall, and perhaps putting it on servers that are also shared or storage systems."

11. So... Cloud Computing:Hot or Not?

12. Bill @ WWDC "We're taking everything we do at the server level and saying we will have a service that mirrors that exactly. It's getting us to think about data centers at a scale that we haven't thought of before... [to create] a mega-data center that Microsoft and only a few others will have."

13. MS Prognosis "We believe that by 2010, at least 25 percent of our Office users will be using some kind of [online] service provided by Microsoft"

14. What is Cloud Computing?�Like having your dinner delivered� SaaS: Software as a Service PaaS: Platform as a Service Not "outsourcing the IT dept"... But includes hosted svcs that overlap current central svcs Not highly-negotiated custom contract services General model: low cost via scale and tech & contract standardization (apts vs. cust. houses)? Full circle: Mainframe ? Mini ? PC ? "Cloudframe" cf. Service Bureaus and Value-Added-Networks

15. Different Cloud Computing Layers(Example players)?

16. CC Attractions Cost Flexibility; rapid scalability and de-scalability Data replication; geo-diversity Easier cross-institution collaboration Any {time, place, device} access via web browser Alternative if dept'l or central IT non-responsive This is where our students/fac/staff will be! Priorities: no need to focus on commodity IT Future of computing, esp. eScience

17. CC Concerns Loss of control (cf. central/decentral debate)? Integration: enterprise & federated auth; SSO Interop: with key enterprise apps (esp cal)? Accessibility and UI limitations of web apps Reliability, performance, security; offline access Features; changes; vendor lock-in Policy/compliance concerns (privacy, eDiscov.)? Breach forensics and mitigation Business �surprises�; Support; More Logins Consequences of �Creative Destruction�

18. Why use cloud-computing?

19. Why not use cloud-computing?

20. Why some enterprises are not interested in SaaS Forrester Research study: 66% Integration issues 61% Total cost of ownership concerns 55% Lack of customization 50% Security concerns 42% "We can't find the specific app. we need" 39% Complicated pricing models 39% Application performance 34% "We're locked in with our current vendor"

21. Sweet Spot? Accepted wisdom: Small � Medium BusinessPaaS especially attractive for Start-Ups BUT: large research universities can be thought of as federations of hundreds of independent businesses... STILL: Higher-Ed is split over CC use Datacenter issues will drive eScience choices Large businesses are just starting to embrace e.g. GE's 400K seat Zoho deal

22. Cloud Computing ApplicabilityWill grow over time

23. UW Is Already Using CC More than half our students already forward their email outside UW Approx 700 sign-ups for Google Team Edition Significant use of MS Live & Google Docs Departments using SaaS, e.g. Blackboard Departments using PaaS, e.g. EC2/S3 Facebook!!! UW focus: productivity tools, not enterprise apps

24. Current UW Cloud Activities Individual (e.g. MS Live, Google docs, Gmail...)? Departmental (e.g. gCal, Blackboard, EC2/S3)? Central Policy/guideline framework Alumni Email via MS ExchangeLabs Google Apps discussion Broader MS apps discussion Investigating hosted exchange/sharepoint options Goal: enable individual & dept'l use with better compliance

25. Things We Need from the Cloud All the usual (e.g. reliability, perf, security, cost) Serious business partners (e.g. security, SLAs) Flexibility, choice Interoperability Interoperability Interoperability

26. Key: Interoperability Across cloud silos Across desk/mobile platforms Across institutions With enterprise IAM With stds-based thick clients Poster-child: Calendaring Beware the famous �Microsoft Myopia�... The cloud is different

27. Interoperability Model

28. Contract Concerns CISO Security Ability to do forensics after a compromise Liability transfer Attorney General Compliance, especially eDiscovery Also ITAR, HIPAA, FERPA, etc Indemnification

29. Microsoft's Challenge Software-and-Service theme: Innovator's Dilemma: new cannibalizes old How to preserve cash cow while embracing cloud? Natural focus on traditional base Will focus on base undermine larger opportunity? We in central IT empathize with this challenge!! Key to broader success: interoperability standards

30. Discussion Topics How committed is Microsoft to interoperability? Web-based ads vs. thick clients Goal of broad contracts w/cloud providers Does a contract increase or decrease risk? Consequences of no institutional contract? Geographic issues: PRA/FOIA, Patriot Act, etc Health care opportunity; HIPAA Policy/guidelines for using cloud services... Relationship to data security standard?

31. Any Questions?