Glue con2011 future_of_net_systems
Upcoming SlideShare
Loading in...5
×
 

Glue con2011 future_of_net_systems

on

  • 1,724 views

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 ...

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

Statistics

Views

Total Views
1,724
Views on SlideShare
1,709
Embed Views
15

Actions

Likes
2
Downloads
44
Comments
0

2 Embeds 15

http://paper.li 14
https://twitter.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Glue con2011 future_of_net_systems Glue con2011 future_of_net_systems Presentation Transcript

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