The Advantages of Cloud - Why and Disadvantages

Transcription

1 Creative Commons licensed image courtesy of

2 Today: Why the cloud: Reasons for a cloud strategy Examples and the ND path Advantages Pitfalls Lessons learned A day in the life of going cloud first

3 Reasons for a Cloud Strategy

4

5

6 Frustration

7 Flexibility (It turns out that searching for Creative Commons licensed images of flexibility leads to strange places...let s stick with text here)

8 Key terms: SaaS, PaaS, IaaS

9 Four Notre Dame tests of the cloud CMS 3. Backups 4. Authentication

10 Initial move/test took three days (10/2012) Performance/scalability test results exceeded expectations Reduced complexity/cost Site went live 1/2013

11

12 Success

13 The payoff

14 Our CMS: Conductor.nd.edu Conductor: ND-developed content management system 435+ web sites 4+ million views/month Hosted in RackSpace - plagued by unstable hardware issues

15 What we did Employed Elasticache Switched from MySQL server to RDS Began process to enable scaling Externalized data in EBS (and after learning a bit, then in S3) Used sub-account to simplify sysadmin permissions and billing

16

17 Faster response at half the cost

18 Authentication High availability for off-campus students, faculty, and staff Auto failover with Route 53 Client Gateway VPN for Domain Controller sync

19 Backups Netbackup to manage 300 TB of backups Chose Panzura as cloud storage gateway partner Backing up to S3 Any server restore since summer 2014 being retrieved through Panzura device Able to avoid augmenting/replacing NetApp on premises footprint

20 Notre Dame s Path to the Cloud

21 Going Google In January of 2014, we committed to moving our entire campus to Google . Not everybody was initially delighted.

22 MarCo mm Training & Support Technic al Project Schedule Spring Summer Fall Planning Convene teams Select migration partner Plan & Report Execution Go Live 1 Go Live 2 Go Live 3 Operationalization Operational/Support Planning Research, Implement Google Groups, Test Integrations, Provisioning, Routing Execution Core IT Team (~25 ppl) Early Adopters (5%) Full Campus Transition (95%) Operationalization Operational/Support Planning Execution Operationalization Planning Preparatory Training Go Live Operational Back-to-School Planning Execution Operationalization Planning Awareness/ Excitement Transactional/Tr aining Communication Go Live Operational Back-to-School Commencement (May 18) Classes start (Aug 26)

23

24 Migration Stats Early Adopter Full Campus Total Number of accounts migrated ,449 16,273 Amount of data migrated 1.5 TB 9.1 TB 10.6 TB Number of items migrated 17.2 million 88.5 million million

25 In the end. We decommissioned 24 physical servers, resulting in hardware savings realized over three years. We recovered 60 TB of storage (which we immediately used elsewhere) We decreased staff dedicated to , freeing resources to use elsewhere

26 Ok, so now what?

27 The ND Cloud First initiative

28

29 Cloud Advantages

30 Better infrastructure

31 Pay for what you need, not how the vendor sizes the product

32 A chance to start clean(er)

33 Quickly adapt to demand

34 And that s not just IaaS - Purchase and support SaaS solutions quickly - Leverage vendor s ability to scale - Pay for what you need as you need it - Allow groups to experiment more easily

35 Spend less time doing (some types of) support

36 Spent more time adding value SaaS: integration and customer support PaaS: Customization IaaS: Scripted builds Horizontal auto-scaling Optimization

37 Take a deep breath It s not all roses. There are pitfalls!

38

39 Pitfalls

40 Buy-in - Executive - Financial - Technical staff - Business staff and partners - Cloud vendor partners really help too

41 Organizational strain points - Process - Training and expertise - Inter-organizational stress points - In-organization stress points - Budget models - Trust

42 Changing cost models Capital costs change to operating expenses Servers and storage actually cost Scaling instead of figuring out problems costs Understanding cost centers is important Financial responsibility gets delegated deeper down the stack

43 Bad design choices How you integrate How you scale How you monitor (or don t) Financial models And many more...

44 Not everything translates well The metaphors and management structures may be different Separation of duties may have to change Basic assumptions that used to work can cause problems

45 Some workloads may not make sense (yet) - Really custom applications and systems - Places where latency may be an issue - If local access or control is required (or mandated) - Things that only scale by making the hardware bigger - If there are regulatory requirements (but that s changing quickly)

46 Now is the time to change how you think about datacenters and infrastructure

47 A new way of thinking...

48 We don t have to build our own castles anymore most of the time.

49

50 And then a DBA walks in the door and says: Hey, you can t do that with data! This actually happened.

51 Ok! So what do we do? - Leverage the cloud where it makes sense - Learn through doing and build confidence - Look at where your big spends are - people, time, money - Compare that to where you could save - Get some buy-in at the top to try this newfangled cloud thing

52 Questions?