Cloud and the Futureof Networked Systems<br />Why “big, flat and dumb” isn’t enough<br />James Urquhart<br />CNET | The Wi...
James Urquhart<br />@jamesurquhart<br />CNET | The Wisdom of Clouds<br />
In 20 years of distributed systems practice, what have I learned?<br />
We need to simplify operations from the point of view of the application.<br />
Application (in theory)<br />a. A type of job or problem that lends itself to processing or solution by computer: Inventor...
Application (in reality)<br />SaaS<br />Data/Metadata<br />Config<br />Policy<br />
Application (in reality)<br />SaaS<br />PaaS<br />Data/Metadata<br />Config<br />Policy<br />Data/Metadata<br />Config<br ...
Application (in reality)<br />SaaS<br />PaaS<br />IaaS<br />Data/Metadata<br />Config<br />Policy<br />Data/Metadata<br />...
Here’s the thing…<br />
Cloud is an<br />operations model.<br />
Cloud is an application centric operations model.<br />
Why?<br />
Prior to cloud, we were server centric…<br />
Pre-<br />Cloud<br />
Pre-<br />Cloud<br />OS<br />OS<br />OS<br />VM<br />VM<br />VM<br />
App<br />App<br />App<br />App<br />App<br />App<br />Pre-<br />Cloud<br />App<br />App<br />App<br />OS<br />OS<br />OS<b...
With the adoption of cloud, we are now application centric…<br />
Application<br />Cloud<br />Config<br />Code<br />Data<br />Policy<br />
Application<br />Cloud<br />Config<br />Code<br />Data<br />Policy<br />Service(s)<br />Other Services<br />
Application<br />Cloud<br />Config<br />Code<br />Data<br />Policy<br />Service(s)<br />Other Services<br />Infrastructure...
Any cloud service or enabling technology must look at solutions from an application perspective.<br />
So, what is the network’s role in cloud computing?<br />
Application developers want one thing from the network…<br />…invisibility.<br />
The temptation is…<br />
Big<br />
Flat<br />
Dumb<br />
Put a little nicer…<br />
Unified<br />
Simplified<br />
Pushed to the Edge<br />
One topology to rule them all…<br />
…and in the darkness bind them.<br />
The problem is that current cloud network architecture was designed for one purpose…<br />
…web applications.<br />
Relatively few processes…<br />UI<br />Service<br />Data store<br />
…with one or few owners…<br />UI<br />Service<br />Data store<br />
…spread over 10s/100s/1000s of servers<br />
The good news is that this also works out great for other “big data” applications.<br />
For example:<br />Data Mining<br />
For example:<br />Data Mining<br />Models/Simulations<br />
For example:<br />Data Mining<br />Models/Simulations<br />“Recombination”<br />
The bad news is this is a lousy model for most enterprise IT models.<br />
Many processes…<br />Sales<br />Pipeline<br />CRM<br />GUI<br />Call<br />Center<br />Records<br />Mgmt<br />Doc<br />Mgmt...
…on many technologies…<br />SF.com<br />Oracle<br />CRM<br />Five9<br />FileHold<br />Alfresco<br />Share-point<br />Chatt...
…with many owners…<br />Sales<br />Pipeline<br />ERP<br />Module A<br />Call<br />Center<br />Records<br />Mgmt<br />Doc<b...
…each using a few, maybe 10s of servers.<br />
The enterprise doesn’t have a scale-out problem…<br />
The enterprise has a…<br />Integration<br />Compliance<br />Management<br />…problem.<br />
This means the actual requirements for cloud infrastructure don’t stop at the application.<br />
There’s…<br />Integration<br />Legal Requirements<br />Traffic Management<br />Troubleshooting<br />Security<br />Etc.<br />
For example,<br />let’s take security…<br />
Each solution will almost certainly be only part of the system(s) that is/are being secured.<br />
Security will be distributed throughout the “cloud stack”<br />
Security will be distributed throughout the network stack<br />
Security will be distributed across geographical and topological boundaries<br />
Security must become <br />multi-tenant<br />
Security must scale.<br />
Security must scale.<br />* Try doing that with compliance… <br />
Security must meet a wide variety of application needs.<br />
Same goes for<br />Application Management<br />
Same goes for<br />Performance Management<br />
Same goes for<br />QoS<br />
Same goes for<br />Load Distribution<br />
Same goes for<br />Etc.<br />
Same goes for<br />Etc., Etc.<br />
Same goes for<br />Etc., Etc., Etc.<br />
So how will the network adapt?<br />
Five ways:<br />
Data center network architectures will “flatten”.<br />
FabricPath<br />OTV<br />DCI<br />Open Source<br />QFabric<br />OpenFlow<br />Open vSwitch<br />
The network will adapt to new dominant payloads and traffic patterns.<br />
App<br />App<br />App<br />App<br />App<br />App<br />App<br />App<br />App<br />App<br />App<br />App<br />OS<br />OS<br ...
The network will introduce new abstractions to simplify configuration and operation.<br />Private<br />Cloud<br />Public<b...
Donabe<br />
The network and its capabilities will become services to be consumed by cloud services.<br />IaaS<br />PaaS<br />SaaS<br /...
VPC<br />
Thanks!<br />
Cloud and the Futureof Networked Systems<br />Why “big, flat and dumb” isn’t enough<br />James Urquhart<br />@jamesurquhar...
Upcoming SlideShare
Loading in...5
×

