Private clouds and enterprise IT: Two closing thoughts on metaphor addiction and hybrid reality
•Descargar como KEY, PDF•
2 recomendaciones•7,391 vistas
The document discusses private clouds and enterprise IT. It makes two main points. First, there may be a return to more centralized IT models as public clouds become more capable of supporting complex enterprise workloads. Second, we are addicted to old metaphors for technology and clouds will likely not resemble the common metaphors of "cloudbursting" or simple cloud hosting. The reality for enterprises will be hybrid cloud models that combine on-premise and on-demand services tailored to specific workloads and policies.
Recomendados
Recomendados
Más contenido relacionado
Destacado
Similar a Private clouds and enterprise IT: Two closing thoughts on metaphor addiction and hybrid reality
Similar a Private clouds and enterprise IT: Two closing thoughts on metaphor addiction and hybrid reality (20)
Más de Alistair Croll
Más de Alistair Croll (20)
Último
Último (20)
Private clouds and enterprise IT: Two closing thoughts on metaphor addiction and hybrid reality
- 1. Private clouds and enterprise IT Two closing thoughts
- 2. Two points Ironically, a return to centralization We’re addicted to old metaphors
- 3. Let’s talk about cars. First: retooling the factory floor on the fly.
- 10. The abdication of authority (and responsibility.) http://www.flickr.com/photos/abulic_monkey/ 130899453/
- 11. You have no right to an opinion This is the pact of on-demand IT Abstraction means abdicating your right to architecture One size fits all meets Jack of All Trades http://www.flickr.com/photos/jamisonjudd/2433102356/
- 13. On-premise On-demand Adaptive Pros Lots of control economics Experimentation DR, connectivity New risks cost more Compliance issues Cons Operational costs Unpredictable & distractions costs
- 14. A return to centralization.
- 15. “Compared to the cost of moving bytes around, everything else is free.” Microsoft technical fellow Dr. Jim Gray, 2003 http://www-users.cselabs.umn.edu/classes/Spring-2009/csci8980-ass/Jim%20Gray.pdf
- 16. Hairy, smoking golf balls http://www.flickr.com/photos/onigiri_chang/4791909127/
- 17. Cloud in a box. AKA the new mainframe.
- 18. Clouds have “surface tension” Strong bonds between storage, processing Portable workloads Mobile clients
- 19. Second: metaphor addiction Just because you understand virtual machines doesn’t make them good for you.
- 22. 1 cm
- 23. 1 cm
- 24. Grams Centimeters Millilitres 1 cm
- 27. We love our metaphors.
- 28. They restrict our thinking.
- 29. So what will enterprise clouds look like?
- 30. The myth: cloudbursting Normal load
- 31. The myth: cloudbursting Load Normal load Traffic spikes
- 32. The startup: cloud hosting Clouds are obvious when you start from scratch 3rd-party 3rd-party Uncertain futures payment service storage service No capital at hand High rate of architectural change Cache App Storage tier tier tier
- 33. The enterprise reality: hybrid clouds, services
- 34. The enterprise reality: hybrid clouds, services PaaS, WebVM, AppVM, DB VM, cloud storage
- 35. The enterprise reality: hybrid clouds, services Custom apps, PaaS, WebVM, AppVM, authentication DB VM, cloud storage services, ERP, SAN/ NAS, CRM
- 36. The enterprise reality: hybrid clouds, services Cloud “Gateway” functions Custom apps, PaaS, WebVM, AppVM, authentication DB VM, cloud storage services, ERP, SAN/ NAS, CRM
- 39. Storage media
- 40. Computer hardware Storage media
- 41. Operating system Computer hardware Storage media
- 42. Software Operating system Computer hardware Storage media
- 43. Query language Software Operating system Computer hardware Storage media
- 44. Query language Let’s just call this a database, Software ‘mmkay? Operating system Computer hardware Storage media
- 45. Edge UI Centralized processing
- 46. Mobile, VDI, IVR, etc. Edge UI Centralized processing
- 47. Mobile, VDI, On-premise On-demand IVR, etc. Edge UI Centralized processing
- 48. Local storage & processing Mobile, VDI, On-premise On-demand IVR, etc. Edge UI Centralized processing
- 49. Local storage & Workload-specific configurations processing Mobile, VDI, On-premise On-demand IVR, etc. Edge UI Centralized processing
- 50. User-specific interfaces Local storage & Workload-specific configurations processing Mobile, VDI, On-premise On-demand IVR, etc. Edge UI Centralized processing
- 51. User-specific interfaces Shared storage & processing Local storage & Workload-specific configurations processing Mobile, VDI, On-premise On-demand IVR, etc. Edge UI Centralized processing
- 52. Self-service & automation User-specific interfaces Shared storage & processing Local storage & Workload-specific configurations processing Mobile, VDI, On-premise On-demand IVR, etc. Edge UI Centralized processing
- 53. Self-service & automation User-specific interfaces Shared storage & processing Local storage & Workload-specific configurations processing Mobile, VDI, On-premise Policies On-demand IVR, etc. Edge UI Centralized processing
- 54. Self-service & automation User-specific interfaces Shared storage & processing Local storage & Workload-specific configurations processing Mobile, VDI, On-premise Policies On-demand IVR, etc. Edge UI Centralized processing The 3 C’s of cloud policy: Cost Compliance
- 56. Thanks! @acroll
Notas del editor
- Let’s talk about cars for a minute. A car is a mode of transportation; but if you want to get from point A to point B, you have some decisions to make.=
- There are lots of different car business models
- At one extreme, you could be a car manufacturer. You’d have complete control over every aspect of your car, even though the cost of doing so would be very high. But you could still build cars from parts, and get them road-certified. It wouldn’t scale very well as demand increased, so this is the domain of hobbyists (who need high customization) or large manufacturers (who need economies of scale)
- For most of us, the answer to transportation is to own a car. You’re not responsible for design – though you have some choice of models and features – but you are liable for everything. You have to finance it, maintain it, and so on.
- If you’re a traveller, then you rent. This is a different model, with different responsibilities. You’re still at fault if you scratch or hit something, and still need to know directions, but someone else finances the deal and handles storage, cleaning, and other things. And you’re paying for what you use, not for the entire asset.
- A car hire service abdicates even more control – you can still decide where to go and how to get there, pickup and dropoff times, etc., but everything else is the driver’s responsibility. You have only marginal control over the car model.
- A taxicab takes this to the ultimate extreme: pay-as-you-drive economics, and nothing’s your fault provided you’re well behaved in the back seat. You have almost no control over the platform.
- These are all degrees of abdication and abstraction. Sometimes a taxi makes sense – for example, when we’re going from place to place in a city. Other times, building our own makes sense – for example, if we’re landing on the moon.
- This is a pretty obvious analogy to the computer industry. Sometimes, on-premise bare metal makes sense (and it’s expensive, but very customizable.) More likely, you’ll buy off-the-shelf components and define your own architecture. And other times, on-demand computing makes sense, either because of temporary workloads or because of elasticity.
- But there’s a change in computing. The advent of virtualization has made us able to – in the analogy – retool the factory floor as needed. Atop our physical architecture, we have the ability to define virtual architectures suited to specific application workloads: OLAP processing, message queues, data analysis, batch computing, and so on.
- This raises the question: where’s the abdication “sweet spot”? How do I find a tradeoff between “I want cloud efficiency and agility” and “I want to control it all”?
- What we’re seeing is the emergence of a new class of mainframe – for an era where the business and the workload, not IT’s hardware and platform constraints, is driving the architecture. Large multi-cabinet devices, holding storage, processing, network, automation, and control systems look just like mainframes. But inside, they can be retooled on the fly by the business to accommodate workloads.
- This simple fact dictates how we build computing architectures today. We put the UI out near the user, since that’s personal and unique – I’m looking at my flights on a Blackberry, you’re looking at yours on a desktop. Different content, different Uis. But we put the shared processing and computing together, in the middle. To distribute information on all flights to all of us would be a nightmare; and the code that has to chew on all those flights needs to live near it to minimize data movement.
- Let’s talk about cars for a minute. A car is a mode of transportation; but if you want to get from point A to point B, you have some decisions to make.=
- I want to talk about the British pint.
- Anyone know what this is?
- The metric system makes sense
- The metric system makes sense
- An enterprise will adopt clouds opportunitstically. As utility services make sense, we’ll connect on-premise and on-demand platforms to one another.
- An enterprise will adopt clouds opportunitstically. As utility services make sense, we’ll connect on-premise and on-demand platforms to one another.
- An enterprise will adopt clouds opportunitstically. As utility services make sense, we’ll connect on-premise and on-demand platforms to one another.
- This is about combining recipes and “composed designs” -- a concept that’s familiar to proponents of SOA.
- When IT architects want to build something, they have a set of proven designs for doing so. A database is an example of this—it’s a combination of storage (disk) and a particular way of arranging things (tables and indexes) and language (structured query language, or SQL). We’ve learned that a database is a good prefab building block, so we use it. The alternative is to build it all, from scratch, writing to the disk itself.
- When IT architects want to build something, they have a set of proven designs for doing so. A database is an example of this—it’s a combination of storage (disk) and a particular way of arranging things (tables and indexes) and language (structured query language, or SQL). We’ve learned that a database is a good prefab building block, so we use it. The alternative is to build it all, from scratch, writing to the disk itself.
- When IT architects want to build something, they have a set of proven designs for doing so. A database is an example of this—it’s a combination of storage (disk) and a particular way of arranging things (tables and indexes) and language (structured query language, or SQL). We’ve learned that a database is a good prefab building block, so we use it. The alternative is to build it all, from scratch, writing to the disk itself.
- When IT architects want to build something, they have a set of proven designs for doing so. A database is an example of this—it’s a combination of storage (disk) and a particular way of arranging things (tables and indexes) and language (structured query language, or SQL). We’ve learned that a database is a good prefab building block, so we use it. The alternative is to build it all, from scratch, writing to the disk itself.
- When IT architects want to build something, they have a set of proven designs for doing so. A database is an example of this—it’s a combination of storage (disk) and a particular way of arranging things (tables and indexes) and language (structured query language, or SQL). We’ve learned that a database is a good prefab building block, so we use it. The alternative is to build it all, from scratch, writing to the disk itself.
- When IT architects want to build something, they have a set of proven designs for doing so. A database is an example of this—it’s a combination of storage (disk) and a particular way of arranging things (tables and indexes) and language (structured query language, or SQL). We’ve learned that a database is a good prefab building block, so we use it. The alternative is to build it all, from scratch, writing to the disk itself.