Automating Business Process via MuleSoft Composer | Bangalore MuleSoft Meetup...
From SDN to Cloud Networking
1. FROM SDN TO CLOUD NETWORKING
EXECUTIVE VICE PRESIDENT, SOFTWARE SOLUTIONS DIVISION
Bob Muglia
2. TODAY’S REALITY
Instability & Constant Change
of CEOs feel confident in
their ability to plan for growth
10%
Source: Gartner, Inc., “CEO and Senior Executive Survey 2013: The Opportunity Now Is to Drive EA From Business Priorities” March 2013
4. BARRIER TO FULL CLOUD ADOPTION
CAN I VIRTUALIZE MY…
Compute NetworkStorage
5. 7 MYTHS OF SDN
Truth:
It will fuel
hardware
innovation
Truth:
Considerable
intelligence
stays
decentralized
Truth:
OpenFlow is
just a protocol
and probably
not the most
important one
for SDN
Truth:
It will happen
step-by-step
Truth:
We will begin
to see the
impact in 2013
Truth:
It applies to
all networking
and networking
services
Truth:
Opex
reduction
is more
significant
Truth:
It will fuel
hardware
innovation
Truth:
Considerable
intelligence
stays
decentralized
Truth:
OpenFlow is
just a protocol
and probably
not the most
important one
for SDN
Truth:
It will happen
step-by-step
Truth:
We will begin
to see the
impact in 2013
Truth:
It applies to
all networking
and networking
services
Truth:
Opex
reduction
is more
significant
Myth:
It’s only
about software
Myth:
It’s only about
centralization
Myth:
It’s only
about
OpenFlow
Myth:
It’s going
to happen
immediately
Myth:
It’s only about
datacenter
networking
Myth:
It’s only about
reducing
CAPEX
Myth:
It’s going to
take forever
7 MYTHS OF SDN
Google: “7 Truths of SDN”
7. 8th
SDN is a forklift upgrade
myth
Truth:
SDN will work with your existing network
8. INITIAL APPROACH TO SDN
Separates the data plane from the control plane
Completely centralizes the control plane
First packet of every flow is punted to the controller - reactive
Uniform flat network
Very large forwarding table in switches
Tenant changes affects all switches in path
Replaces existing network and protocols
REACTIVE END-TO-END NETWORK
9. REACTIVE END-TO-END NETWORKS
First packet of every flow
is punted to controller
Controller reactively programs every flow
on every switch on path
Per-tenant state in physical network:
Switches contain many flows
High latency. Low scalability. Fragile. Fork-lift upgrade.
10. A TWO DIMENSIONAL SPECTRUM
REACTIVE
PROACTIVE
END-TO-END OVERLAY
Reactive
End-to-End
Aggregated
Flows in
Core
Proactive Flow
Installation
Proactive
Overlay
11. A BETTER APPROACH TO SDN
Underlay physical network provides industry standard L2 & L3 forwarding
Tenant state only at the network edge – server hypervisors & gateways
Controller proactively installs forwarding state
Much smaller forwarding table in switches
Tenant changes don’t affect physical network
Incremental evolution of existing network and protocols
PROACTIVE OVERLAY NETWORK
12. PROACTIVE OVERLAY NETWORKS
Packets are not
punted to controller
Existing protocols establish
IP fabric underlay
No per-tenant state in physical network:
Switches only know physical servers
Low latency. High scalability. Robust. Evolutionary.
Controller proactively programs virtual
overlay switches & gateways only
13. WHAT ABOUT OPENFLOW?
OpenFlow is a control protocol
OpenFlow 1.3 was initially used for Reactive End-to-End networks
Very low level – i.e. programming hardware TCAM entries
Not ideally suited to establish high-level, proactive overlays
That said, OpenFlow can be used for all SDN approaches:
Reactive End-to-End, Aggregated Flows in Core, Proactive Flow
Installation, & Proactive Overlay
Alternative control protocols better suited to the Proactive Overlay model
XMPP or OVS-DB
14. WANT MORE DETAIL?
Blog by Bruno Rijsman – Juniper SDN Architect
Part One:
http://forums.juniper.net/t5/The-New-Network/Applying-the-Goldilocks-
principle-to-SDN/ba-p/190245
Part Two:
http://forums.juniper.net/t5/The-New-Network/Myth-8-Software-Defined-
Networking-requires-a-forklift-upgrade/ba-p/190255
Whitepaper by Bruno Rijsman – Juniper SDN Architect
http://www.juniper.net/us/en/local/pdf/whitepapers/2000515-en.pdf
END-TO-END VS. OVERLAY
15. SDN Controller
Configuration Analytics
Control
Virtualized Server
VM VM VM
Virtualized Server
VM VM VMIP fabric
(underlay network)
Horizontally
scalable
Highly available
Federated
SDN CONTROLLER
Control
Orchestrator
OVERLAY ARCHITECTURE
16. JUNOS-V CONTRAIL CONTROLLER
SDN Controller
Configuration Analytics
Control
Virtualized Server
VM VM VM
Virtualized Server
VM VM VMIP fabric
(underlay network)
Juniper Qfabric/QFX/EX
or 3rd party underlay switches
Juniper MX
or 3rd party gateway routers
Tenant VMs
Horizontally
scalable
Highly available
Federated JunosV Contrail Controller
KVM Hypervisor +
JunosV Contrail (L2 & L3)
SDN CONTROLLER
Control
Orchestrator
17. JUNOS-V CONTRAIL CONTROLLER
SDN Controller
Configuration Analytics
Control
Virtualized Server
VM VM VM
Virtualized Server
VM VM VMIP fabric
(underlay network)
Juniper Qfabric/QFX/EX
or 3rd party underlay switches
Juniper MX
or 3rd party gateway routers
Tenant VMs
BGP
Federation
Horizontally
scalable
Highly available
Federated
BGP
Clustering
JunosV Contrail Controller
KVM Hypervisor +
JunosV Contrail (L2 & L3)
REST
XMPP
SDN CONTROLLER
Control
Orchestrator
XMPP BGP + Netconf
18. JUNOSV CONTRAIL SERVICE CHAINING
SDN Controller
Configuration Analytics
Control
Virtualized Server
VM VM VM
Virtualized Server
VM VM VMIP fabric
(underlay network)
REST
SDN CONTROLLER
Control
Orchestrator
Virtualized Server
Virtual Service
Virtualized Server
Virtual Service
XMPPXMPP XMPP
Overlay establishes a serial, “chain”
through multiple virtualized services
19. STANDARDS
Overlay control plane protocols:
XMPP: RFC 6120, draft-marques-l3vpn-end-system
BGP L3VPN: RFC 4364
BGP EVPN: draft-ietf-l2vpn-evpn
NetConf: RFC 6241
Multicast: draft-marques-l3vpn-mcast-edge
Overlay data plane encapsulation:
MPLS over GRE: RFC 4797
VXLAN (encapsulation only): draft-mahalingam-dutt-dcops-vxlan
Underlay control plane protocols:
Existing layer-2 or layer-3 protocols
Overall architecture
IETF NVO3 WG
ETSI NFV ISG
20. Centralize ControllerCentralize Management
1 LICENSING MODEL
JUNIPER SOFTWARE ADVANTAGE
Full Use/Elastic Transferable
Software
Lifetime Assurance
Standard ProtocolsCentralizeSeparate
Networking Planes
Use the cloud Common Platform Apply Broadly
Across Domains
6 PRINCIPLES
4 STEP ROADMAP
Extract Services Optimize the Hardware
JUNIPER’S SDN STRATEGY: 6-4-1
21. Centralize ControllerCentralize Management
1 LICENSING MODEL
JUNIPER SOFTWARE ADVANTAGE
Full Use/Elastic Transferable
Software
Lifetime Assurance
Standard ProtocolsCentralizeSeparate
Networking Planes
Use the cloud Common Platform Apply Broadly
Across Domains
6 PRINCIPLES
4 STEP ROADMAP
Extract Services Optimize the Hardware
JUNIPER’S SDN STRATEGY: 6-4-1
Centralize Management
22. Centralize ControllerCentralize Management
1 LICENSING MODEL
JUNIPER SOFTWARE ADVANTAGE
Full Use/Elastic Transferable
Software
Lifetime Assurance
Standard ProtocolsCentralizeSeparate
Networking Planes
Use the cloud Common Platform Apply Broadly
Across Domains
6 PRINCIPLES
4 STEP ROADMAP
Extract Services Optimize the Hardware
JUNIPER’S SDN STRATEGY: 6-4-1
Extract Services
23. Centralize ControllerCentralize Management
1 LICENSING MODEL
JUNIPER SOFTWARE ADVANTAGE
Full Use/Elastic Transferable
Software
Lifetime Assurance
Standard ProtocolsCentralizeSeparate
Networking Planes
Use the cloud Common Platform Apply Broadly
Across Domains
6 PRINCIPLES
4 STEP ROADMAP
Extract Services Optimize the Hardware
JUNIPER’S SDN STRATEGY: 6-4-1
Centralize Controller
How can you Proactively plan for change … before there is a need to change?CEO’s are more uncertain than ever about future of market conditions, they crave the ability to make their overall business more agile in responding to market conditions. CIO’s align to CEO priority with cloud infrastructures initiatives to unleash agility in IT resources. The network is blocking the CIO’s cloud vision today because of its manual nature. The primary protocol for configuring the network is still a human interface called the “work ticket.” SDN makes cloud networks possible.
Network has hindered full cloud/virtualization adoption because… Network services are bound to physical network hardware and topologyBogged down with an old model designed for manual provisioning on a device-by-device basisHundreds of individual network devices tied together with no programmatic interface for network-wide controlProblem this is causing…“Thanks to virtualization, a new server can be fired up in a matter of hours, but the networking aspect still takes two weeks.” – Computer Weekly“Application access/delivery is dependent on underlying network which will need to become more dynamic/flexible with SDN” - IDCToday,complex manual reconfiguration of network hardware is needed to extend the network in cloud environments. While provisioning a VM may take only 2 min, provisioning the associated network and networking services can add days or even weeks to the process. Furthermore, cloud computing benefits from applications’ ability to move all around a datacenter (or even across datacenters). However, physical network topology limits workload mobility within the scope of a top-of-the-rack switch and a handful of servers. While compute and storage can be quickly provisioned – the network is the last thing we can't currently rapidly deploy.
Centralize management extract services that were formerly on network devices but would now run on a common platform as virtual machines, leverage a centralized controller enabling a new broad range of network capabilitiessimplify the network device.