Transcript SDN e NFV: Novas Oportunidades em Redes de

MANAGEMENT OF SDNAND NFV-BASED
COMPUTER NETWORKS
Lisandro Zambenedetti Granville
[email protected]
Institute of Informatics
Federal University of Rio Grande do Sul
Outline
• Introduction: the Internet ossification
• Network virtualization
• Software-Defined Networking (SDN)
• Management of SDN
• Network Functions Virtualizaton (NFV)
• NFV management
• Examples of management systems
Introduction
• Innvation in the past:
• 1982: DNS insted of hosts.txt
• 1983: NCP to TCP/IP (400 devices)
• 1990s: Border Gateway Protocol (BGP)
• 1993: Classless Inter-Domain Routing (CIDR)
Introduction (cont.)
• Innovation strugling:
• IP Multicast (RFC #1112 1989)
• Quality of Service (QoS)
• Integrated Services (IntServ) (RFC #1633 1994)
• Differentiated Services (DiffServ) (RFC #2475 1998)
• IPv6 (RFC #2460 1998)
• Explicit Congestion Notification (ECN) - (RFC #1633 2001)
• Mobile IP (RFC #3220 2002)
Introduction (cont.)
• Where’s the innovation?
• Peer-to-peer file sharing
• Napster
• Voice over IP
• Skype
• Social Networks
• Facebook, Twitter
• Video services
• YouTube, NetFlix
Introduction (cont.)
• Structural changes were possible in the early
days of the Internet
• Still, the core technology (TCP/IP) remains
untouched for over two decades
• The Internet ossification refers to the inability of
innovating on the core of the network
Network Virtualization
• Virtual machines have been around for awhile:
• CPU virtualization
• Storage virtualization
• Memory virtualization
• Virtualization on networks:
• Link virtualization
• Router virtualization
• Service virtualization
Network Virtualization (cont.)
Service
provider 2
Virtualized
network 2
Recursion
Service
provider 1
Virtualized
network 1
Infrastructure
provider 1
Infrastructure
provider 2
Network Virtualization (cont.)
• Benefits:
• “Isolated” and realistic environment for network experimentation
• Enables de development of new stacks, protocols, and addressing
schemas
• In the end, it enables the development of new network
architectures
Network Virtualization (cont.)
• Project
• GENI (Global Environment for Network Innovations)
• FIRE (Future Internet Research Experimentation)
• FIBRE (Future Internet Testbeds Experimentation Between Brazil
and Europe)
Software-Defined Networking (SDN)
• Network industry mimicking the old mainframe paradigm
Routing, management, mobility, access
control, VPNs, etc.
Function
Function
OS
Proprietary hardware
Millions of
source code
lines
Billions
of devices
6,000 RFCs
SDN (cont.)
• Design versus reality
• Few vendors delivering low innovation
• Proprietary architecture leads to closed interfaces
App
App
App
App
App
App
Operating System
Operating System
Hardware
Hardware
SDN (cont.)
• How the PC industry solved the problem?
AppAppAppAppAppAppAppAppAppAppApp
Specialized
applications
Closed
Operating
System
Proprietary
hardware
Closed interfaces,
small industry, and
slow innovation
Open Interfaces
Windows
(OS)
Linux
Open interface
Microprocessor
Open interfaces,
huge industry,
fast innovation
Mac
OS
SDN (cont.)
• SDN shares the same principle
AppAppAppAppAppAppAppAppAppAppApp
Specialized
functions
Specialized
control plane
Open interfaces
Control
plane
Control
plane
Control
plane
Open interface
Proprietary
hardware
Close, proprietary,
slow innovation
Off the shelf
switching chips
Open interfaces,
fast innovation
SDN (cont.)
Function
Function
Network Operating System
Function
Function
SO
Function
Function
Hardware
OS
Function
Function
Hardware
SO
Function
Hardware
Function
SO
Function
Function
SO
Hardware
Hardware
SDN (cont.)
• OpenFlow
Centralized control
Controller
OpenFlow
Switch
Distributed control
Controller
OpenFlow
Switch
Controller
OpenFlow
Switch
OpenFlow
Switch
OpenFlow
Switch
Controller
OpenFlow
Switch
SDN (cont.)
• OpenFlow and network virtualization
App
App
Windows
Windows
Windows
(OS)
(OS)
(SO)
App
Linux
Linux
Linux
Computer industry
App
App
Mac
Mac
Mac
OS
OS
SO
Virtualization layer
X86
App
Controller
Controller
NOX
11de Rede)
(SO
Controller
Controller
SO
22 de Rede
Virtualization layer
OpenFlow
Network industry
SDN (cont.)
• Slicing
OpenFlow Controller
Default
OpenFlow Controller
New routing protocol
OpenFlow Controller
New mobility mgmt.
SDN management
• SDN is often refereed to as a management technology
• It can help tackle classical network management
problems
• Network discovery
• Event correlation
• However, as a new networking technology, it poses new
management problems as well
• Unfortunately, management is often an afterthoght
SDN management (cont.)
2008
OpenFlow at
ACM SIGCOMM [2]
2008
OpenFlow
Specification 1.0
2010
Lyatiss
2009
Vello
2009
Pica8
2009
2008
2010
Big Switch
2010
NEC IP8800 switch
NOX at
ACM SIGCOMM [3]
2011
Open Networking
2012
2010
Foundation 2012
HP FlexNetwork
Google announces
VMWare
Architecture
the adoption of SDN
acquires Nicira
2012
2011
SIGCOMM
HotSDN
Juniper JunosV
Workshop
Midokura
2011
2012
Plexxi
Pluribus
PLUMgrid
OFELIA Project
2013
Contrail
Open Networking
Summit
IRTF SDNRG
Cisco ONE
Pertino
2014
CNSM ManSDN
Workshop
Start-ups
Market Activity
Academia
Standardization
Cisco ACI
2014
Open Daylight
2015
SDN & OpenFlow
World Congress
Juliano Araujo Wickboldt, Wanderson Paim de Jesus, Pedro Heleno Isolani,
Cristiano Bonato Both, Juergen Rochol, Lisandro Zambenedetti Granville.
Software-Defined Networking: Management Requirements and
Challenges. IEEE Communications Magazine: Network and service
management series, January (2015), ISSN 0163-6804.
SDN management (cont.)
• Lack of a proper management plane at the SDN design
phase
• Classical clash between control versus management
• Control
• Short loops
• Fast reaction
• Minimal human intervention
• Known events
• Management
• Larger loops
• Slow reaction
• Based on human perception of the network status
• Unknown events
...
Management
Interface
SDN management (cont.)
...
Management
Interface
NorthBound API
Functional
Physical
...
Management
Interface
SouthBound API
Management
Plane
SDN management (cont.)
• Management requirements
• Bootstrap and configuration
• Because of plane separation, management actions must be in place to
configure network devices to properly bootstrap the communication
between forwarding and control planes
• Availability and resilience
• With a logically centralized controller, the network can become
unavailable more easily. Management must consider the resilience of
the SDN infrastructure in the light of the controller element, its copies,
and their placement
SDN management (cont.)
• Management requirements (cont.)
• Network programmability
• Including control versioning, coordinated deployment, and verification of
network software in an environment where innovation is more intense,
but software updates are also more frequent.
• Performance and scalability
• Management must take into account to peculiarities of SDN to tweak the
network and tune performance and scalability
SDN management (cont.)
• Management requirements (cont.)
• Isolation and security
• With much more virtual network in place, management must ensure
isolation between different traffic. It must also handle security threads
from malicious software developed for SDN environments.
• Flexibility
• With new software being deployed much more easily, management
must be sufficiently flexible and expandable to accommodate the
management of new functions that are gradually incorporated into the
network
SDN management (cont.)
• Management requirements (cont.)
• Network planning
• With new software constantly deployed on the network, network
planning must consider not only forwarding devices, but the influence
new software has over the SDN environment
• Monitoring and visualization
• Monitoring must be designed for the new SDN environment, and
visualization must reflect both physical and virtual network components
SDN management (cont.)
• Research challenges
• From high-level rules to network configuration
• Policy-based network management in SDN
• Autonomic and in-network management
• Management components inside SDN devices
• Flexible management through interfaces
• Are current network management interfaces sufficient?
• Smart network planning
• Wizards to help the administrator plan network expansions
• Situational management
• How to react to short lived situations in an affordable way?
Network Functions Virtualization (NFV)
• Hardware-based network appliances (middleboxes) are
now an intrinsic and fundamental part of today’s Internet
• Essential to network operators, supporting diverse set of
functions (e.g., NAT, traffic shaping, security)
NFV (cont.)
• Middleboxes come with a number of drawbacks
• Expensive to buy and manage
• Cannot be easily scaled up and
down with shifting demand
• Not flexible to include new
features (unless buying and
deploying new hardware)
NFV (cont.)
• How about virtualizing middleboxes?
• Network Function Virtualization has been proposed in
2012 by ETSI to shift middlebox processing from
hardware appliances to software running on
commodity hardware
• By virtualizing and consolidating network functions,
network operators expect to achieve
• Lower cost of equipment and savings on energy
• Improved scalability of network functions
• Fully remote deployment of appliances
• Spatial functions migration with no or very short service interruption
• More open market for virtual appliances than today
NFV (cont.)
Source: ETSI 2013
NFV (cont.)
• NFV versus SDN
• NFV is not dependent on SDN concepts or OpenFlow
• It is possible to implement a virtualized network function (VNF) as a
standalone entity using existing networking and orchestration
mechanisms
• However, there are inherent benefits in leveraging SDN concepts to
implement and manage an NFV infrastructure, namely in
orchestration of VNFs
NFV (cont.)
• Function chaining example
Set of chains of service function
(Applications, Services, flows)
A
NF-1
NF-2
Set of network functions
NF-1 (NAT)
B
NF-2 (Firewall)
NF-4a
A
NF-2
NF-5
NF-4 (Cache)
C
NF-5 (LB)
NF-4b
B
A
C
D
NFV Infrastructure (NFVI)
NFV (cont.)
• Function chaining example (cont.)
NFV Infrastructure (NFVI)
B
A
NF-5
NF-2
NF-4a
NF-1
NF-4b
Set of network service chain
(Applications, Services, flows)
A
NF-1
NF-2
D
B
NF-4a
A
NF-2
NF-5
C
NF-4b
C
NFV management
• Different than SDN, management aspects have been core
to the NFV general architecture
• Management versus orchestration
NFV management (cont.)
• Management requirements
• VNF server configuration
• Each virtualization platform has to be properly configured
• VMs instantiation
• Virtual machines need to be instantiated to host VNF
• Infrastructure deployment and VNF location
• Communications between VNFs need to establish, as well as their
location along the physical servers
• VNF deployment
• What is the method to used to deploy VNFs?
• VNF monitoring and VNFI visualization
• How to retrieve the status of VNFs and visualize the whole
infrastructure?
• Physical and virtual NFs coexistence
• How to manage the structure switching between different view?
NFV management (cont.)
• Because NFV can be taken as a specialized cloud
instance, cloud management solutions can inspire NFV
management
• Interesting possible overlapping of areas: computer
networks and cloud computing
Virtualization Monitoring
Márcio Carvalho, Lisandro Zambenedetti Granville. Incorporating Virtualization
Awareness in Service Monitoring Systems. IEEE/IFIP IM 2011, Dublin
Virtualization Monitoring
Virtualization Management
Fábio Daitx, Rafael Esteves, Lisandro Zambenedetti Granville. On the use of SNMP as a
Management Interface for Virtual Networks. IFIP/IEEE IM 2011, 23-27 May 2011, Dublin
Virtualization Management
24
Cumulative average delay (seconds)
21
18
15
12
VMware
Xen
9
6
3
0
1
2
3
4
5
6
Active VRs
7
8
9
10
Virtualization Management
40
35
CPU utilization (%)
30
25
20
VMware
Xen
15
10
5
0
0
6 12 18 24 30 36 42 48 54 60 66 72 78 84 90 96 102 108 114 120 126 132 138 144 150 156 162 168
Time (seconds)
Virtualization Management
4500
4000
3000
2500
VMware
2000
Xen
1500
1000
500
0
0
6
12
18
24
30
36
42
48
54
60
66
72
78
84
90
96
102
108
114
120
126
132
138
144
150
156
162
168
Used memory (MB)
3500
Time (seconds)
Mashups for Network Management
Carlos Raniery Paula dos Santos, Rafael Santos Bezerra, João Marcelo Ceron, Lisandro
Zambenedetti Granville, Liane Margarida Rockenbach Tarouco. On Using Mashups for
Composing Network Management Applications. IEEE Commag, V. 48, December 2010
Management Visualizations
Paulo Teles Barbosa, Lisandro Zambenedetti Granville. Interactive SNMP Traffic
Analysis Through Information Visualization. IEEE/IFIP NOMS 2010 mini-conference
Dynamic Circuits
José Jair Cardoso de Santanna, Juliano Araujo Wickboldt, Lisandro Zambenedetti
Granville. A BPM-Based Solution for Inter-domain Circuit Management. IEEE/IFIP
NOMS 2012, Hawaii
Visualization of SDN
Pedro Heleno Isolani, Juliano Wickboldt, Cristiano Both, Juergen Rochol, Lisandro
Zambenedetti Granville. Interactive Monitoring, Visualization and Configuration of
OpenFlow-based SDN. IFIP/IEEE 11-15 May 2015, Ottawa, Canada
QoS policies for SDN
Cristian Machado, Juliano Wickboldt, Lisandro Zambenedetti Granville, Alberto SchaefferFilho. Policy Authoring for Software-Defined Networking Management. IFIP/IEEE IM
2015, , Ottawa, Canada
MANAGEMENT OF SDNAND NFV-BASED
COMPUTER NETWORKS
Thanks for your attention!
Question?
Lisandro Zambenedetti Granville
[email protected]