1. Cloud and the Futureof Networked Systems
Why big, flat and dumb isnt enough
James Urquhart
CNET | The Wisdom of Clouds
Program Manager, OpenStack@Cisco

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