Glue con2011 future_of_net_systems

1,622

Published on

Understanding the network's role in cloud computing requires understanding the effect of cloud computing on networking. The end result is five key trends in cloud networking, as presented by James Urquhart from Cisco Systems, and author of CNET's The Wisdom of Clouds

Published in: Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,622
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
45
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Glue con2011 future_of_net_systems

  1. 1. Cloud and the Futureof Networked Systems<br />Why “big, flat and dumb” isn’t enough<br />James Urquhart<br />CNET | The Wisdom of Clouds<br />Program Manager, OpenStack@Cisco<br />
  2. 2. James Urquhart<br />@jamesurquhart<br />CNET | The Wisdom of Clouds<br />
  3. 3. In 20 years of distributed systems practice, what have I learned?<br />
  4. 4.
  5. 5. We need to simplify operations from the point of view of the application.<br />
  6. 6. Application (in theory)<br />a. A type of job or problem that lends itself to processing or solution by computer: Inventory control is a common business application.<br />b. A program used for a particular use (as opposed to a system)<br />
  7. 7. Application (in reality)<br />SaaS<br />Data/Metadata<br />Config<br />Policy<br />
  8. 8. Application (in reality)<br />SaaS<br />PaaS<br />Data/Metadata<br />Config<br />Policy<br />Data/Metadata<br />Config<br />Policy<br />Code<br />
  9. 9. Application (in reality)<br />SaaS<br />PaaS<br />IaaS<br />Data/Metadata<br />Config<br />Policy<br />Data/Metadata<br />Config<br />Policy<br />Data/Metadata<br />Config<br />Policy<br />Custom<br />Code<br />Code<br />Libraries<br />OS/Middleware<br />VM<br />
  10. 10. Here’s the thing…<br />
  11. 11. Cloud is an<br />operations model.<br />
  12. 12. Cloud is an application centric operations model.<br />
  13. 13. Why?<br />
  14. 14. Prior to cloud, we were server centric…<br />
  15. 15. Pre-<br />Cloud<br />
  16. 16. Pre-<br />Cloud<br />OS<br />OS<br />OS<br />VM<br />VM<br />VM<br />
  17. 17. App<br />App<br />App<br />App<br />App<br />App<br />Pre-<br />Cloud<br />App<br />App<br />App<br />OS<br />OS<br />OS<br />VM<br />VM<br />VM<br />
  18. 18. With the adoption of cloud, we are now application centric…<br />
  19. 19. Application<br />Cloud<br />Config<br />Code<br />Data<br />Policy<br />
  20. 20. Application<br />Cloud<br />Config<br />Code<br />Data<br />Policy<br />Service(s)<br />Other Services<br />
  21. 21. Application<br />Cloud<br />Config<br />Code<br />Data<br />Policy<br />Service(s)<br />Other Services<br />Infrastructure<br />
  22. 22. Any cloud service or enabling technology must look at solutions from an application perspective.<br />
  23. 23. So, what is the network’s role in cloud computing?<br />
  24. 24. Application developers want one thing from the network…<br />…invisibility.<br />
  25. 25. The temptation is…<br />
  26. 26. Big<br />
  27. 27. Flat<br />
  28. 28. Dumb<br />
  29. 29. Put a little nicer…<br />
  30. 30. Unified<br />
  31. 31. Simplified<br />
  32. 32. Pushed to the Edge<br />
  33. 33. One topology to rule them all…<br />
  34. 34. …and in the darkness bind them.<br />
  35. 35. The problem is that current cloud network architecture was designed for one purpose…<br />
  36. 36. …web applications.<br />
  37. 37. Relatively few processes…<br />UI<br />Service<br />Data store<br />
  38. 38. …with one or few owners…<br />UI<br />Service<br />Data store<br />
  39. 39. …spread over 10s/100s/1000s of servers<br />
  40. 40. The good news is that this also works out great for other “big data” applications.<br />
  41. 41. For example:<br />Data Mining<br />
  42. 42. For example:<br />Data Mining<br />Models/Simulations<br />
  43. 43. For example:<br />Data Mining<br />Models/Simulations<br />“Recombination”<br />
  44. 44. The bad news is this is a lousy model for most enterprise IT models.<br />
  45. 45. Many processes…<br />Sales<br />Pipeline<br />CRM<br />GUI<br />Call<br />Center<br />Records<br />Mgmt<br />Doc<br />Mgmt B<br />Doc<br />Mgmt A <br />Soc<br />Media<br />CRM<br />App Tier<br />Data<br />Service<br />Video<br />Conf<br />Collab<br />Office Apps<br />Customer DB<br />Product<br />Catalog<br />VOIP<br />Catalog Data<br />Dept<br />App<br />etc.…<br />
  46. 46. …on many technologies…<br />SF.com<br />Oracle<br />CRM<br />Five9<br />FileHold<br />Alfresco<br />Share-point<br />Chatter<br />Oracle<br />CRM<br />Java/WS-*<br />Tandberg<br />Yammer<br />MSFT<br />Office<br />Oracle RDBMS<br />MF COBOL<br />Cisco<br />HCS<br />Sybase<br />RDBMS<br />Visual-BASIC<br />etc.…<br />
  47. 47. …with many owners…<br />Sales<br />Pipeline<br />ERP<br />Module A<br />Call<br />Center<br />Records<br />Mgmt<br />Doc<br />Mgmt B<br />Doc<br />Mgmt A<br />Soc<br />Media<br />ERP<br />Module B<br />Data<br />Service<br />Video<br />Conf<br />Collab<br />Office Apps<br />Customer DB<br />(Oracle)<br />Product<br />Catalog<br />VOIP<br />Catalog Data<br />Exec<br />Reports<br />etc.…<br />
  48. 48. …each using a few, maybe 10s of servers.<br />
  49. 49. The enterprise doesn’t have a scale-out problem…<br />
  50. 50. The enterprise has a…<br />Integration<br />Compliance<br />Management<br />…problem.<br />
  51. 51. This means the actual requirements for cloud infrastructure don’t stop at the application.<br />
  52. 52. There’s…<br />Integration<br />Legal Requirements<br />Traffic Management<br />Troubleshooting<br />Security<br />Etc.<br />
  53. 53. For example,<br />let’s take security…<br />
  54. 54. Each solution will almost certainly be only part of the system(s) that is/are being secured.<br />
  55. 55. Security will be distributed throughout the “cloud stack”<br />
  56. 56. Security will be distributed throughout the network stack<br />
  57. 57. Security will be distributed across geographical and topological boundaries<br />
  58. 58. Security must become <br />multi-tenant<br />
  59. 59. Security must scale.<br />
  60. 60. Security must scale.<br />* Try doing that with compliance… <br />
  61. 61. Security must meet a wide variety of application needs.<br />
  62. 62. Same goes for<br />Application Management<br />
  63. 63. Same goes for<br />Performance Management<br />
  64. 64. Same goes for<br />QoS<br />
  65. 65. Same goes for<br />Load Distribution<br />
  66. 66. Same goes for<br />Etc.<br />
  67. 67. Same goes for<br />Etc., Etc.<br />
  68. 68. Same goes for<br />Etc., Etc., Etc.<br />
  69. 69. So how will the network adapt?<br />
  70. 70. Five ways:<br />
  71. 71. Data center network architectures will “flatten”.<br />
  72. 72. FabricPath<br />OTV<br />DCI<br />Open Source<br />QFabric<br />OpenFlow<br />Open vSwitch<br />
  73. 73. The network will adapt to new dominant payloads and traffic patterns.<br />
  74. 74.
  75. 75. App<br />App<br />App<br />App<br />App<br />App<br />App<br />App<br />App<br />App<br />App<br />App<br />OS<br />OS<br />OS<br />OS<br />OS<br />OS<br />OS<br />OS<br />OS<br />OS<br />OS<br />OS<br />Cloud Network Boundary<br />Virtual Data Center<br />Virtual Data Center<br />Cloud OS<br />Application Security Services<br />Application Security Services<br />Cloud OS<br />Network Services (Security, Performance, Monitoring)<br />Network Transport Virtualization (VPN)<br />Enterprise<br />Network<br />Cloud Service<br />Provider<br />Network Service<br />Provider<br />Core networks will become agile and dynamic.<br />
  76. 76.
  77. 77. The network will introduce new abstractions to simplify configuration and operation.<br />Private<br />Cloud<br />Public<br />Cloud<br />Management<br />Firewall<br />Load Balancer<br />Network Container<br />
  78. 78. Donabe<br />
  79. 79. The network and its capabilities will become services to be consumed by cloud services.<br />IaaS<br />PaaS<br />SaaS<br />API(s)<br />Network service catalog(s) and fulfillment<br />Routers, switches, services (physical and virtual), etc.<br />
  80. 80. VPC<br />
  81. 81. Thanks!<br />
  82. 82. Cloud and the Futureof Networked Systems<br />Why “big, flat and dumb” isn’t enough<br />James Urquhart<br />@jamesurquhart<br />jurquhar@cisco.com<br />
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×