the network behind the clouds
DESCRIPTION
Luc Ceuppens, The Vice President, Product Marketing of the Infrastructure Product Group of Juniper Networks presented Juniper's New Network vision in the Carrier Ethernet World APAC on Dec 01, 2010.TRANSCRIPT
THE NETWORK BEHIND THE CLOUDS
Luc Ceuppens
Vice President, Product MarketingInfrastructure Product Group
2 Copyright © 2010 Juniper Networks, Inc. www.juniper.net
AGENDA
Historical precedents
Cloud computing: business and deployment models
Cloud networking: definition and properties
“Connecting” cloud computing and networking
Conclusion
3 Copyright © 2010 Juniper Networks, Inc. www.juniper.net
Image Copyright Andrew Bossi. This work is licensed under the Creative Commons Attribution-Share Alike 2.0 Generic License.
4 Copyright © 2010 Juniper Networks, Inc. www.juniper.net
“Freeway Gridlock” – Image Copyright: Fihliwe. This work is licensed under the Creative Commons Attribution-Share Alike 2.0 Generic License.
5 Copyright © 2010 Juniper Networks, Inc. www.juniper.net
Photo by Gregory Maxwell, converted to rectilinear projection and missing areas filled in by Ilmari Karonen. [GFDL-1.2], from Wikimedia Commons
6 Copyright © 2010 Juniper Networks, Inc. www.juniper.net
7 Copyright © 2010 Juniper Networks, Inc. www.juniper.net
Simplified
Automated
Secure
The New Network
8 Copyright © 2010 Juniper Networks, Inc. www.juniper.net
INNOVATION AT EVERY NETWORK LAYER
Mega Data Centers
Mega POPs
Devices
Data Centers
Campus
Branch
Devices
Service ProvidersEnterprise
Aggregation/Access
Universal Edge
9 Copyright © 2010 Juniper Networks, Inc. www.juniper.net
“Dawn over morning cloud, New Zealand” – By Danial – Creative Commons license
10 Copyright © 2010 Juniper Networks, Inc. www.juniper.net
DEFINITION OF CLOUD COMPUTING
(Network-based) access to a pool of data center resources
(servers, storage, applications, inter-connect, firewalls, …)
Key characteristics
lease, not own
economies of scale
location independent
on-demand, reconfigurable, elastic
Service models are based on how cloud resources are offered
Deployment modes are based on who uses the cloud
The type of network access plays a big role
11 Copyright © 2010 Juniper Networks, Inc. www.juniper.net
Offer software/application built on topUse our
cloud-based software
SERVICE MODELS
Offer resources as a platform Write your own software
Offer raw compute resourcesBuild your
own DC
Layer of Infrastructure Offered Service
12 Copyright © 2010 Juniper Networks, Inc. www.juniper.net
DEPLOYMENT MODELS
Private cloud
owned or leased by an enterprise
private access
Community cloud
shared infrastructure for community (e.g., set of enterprises)
access limited to community
Public cloud
mega-scale infrastructure for public use
public access
Hybrid cloud
composition of two or more types of clouds
13 Copyright © 2010 Juniper Networks, Inc. www.juniper.net
CLOUD SERVICES CHALLENGES
Q: Rate the challenges/issues of the „cloud”/on-demand model
(sale: 1 = Not at all concerned 5= Very Concerned)
Source: IDC Enterprise Panel, 3Q09, n = 263
70% 72% 74% 76% 78% 80% 82% 84% 86% 88% 90%
Not enough ability to customize
Hard to integrate with in-house IT
Bringing back in-house may be difficult
Lack of interoperability standards
On-demand paym't model may cost more
Performance
Availability
SecurityAttributes requiring
a „Cloud Networking‟
approach
14 Copyright © 2010 Juniper Networks, Inc. www.juniper.net
PROPERTIES OF CLOUDS
All the resources of cloud computing have several properties
that are crucial to the success of this paradigm
Fungibility
Elasticity
Reconfigurability
(Resource) Mobility
Virtualizability
These same properties are required of cloud networking!
15 Copyright © 2010 Juniper Networks, Inc. www.juniper.net
FUNGIBILITY
Build computing infrastructure
with the fewest pools of
independent resources
IaaS: pick a standard CPU,
emulate others as needed
Storage: offer block access,
via FCoE/iSCSI; filesystems
PaaS: different platforms,
languages, SDKs
SaaS: straightforward
Single physical resource?
Build the network infrastructure
with the fewest pools of
independent resources
Interconnect: Ethernet, FCoE
L2: Ethernet, VLANs, MACs
L3: IP, IP addresses
L4-L7: virtualized firewalls,
load balancers, DPI engines
Single physical resource?
16 Copyright © 2010 Juniper Networks, Inc. www.juniper.net
ELASTICITY
Compute resources allocated
on demand (scheduled),
resized dynamically (real-time)
CPU cycles
RAM
Storage
Limits and time bounds may
be placed up front
Metered use
Network resources allocated
on demand (scheduled),
resized dynamically (real-time)
Bandwidth
IP/MAC addresses
Auxiliary services (DPI, fw)
Again, limits and time bounds
may be needed
Metered use
17 Copyright © 2010 Juniper Networks, Inc. www.juniper.net
RECONFIGURABILITY, MOBILITY
Reconfiguration and mobility of the underlying resources are
alike and have similar constraints
Reconfiguring or moving compute resources MUST be done in
tandem with reconfiguring or moving network resources
Moves in particular require that the network be aware that the
customer application may be in two places for a short duration,
and has to assist the transition with routing, switching and other
services
While clever algorithms allow reconfiguration and moves to be
“in service” and reduce the impact on customer applications,
there may be a need to pause the apps for a short duration
18 Copyright © 2010 Juniper Networks, Inc. www.juniper.net
VIRTUALIZABILITY
Virtualizing physical compute
resources allows the cloud
provider to manage them more
easily, to treat them as
fungible entities and to
reconfigure and move them
Virtualization also allows the
cloud provider a greater
degree of control over the use
of resources
Network resources have to be
virtualized to connect related
compute entities, as well as to
connect the user to the cloud
The former is often Layer 2;
the latter is Layer 3; the two
must also interconnect
securely and seamlessly
Network virtualization must
also support reconfiguration
and moves as seamless as
possible
19 Copyright © 2010 Juniper Networks, Inc. www.juniper.net
SLAs AND CHARGING MODELS
On the compute front, this
includes CPU time, RAM
usage, storage space (and this
is often persistent)
SLAs may also cover
elasticity, reconfigurability and
mobility: how responsive to
bursts, recovery time,
interruption
Charging varies by resource,
but is typically metered, with
extra for elastic growth
On the networking front, this
includes bandwidth within and
out of the data center and L4-
L7 services. These are
typically networking SLAs
There may need to be tighter
SLAs around elasticity, VM
motion and storage
Charging models for network
will probably need rethinking
20 Copyright © 2010 Juniper Networks, Inc. www.juniper.net
“CONNECTING” COMPUTING AND NETWORK
In all of the above properties of clouds, there is an interaction
between what happens on the compute front and on the
networking front
In reconfiguration and moves, this is even stronger
Matching up compute virtualization, network virtualization within
the data center (L2) and between the customer and the data
center (L3) is crucial to correct operation as well as to security
BTW, security will make or break cloud computing!
21 Copyright © 2010 Juniper Networks, Inc. www.juniper.net
CONCLUSION
The current focus on “Clouds” centers on cloud computing,
service and deployment models (and rightly so)
However, the networking piece (“cloud networking”) is an equal
partner, and thus needs equal focus
Most of the properties of clouds apply on both fronts, and
although they may manifest themselves in somewhat different
ways, one must consider them together
Fortunately, most of the issues are not new for networks, they just
need to be integrated
Cloud security and privacy is crucial, and again must be
considered jointly on the compute and networking fronts