17. $-
$500
$1,000
$1,500
$2,000
$2,500
2014 2015 2016 2017 2018 2019
ADC Market Disruption
(Billions $)
The ADC Market is Changing
• Rapidly changing market place
– Shift from propriety hardware to virtualized Intel
servers + software
– Driven by private / public cloud movement
– Telco Service Providers pushing shift to
software through NFV
– Large savings in CAPEX and OPEX through
migration from hardware to virtual
• Existing hardware ADC incumbents not well
suited to new market
– Trying to protect hardware revenue while
moving to software
– Legacy software designed for ASICs must be
“translated” to run on Intel servers
– Huge code size a barrier to virtualization 17
35% vADC CAGR -3.7% HW CAGR
Source: IDC
38. 网络功能的集成测试——功能对比
方案 A方案(OpenStack原生纯开源) B方案(B厂商纯软,紧密集成) B’方案(B厂商纯软,松散集成)
分类 功能项对比
通过 Neutron 调 用 L3 和 开源 VNF
(FWaaS/VPNaaS/LBaaS)
通过Neutron调用VNF 并配置,不
使用VNF自带配置界面进行配置
不 通 Neutron 而 是 通 过 Nova 调 用
VNF 虚 拟 机 , 通 过 B 厂 商 自 带配
VNF置界面进行配置
三层路由
网关功能 √ √ √
路由功能 √ √ √
OSPF支持 x x √
PolicyBasedRouting x x √
QoS √ √ √
IGMP x x √
MLD x x √
PPP-Based Encapsulations x x √
PIM x x √
RIP x x √
RIPng x x √
Multicast Routing x x √
iBGP x x √
eBGP x x √
主备高可用 √ √[注1] √[注1]
主主高可用 x √[注1] √[注1]
防 火 墙 四
层防护
无状态防火墙 √ √ √
状态防火墙 √ √ √
双向地址转换NAT √ √ √
目标地址转换DNAT x x √
源地址转换SNAT x x √
高可用 AS x x √
高可用 AA x x √
VPN
IPSec √ √ √
Site-2-Site VPN功能 √ √ √
OpenVPN支持 x x √
Remote Access VPN x x √
高可用AS x √[注1] √[注1]
高可用 AA x √[注1] √[注1]
79. 80
可用区URL获取:
https://docs.aws.amazon.com/general/latest/gr/rande.html
Region Name Region Endpoint Protocol
US East (N. Virginia) us-east-1 ec2.us-east-1.amazonaws.com HTTPS
US West (N. California) us-west-1 ec2.us-west-1.amazonaws.com HTTPS
US West (Oregon) us-west-2 ec2.us-west-2.amazonaws.com HTTPS
Asia Pacific (Mumbai) ap-south-1 ec2.ap-south-
1.amazonaws.com
HTTPS
Asia Pacific (Seoul) ap-northeast-2 ec2.ap-northeast-
2.amazonaws.com
HTTPS
Asia Pacific (Singapore) ap-southeast-1 ec2.ap-southeast-
1.amazonaws.com
HTTPS
Asia Pacific (Sydney) ap-southeast-2 ec2.ap-southeast-
2.amazonaws.com
HTTPS
Asia Pacific (Tokyo) ap-northeast-1 ec2.ap-northeast-
1.amazonaws.com
HTTPS
EU (Frankfurt) eu-central-1 ec2.eu-central-
1.amazonaws.com
HTTPS
EU (Ireland) eu-west-1 ec2.eu-west-1.amazonaws.com HTTPS
South America (São Paulo) sa-east-1 ec2.sa-east-1.amazonaws.com HTTPS
116. Automating Across Domains Is the Solution
Cross-domain automation eliminates delays, enables business agility
125
Total Time
Delay
“90% of the total time used to complete
business tasks is classified as transfer delay
time and 10% on actual task execution.”
Workflow Management Coalition
End-to-EndWorkflow
Delay
Delay
Server
Team
Application
Team
Network
Team
Security
Team
Brocade Workflow Composer cross-
domain workflows eliminate transfer
delay and reduce workflow execution
from weeks or days to just seconds
131. NFV Orchestrator (NFVO)
140
Network Service Orchestration using a collection of VNFs
and Forwarding Graphs
Templatize an end-to-end Network Service using
decomposed VNFs
Resource Checks and Resource Allocation
VNFs connected using Forwarding Graphs
o Described in a VNF Forwarding Graph Descriptor
o Render VNF Forwarding Graphs using SDN Controller
or a SFC API
Ability to orchestrate VNFs across Multiple VIMs
PNF connectivity and configuration in end to end network
service orchestration
133. Virtual Infra Manager (VIM)
142
Responsible for controlling and managing the NFVI
compute, storage and network resources
Usually within one operator’s Infra Domain (i.e. NFVI-POP)
Exposes Northbound APIs (i.e. used by VNFM)
OpenStack is an example of a VIM
139. VNFFG API
Tacker
Compute Node 1
OVS
SDN Controller
OVSDB
Compute Node 2
OVS
...
VNF
vRouter
VNF
DPI
Templates
Neutron
(networking-sfc)
DB
Workflow:
1) Onboard NSD,
FGD, VNFD to
Catalog
2) Instantiate 2 or more
VNFs from Catalog
3) Invoke Tacker
VNFFGD API to
render the graph
VNF
FFG
D
Heat
VNFFG
Copy from
Sridhar Ramaswamy, Tacker
PTL
142. What is TOSCA NFV?
• Topology and Orchestration Specification for
Cloud Applications (TOSCA) comes from the
OASIS open standards consortium and has
been used in the applications ecosystem
since 2014
• TOSCA NFV is a data modeling and
templating language for NFV services
allowing you to define: Topology,
Composition, Lifecycle, Portability
• Is very different to Yang, Yang is good for
network device configuration not good for
above complex relationships
• Some Open Source Implementations: Senlin,
Tacker, Parser, Alien4cloud, Cloudify, Aria
TOSCA NFV Specification: http://docs.oasis-open.org/tosca/tosca-nfv/v1.0/csd02/tosca-nfv-v1.0-csd02.pdf
Source: TOSCA NFV Specification
143. TOSCA NFV templates describes the
service in vendor abstract terms
A simple p2p
circuit just uses the
WAN infrastructure
Input parameters
specify the
endpoints of the
service
152
144. TOSCA NFV is useful as it can describe
both VNF and Carrier SDN-WAN
153
145. Bringing SDN/NFV together
Open Modular architecture
allows the platform to evolve
over time (no monolithic
proprietary lock-ins)
Service API provides
a simple
programmatic
interface for all
network services
SDN WAN for
proven scalability
and reliability
Open Source projects
with broad, active
communities for
components that
enable interoperability
155
WAN PCE Application
leverages open source
ODL SDN Controller
platform
147. AT&T SDN创新 按需网络 愿景落地
按需广域网服务 Brocade vRouter
局域/领域控制器:
• NSX
• Nuage
• Contrail
• ….
Domain 2.0
The First Major Case
服务编排
云编排
策略
分析
Brocade
SDN 控制器
148. Latest Commercial Case – MANO Driven
Large Service Provider looking to provider core offload via SDN
158
Develop a software-defined network and NFV platform that:
Transports and processes non-critical traffic, such as
tap/sensor streams, for monitoring and analytics
Supports low cost network business case to migrate traffic
off the premium customer MPLS core network
Provides a national network, that is programmable and able to
insert VNF instances into network paths for traffic processing
That is developed in an agile manner, to provide the SP the
ability to adapt throughout the development process
Delivers the project to educate SP’s engineers and set-up
software practices, process and tools which can be re-used
Provides SP options for operate and transfer following build
Project Objectives
149. Modular
Clear, well defined
and open interfaces
Simplified
integration points
with existing
systems
Proven, fully
supported products
Bespoke
integration
Open Source
projects with broad,
active communities
for components that
enable
interoperability
Customer Use Case
159
150. Brocade & Partner Products & NetDev Integrations
Brocade Products:
1. Brocade SDN
Controller
2. Brocade Flow
Manager
3. Brocade VNF
Manager (Tacker)
Brocade NetDev
Integrations:
a. SP TOSCA NFV
Service Templates
(NSD)
b. SP TOSCA VNF
Definition (VNFD)
c. Service Orchestrator
Plugin – BFM
d. Service Orchestrator
Plugin – BVM (Tacker)
e. SDN Traffic
Engineering: BFM &
Brite-box
f. Service Assurance
integration with existing
NMS and remediation
into the orchestrator
160
1
2 3
1
2
3 a
b
c
d
e
c d
a
e
f
b
f
Partner Products:
1. Red Hat RHEL/OSP
2. Gigaspaces Cloudify
3. Brite-box switches
Supermicro Servers
4
5
6
7
4
7
6
5
151. Open interfaces allow components to be
interchangeable
Flow Manager interface
used to bring provision
virtual links (paths)
across the SD-WAN
Tacker interface
provisions VNFs, passes
VNF parameters and
optionally config
Heat interface used by
tacker to bring up VMs
with Openstack
TOSCA NFV based
“Service API” used to
deploy end to end
network services
Openstack used to
provision OS provider
networks for the VNF
161
152. Unique capability of solution is ability to scale
out
• Service Orchestrator integrates the end to
end network service (multiple Openstack
regions supported out of the box, can also
support Hybrid clouds)
• SDN-WAN efficiently scales out as the
network grows (supports TE in the WAN)
• Not an overlay solution
• Overlay technologies (like VXLan) across the WAN at
scale is not proven – designed for the DC
• Overlay technologies between multiple VIMs still
needs something to co-ordinate between them
• SFC Technologies like NSH still evolving, our
solution will make use of these as they
become more widely accepted and
standardised (i.e. SFC support in Tacker)
162
153. SP can take control from day-one in
creating new services with templates
• Created once per service type (i.e. p2p, p2p
with FW+LB, l2vpn, etc)
• Is simple enough to be done by Telstra,
although Brocade can provide support if
needed
• Defined using the TOSCA NFV model and
written in either YAML or JSON
• YAML is a very easy modelling language
with many tools and editors, Cloudify does
have a blueprint editor available
• Once created the service template (or
Blueprint) is loaded into the service
orchestrator where it is validated before
being added to the service catalogue
163
154. Demonstration topology
164
1a. Service Orchestration
1b. VNF Orchestration
1c. Instances
1d. Networks
of:11 of:21
of:12 of:22 of:31
31513101
3102
3103
3153
OVS
SDN Controller
BFM
City#1 POD
City#2 POD
Service Orchestrator
OS Controller
Tacker
OF:100 OF:200of:32
3152
vRouter vRouter
Openflow
Horizon
1
2
3
4
n Screens used in demonstrations
155. Sw itch Sw itch Sw itch
Edge Transit Edge
Match Match
Demo: Bi-directional Point to Point Path
Path traverses one or more switches
End-user defines match criteria and two edge switches
Path computed based on standard least-hops algorithm and programmed in switches in real-time
Back-up provided as standard, path recomputed and reprogrammed following any service impacting
topology changes
Demo: Bi-directional Point to Point Path, with Way Point(s)
Path traverses two or more switches
End-user defines match criteria, two edge switches and one or more transit switches as way points
Path computed based on least-hops algorithm between way points and programmed in real-time
Back-up provided as standard, path recomputed and reprogrammed following any service impacting
topology changes
Sw itch Sw itch Sw itch
Edge
Way Point(s)
- Transit
Edge
Match Match
Demos: End-to-end Paths
165
156. Sw itch Sw itch Sw itch
Edge Transit Edge
Match Match
C om pute
VNFDemo: Bi-directional Point to Point Path with VNF
Path traverses one or more switches
End-user defines match criteria, two edge switches and VNF details
Path computation and programming as before
VNF inputs specified by end-user: location, VM, VNF image and config
VNF defined at edge switch location Two VNF defined on different compute pods
Sw itch Sw itch Sw itch
Edge Transit Edge
Match Match
C om pute
VNF
C om pute
VNF
Demos: Paths + VNF Services
166
162. 1995
“Steve Jobs: The Lost Interview”
On the importance of software to the
computer industry from 1995 on: "There
hasn't really been a revolution in how we
created software, at least not in the last 20
years. [But] software is infiltrating
everything we do these days. Software is
going to be a major enabler in our society."
163. The Race against Machines… 和机器的赛跑… 开始了吗?
1968
1999
1984
2015
The Rise of The Machines
164.
165. 1995 Mr. Jobs on importance of computer programming to cognitive ability:
"It didn't have to do with using them for anything practical; we used it as a way to
mirror our thought process. I think everyone should learn how to program a
computer, because it teaches you how to think. I view computer science as a
liberal art, something everyone should learn to do."
166. Up the Stack, Deeper into Data, Playing with Machines…学习
• 网络作为 Data Fabric & Sensors
• 网络可视分析与大数据平台
• 网络大数据,SDN,机器学习
• 基于云平台的IT运维全局分析 & benchmark
云网交界处的数据湖