Published on

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide


  1. 1. http://www.bripblap.com/uploads/cloudbridge.jpg Stepping into the Cloud Risks, Rewards, Realities Terry Gray , PhD Assoc VP, Technology Strategy UW Technology Erik Lundberg Director, CS Laboratory Computer Science & Engineering 14 October 2009
  2. 2. http://blog.host1plus.com/wp-content/uploads/2009/08/Cloud-computing013-300x300.jpg Agenda <ul><li>Background </li></ul><ul><li>UW Strategy </li></ul><ul><li>Risks </li></ul><ul><li>Compliance </li></ul>
  3. 3. What's Inside that Cloud? the Internet + Servers From Wikipedia article on Cloud Computing Cloud Computing = IT stuff running in someone else's data center
  4. 4. Kinds of Cloud Services <ul><li>Infrastructure as a Service e.g. Amazon EC2, S3 </li></ul><ul><li>Platform as a Service e.g. Google AppEngine </li></ul><ul><li>Software as a Service (SaaS) e.g. Hotmail 1994 </li></ul>Varying degrees of shared vs. dedicated, e.g. “Cloud vs. Hosted”
  5. 5. Cloud Computing Ingredients <ul><ul><li>Old “service bureau” paradigm cf. ADP, 1949 </li></ul></ul><ul><ul><li>Revenue from ads + subscriptions </li></ul></ul><ul><ul><li>Data mining for personalizing the ads </li></ul></ul><ul><ul><li>Modern technology (web, Internet, datacenter) </li></ul></ul><ul><ul><li>Low cost via high-scale, more self-support </li></ul></ul><ul><ul><li>Disintermediation (self-service) </li></ul></ul>
  6. 6. Natural Evolution Who ya gonna call (for commodity IT)? Individual Departmental Central Cloud Goodbye “IT priesthood”... Hello “Consumer Computing” In the beginning...
  7. 7. Cloud Currency users are the inventory http://www.library.drexel.edu/blogs/librarylog/dollars.gif http://www.cksinfo.com/clipart/people/bodyparts/eyes/eyeballs.png http://thomaslarock.com/wp-content/uploads/2009/06/datamining.jpg
  8. 8. So... Cloud Computing: Hot or Not? Nick Carr Richard Stallman Larry Ellison Bill Gates Eric Schmidt
  9. 9. It must be Hot if ... http://www.virtualizationconference.com/node/597208 http://gemsres.com/section/156/Cloud-Computing-307x100.jpg http://res.sys-con.com/story/dec08/770227/CloudComputingBook_MichaelMiller.JPG http://img.brajeshwar.com/cloud-computing-vote.jpg
  10. 10. UW meets the Cloud
  11. 11. Cloud Apps @ UW 64K UW users 60% of students ALREADY forward their UW email!
  12. 12. Premises <ul><li>Cloud computing is a big deal </li></ul><ul><li>UW should encourage use of cloud services, consistent with compliance obligations </li></ul><ul><li>Compliance risk is reduced via partner contracts </li></ul><ul><li>A dual-vendor strategy is appropriate for UW </li></ul><ul><li>Including faculty, staff and students maximizes collaboration potential </li></ul>
  13. 13. Cloud Partnership Motivations <ul><li>This is where our community is (or will be)! </li></ul><ul><li>Enhance the cloud services </li></ul><ul><li>Improve regulatory compliance </li></ul><ul><li>Eventual reallocation of IT resources </li></ul>IT Goal: info access & collaboration, any time, place, device -> Cloud computing supports this goal
  14. 14. http://blogs.msdn.com/blogfiles/stevecla01/WindowsLiveWriter/MicrosoftGoogleandCloudWars_ACE7/03cloud_xlarge1_thumb.jpg A Tale of Two Clouds (for SaaS) -One size does not fit all -We want both partners to succeed
  15. 15. Progress <ul><li>MS and Google pilots successfully completed </li></ul><ul><li>Campus launch to students and alums on 9/28/09 </li></ul><ul><li>CSE launch ... </li></ul><ul><li>Planning for 2010 phase-out of student UA svcs </li></ul><ul><li>(Per STF Committee funding decision) </li></ul>
  16. 16. Lessons <ul><li>Free services are not free </li></ul><ul><ul><li>Moving targets, startup problems, service culture </li></ul></ul><ul><ul><li>Cloud Conundrum: Integration adds value & cost </li></ul></ul><ul><li>Collaboration Barriers </li></ul><ul><ul><li>Multiple account madness </li></ul></ul><ul><ul><li>Interoperability </li></ul></ul><ul><li>Pushback </li></ul><ul><ul><li>Students: “Where's the beef” (vs. existing options) </li></ul></ul><ul><ul><li>Faculty: privacy, security, data ownership/mining </li></ul></ul><ul><li>Help desk load: OK so far (no forced migrations yet) </li></ul>
  17. 17. 2010 Plans <ul><li>Cloud Service Enhancement </li></ul><ul><ul><li>SSO for Outlook Live </li></ul></ul><ul><ul><li>Microsoft BPOS (Dedicated version!) </li></ul></ul><ul><ul><li>Group management features </li></ul></ul><ul><ul><li>Improved calendar interoperability </li></ul></ul><ul><li>On-Premise Service Retirement </li></ul><ul><ul><li>Student UA services (at least email) </li></ul></ul><ul><ul><li>Central Exchange/Sharepoint services </li></ul></ul><ul><li>Progress gated by </li></ul><ul><ul><li>Service maturity </li></ul></ul><ul><ul><li>Migration and support costs </li></ul></ul>
  18. 18. Impact on UA Services <ul><li>Student Tech Fee Committee decision </li></ul><ul><ul><li>UA services for students have been de-funded </li></ul></ul><ul><ul><li>Thus, they will migrate to cloud soon... </li></ul></ul><ul><li>Email </li></ul><ul><ul><li>No new student Deskmail accounts as of Jan 2010 </li></ul></ul><ul><ul><li>Migrate existing student accounts later in 2010 </li></ul></ul><ul><ul><li>Students may continue to use consumer accts or MS and Google partner accts </li></ul></ul><ul><li>Web publishing, etc </li></ul><ul><ul><li>Roadmap will be developed during Fall quarter </li></ul></ul>
  19. 19. Risks <ul><li>User Concerns </li></ul><ul><ul><li>Service maturity </li></ul></ul><ul><ul><li>Privacy </li></ul></ul><ul><ul><li>Interoperability </li></ul></ul><ul><li>Institution Concerns </li></ul><ul><ul><li>Operational risk </li></ul></ul><ul><ul><li>Financial risk </li></ul></ul><ul><ul><li>Compliance risk </li></ul></ul>
  20. 20. Service Maturity http://mrgadget.co.za/catalog/images/Moving_Target.jpg
  21. 21. Total Information Awareness
  22. 22. Interoperability example: the calendaring problem http://www.loc.gov/exhibits/bobhope/images/vcvg20.jpg Outlook/ Exchange User IT Staff Google Calendar User
  23. 23. Institutional Risks <ul><li>Operational (service or business failures) </li></ul><ul><ul><ul><li>Individuals have biggest stake here for now </li></ul></ul></ul><ul><li>Financial (surprise support or integration costs) </li></ul><ul><ul><ul><li>High-touch support model could kill future savings </li></ul></ul></ul><ul><li>Compliance (failure -> liability cost) </li></ul><ul><ul><ul><li>Primarily unauthorized disclosure of sens. Info </li></ul></ul></ul><ul><ul><ul><li>Limited forensics ability -> notification cost </li></ul></ul></ul><ul><ul><ul><li>Ability to respond to legal requests for data </li></ul></ul></ul>NB: 1) these kinds of business risks are uninsured 2) departments assume $$ liability for failure to comply w/UW policies 3) data guidelines need to cover all cases, not just cloud computing
  24. 24. Risk Mitigation compared with status-quo Contract terms added Data security guidelines to define appropriate use Partner contracts provide for UW account control Inability to comply with FERPA Disclosure of confidential data Inability to respond to eDiscovery request
  25. 25. Cloud use is soaring despite concerns The cloud enables more collaboration So we need to enable the cloud...
  26. 26. End of Terry's Part... Go Erik!
  27. 27. Questions http://www.geo.me/images/cloud.jpg?1249871890