Embed Size (px)
Citation preview
v
Network Automation
and Orchestration with
Carrier SDN and NFV
Caroline Chappell
Senior Analyst
Heavy Reading
Network Automation &
Orchestration With
Carrier SDN & NFV
OUR PANELISTS
www.lightreading.com
• Margaret Chiosi, Distinguished Network Architect, AT&T
• Ralph Santitoro, Director of Strategic Market Development, Fujitsu
• Nirav Modi, Director of Software Innovations, Cyan
• Manish Gulyani, VP Product Marketing, Alcatel-Lucent
• Prayson Pate, Chief Technologist, Overture Networks
AGENDA
• Operationalizing SDN and NFV: abstracting,
automating, and orchestrating the network
• Panel Discussion
• Q&A
www.lightreading.com
SDN vs NFV N
FV
Function/
location
separation
Reduced power
usage (elastic
scalability)
Initial focus on
atomic network
functions, but
topology focus
coming
SD
N
Control/
data plane
separation
Focus on network
function
connectivity
(logical topologies)
COTS hardware
Vendor-independence
Rapid service innovation
Improved operational efficiency
Standardized, open interfaces
Dynamic chaining of network functions
Centralized orchestration and management
Consistent policy framework
Network Automation & Orchestration
With Carrier SDN & NFV
Ralph Santitoro Director of Strategic Market Development
October 2, 2013
Current OSS Landscape OSS Problem Statement
OSS’s have limited or no technology abstraction Technology abstraction simplifies multi-vendor, multi-layer,
multi-technology management
Difficult and time consuming to innovate Cost prohibitive to experiment with new types of services or
customization of existing services
Provisioned Networks Limited Programmability and Service Elasticity
Managed Network Functions Limited Automation
(c) Copyright 2013 Fujitsu Network Communications, Inc. All Rights Reserved. NFV and SDN Management Orchestration 6
Our cloud-centric world requires automation and elasticity Carrier’s OSSs must evolve to support this new reality
SDN Management Orchestration Model
In the Southbound direction (SDNC NE/EMS) Abstracts networking technology/protocol details from NetOS/SDN Controller
Provides vendor-independent programmability of network elements
In the Northbound direction (SDNC Apps) Provides network/service programmability (APIs) by software applications
Abstracts networking technology details from the applications
Northbound APIs (network/service abstraction)
Network OS/SDN Controller
Southbound APIs (technology abstraction)
Network Element
Network Element
EMS
Apps Apps Apps
Web 2.0 RESTful APIs using, e.g.,
JSON representations, for Apps to
program networks and services
Software adapters for NetOS/SDNC
to NE/EMS protocol translation Network Element
Apps
OpenFlow TL1 SNMP XML
NFV and SDN Management Orchestration (c) Copyright 2013 Fujitsu Network Communications, Inc. All Rights Reserved. 7
Network Function Virtualization Infrastructure (NFVI)
NFV Management Orchestration Model ETSI NFV ISG (Work in Progress)
Physical Resources
Compute Storage Network
Virtualization Layer (Hypervisor)
Virtual Resources
vCompute vStorage vNetwork
VNF VNF VNF VNF
Virtual Machines (VMs)
Virtual Network Functions
VNF and NFVI
Management
and
Orchestration
NFV and SDN Management Orchestration (c) Copyright 2013 Fujitsu Network Communications, Inc. All Rights Reserved. 8
OSS / BSS
NFV Management & Orchestration following Cloud Computing Model
NFV
Virtualization (Hypervisor)
VM
vCompute vStorage vNetwork
SDN
Control
Layer Network Services
Next Generation OSSs require Orchestration of
Cloud Computing, SDN and NFV Management
NFV and SDN Management Orchestration
VNF
VM
VNF
VM
VNF
VM
Application
Layer Business
Applications
Network Service
Network Service Network
Service
Infrastructure
Layer
OpenFlow TL1 SNMP
Technology Abstraction
RESTful APIs
Network/Service Abstraction
(c) Copyright 2013 Fujitsu Network Communications, Inc. All Rights Reserved. 9
VNF Management
and Orchestration
© 2013, CYAN, INC. 10 10 © 2013, CYAN, INC. © 2013, CYAN, INC.
Cyan Solutions
© 2013, CYAN, INC. 11 11 © 2013, CYAN, INC.
Reinventing the OSS
Network and DC are converging into a singular resource pool
Elasticity previously only available in DCs is migrating to the networking space
Current OSSs not architected to deploy SDN technologies and NFV orchestration
Carrier-grade service requirements still need to be met
Service agility, service innovation as well as transformation of cost and operational models are drivers for change
Existing systems not flexible, service introduction can take months
© 2013, CYAN, INC. 12 12 © 2013, CYAN, INC.
Network & Cloud Convergence Black, White and mostly Grey?
Data Center Residential
Enterprise
Wholesale Enterprise
Wireless
Provider A
Provider B
Legend: - Network functions as specialized physical NEs
- Generic switch as physical NE
- Virtual network functions
- Data Center providing NFV Infrastructure services
Majority of economically compelling NFs virtualized Larger freedom of (re-)location Consolidations
© 2013, CYAN, INC. 13 13 © 2013, CYAN, INC.
The OSS Needs New Clothes
Network Orchestration Cloud
Orchestration
APIs APIs
NFV Orchestration
Controller
Access Metro Core
Service Orchestration
VNF Services
Controller
Cloud Services Multi-Layer, Multi-Vendor NaaS
Controller
© 2013, CYAN, INC. 14 14 © 2013, CYAN, INC.
Enabling SDN and NFV
NMS/EMS
BSS/OSS BSS/OSS
NMS/EMS
CMS
CMS CMS
CMS CMS
SDN/NFV Platform
SDN/NFV Platform
NFV Infrastructure
APIs APIs
© 2013, CYAN, INC. 15 15 © 2013, CYAN, INC.
Multi-Domain SDN/NFV Orchestration
NETWORK AUTOMATION & ORCHESTRATION WITH CARRIER SDN & NFV
Manish Gulyani
September 2013
18
MOBILE
CORE
IPTV
RNC/BSC
IMS
SDM
OSS/BSS
ENTERPRISE
SERVICES
CDN
EPC
IPTV
IMS
CDN
OSS/BSS
ENTERPRISE
SERVICES
EPC
RNC/BSC
NETWORK WANTS TO EMBRACE CLOUD
FROM CONVENTIONAL INFRASTRUCTURE … … TO A SOFTWARE DEFINED ENVIRONMENT
RAPID PROGRAMMABILITY
FULL AUTOMATION
IMPROVED EFFICIENCY
19
YOU NEED MORE THAN VIRTUALIZATION
LEAN: AGILE & COST EFFECTIVE FIT WITH SLAS AS REQUIRED
REAL TIME
99.9 to 99.999%
SECURITY
UNRESTRICTED NETWORKING
REGULATORY COMPLIANCE
ECOSYSTEM
20
CLOUD ORCHESTRATION & NETWORK AUTOMATION REQUIREMENTS TO CLOUDIFY THE NETWORK
app RAPID ONBOARDING
& AUTOMATED LIFECYCLE
MANAGEMENT
E2E ASSURANCE
& ANALYTICS
VIRTUAL & NON-VIRTUAL
BARE METAL & CONVENTIONAL SYSTEMS
DYNAMIC CAPACITY
MANAGEMENT AT SCALE
UNCONSTRAINED CONNECTIONS
RESPECTING APPLICATION SECURITY & QoS
21
Open, distributed cloud
infrastructure
Cloud services & capabilities
Cloud intelligence & control
Cloud orchestration & automation
Virtual private clouds
Enterprise private clouds
Hybrid clouds
Public clouds
Network virtualization & automation
Customers
IT services (PaaS, IaaS)
NFV applications Application
services (SaaS)
MUST FIT INTO AN OPEN CLOUD ENVIRONMENT
DEPLOY APPLICATIONS ON TOP OF ANY CLOUD H/W, OS OR NETWORK
22
Cloud Mgr &
Orchestrator
PUTTING IT IN ACTION ADDING SIGNALING CAPACITY TO A VIRTUAL EPC
Scenario
After introduction of a set of small cells, the signaling traffic load is much greater than expected
Native OS (Optional)
Hypervisor
Generic x86 Hardware
Virtual Operating Environment
vMME recipe
vMME
Virtual Routing & Switching 4
5
1
2
3 SDN
Controller
Network Services
Policy
EPC Mgmt System
23
UNDERTAKING THE JOURNEY
EARLY
VIRTUALIZATION
CLOUD DC
DEPLOYMENT
LIFECYCLE
AUTOMATION FULL CLOUD OPERATION
MATU
RIT
Y L
EVEL
IMPLEMENTATION
OVERTURENETWORKS.COM
Carrier Class Orchestration for SDN & NFV Prayson Pate Chief Technologist Overture Networks
Carrier Orchestration is Different!
Traditional orchestration (e.g. AWS CloudFormation) is focused on the data center.
26 Carrier Class Orchestration for SDN & NFV
Carrier SDN and NFV will be used to build carrier services across the network; orchestration must reflect additional requirements.
Resource Acquisition, Assignment & Span
• In a data center, resources are all equivalent.
• In an NFV network location matters
• Span extends beyond data center to MEN and WAN
27 Carrier Class Orchestration for SDN & NFV
Customer Site
Central Office Mini-Datacenter
Metro Datacenter
Metro Network
All the same These resources are scarce, but lower latency
Not just in here
But also here
Lifecycle and Work Flow
• Critical to tie into higher-level systems
• Could be OSS/BSS systems
• Could be network applications
• Programmable and transactional behavior on service activation
• Reliability and status monitoring
28 Carrier Class Orchestration for SDN & NFV
Service Elasticity and Orchestrator Scalability
• Services built using NFV must have VNF components that are elastic / horizontally scalable
• Can’t be simple conversions of software to run on a server instead of an appliance
29 Carrier Class Orchestration for SDN & NFV
Orchestrator Multi-Tenancy
• Wikipedia: “Multi-tenancy refers to a principle in software architecture where a single instance of the software runs on a server, serving multiple client-organizations (tenants)”
• Different from “virtualization where components are abstracted enabling each customer application to appear to run on a separate physical machine.”
• Orchestrator multi-tenancy simplifies system design and integration into higher level systems.
30 Carrier Class Orchestration for SDN & NFV
Summary of Carrier Class Orchestration
Aspect Data Center Carrier Class
Resource Acquisition and Assignment
All resources are equivalent
Location, latency and bandwidth matter
Span of Control Within data center Across metro area
Lifecycle and Work Flow
Controlled directly by user
Tied into higher level systems
Service Assurance and Resilience
Coarse status monitoring
Transactional behavior and fine status monitoring
Elasticity, Scalability and Multi-tenancy
Current resources are elastic
VNFs must be elastic and orchestrator multi-tenant
31 Carrier Class Orchestration for SDN & NFV
QUESTION 1
What do we mean by orchestration?
Service orchestration? Resource cloud
orchestration? Controller orchestration?
www.lightreading.com
QUESTION 2
What happens to legacy OSS? What is the
migration path to SDN/NFV management
approaches?
www.lightreading.com
QUESTION 3
What are the largest barriers to
operationalizing SDN and NFV?
www.lightreading.com
QUESTION 4
Can SDN and NFV be introduced into
legacy networks or should they support new
services in a greenfield way?
www.lightreading.com
QUESTION 5
How much of the network can a single
vendor realistically orchestrate? What are
the specific standards needed here?
www.lightreading.com
QUESTION 6
How far should NFV management and
orchestration follow the IT cloud
management paradigm?
www.lightreading.com
QUESTION 7
What are the benefits of SDN/NFV network
automation and orchestration?
www.lightreading.com
Q&A
www.lightreading.com
