VNF Meets the Cloud - RNP · 2017-09-26 · Benefits of NFV (Examples) Reduced equipment costs and...
Transcript of VNF Meets the Cloud - RNP · 2017-09-26 · Benefits of NFV (Examples) Reduced equipment costs and...
1
Matti Hiltunen, Ph.D.
Principal Inventive ScientistCloud Technologies and Services ResearchAT&T Labs – ResearchBedminster, NJ, USA
May 31 2016
© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
VNF Meets the Cloud
Challenges and Solutions
Outline
AT&T: NFV and SDN
NFV Approach
NFV Challenges
Some solutions
CloudQoS Project at AT&T Labs - Research
Valet Holistic Placement Service
Looking forward
Conclusions2 © 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.3
AT&T: NFV and SDN
AT&T Software Defined Networking
AT&T Puts SDN/NFV in Driver's SeatAT&T shows how serious it is about SDN, NFV and open source
AT&T will launch SDN service in 63 countries simultaneously this year, de la Vega says ONOS and AT&T Team Up to Deliver CORD
AT&T Reveals Audacious SDN Plans
AT&T accelerates SDN vision by extending network on demand capability to 100 cities AT&T Shares ECOMP Vision, Might Share Software
AT&T reveals details of ECOMP SDN platform
0
2
4
6
8
10
12
14
16
2010 2011 2012 2013 2014 2015
© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.4
data
voice
Why: Mobile vs. Data Growth
Time
Traffic
2007 2008 2009 2010 2011 2012 2013 2014
© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.5
in data traffic on AT&T national wireless network
100,000% increase
Jan. 2007 – Dec. 2014
Why: Customer Demand
Mobile Video Traffic
6
More than 2Xin 2014
Additional Growth Drivers
© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
2010 2011 2012 2013 2014
More than 1300%
Ethernet Ports
© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.7
The Vision
Faster
HighlySecure
MoreFlexible
MoreReliable
Easier to Scale
Cheaper Agile
SpecializedHardware
FlexibleSoftware
Solution
8
Network Function Virtualization Software Defined Networking
Physical functions become virtual functions
Applications evolve fast
Greater reuse & distribution
Elastic
Intelligent – autonomous & automated
Reliable & secure – greater extensibility & control
Accelerates innovation – lower entry barrier, faster cycles
Programmable
Open
ModularScalable
Agile
Cloud
Infrastructure
© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
Shift: Adopt the Speed and Scale of the Web Platform Industry
9
Web-scale Companies
Bottom-up
Physically-based
Custom
Top-down
Virtualization-based
Commodity
Network Service Providers
Application Resiliency & Performance
Infrastructure Reliability & Scale
Hardware
© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
NFV APPROACH
10 © 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
Network Virtualization Approach
• Fragmented non-commodity hardware.• Physical install per appliance per site• Hardware development large barrier to entry for new vendors, constraining innovation
and competition
BRAS
Firewall
CDNMessageRouter
CarrierGrade NAT
Session BorderController
PE RouterSGSN/GGSNHigh volume standard processors (servers)
High volume standard storage
Network Function Software
Orchestrated, automatic, and remote install
European Telecommunications Standards Institute (ETSI) NFV Industry Specification Group (ISG), NFV White Paper (WP), Sept. 2014.
© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
NFV Use Cases
12
From ETSI NFV ISG WPU© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
Benefits of NFV (Examples)
Reduced equipment costs and power consumption through consolidation.
Improved operational efficiency thanks to higher uniformity of the physical platform.
Tailored services and connectivity for multiple users and applications on the same hardware.
Targeted, very fast service introduction based on geography or customer sets.
Services can be rapidly scaled up/down as required.
Enabling a wide variety of eco-systems and encouraging openness.
13 From ETSI NFV ISG WP© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
Architectural Framework
14 From ETSI NFV ISG WPU© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
NFV CHALLENGES
15 © 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
Challenges
1. Virtualization
VNF Provider:
Commodity hardware and OS
Reliability
Virtualization overhead
Performance
Cloud
Infrastructure
© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
2. “Cloudification”
VNF Provider:
Unpredictability
Reliability
Security
Elasticity required
Cloud Provider:
Multi tenancy
QoS: Reliability, Performance, Security, ..
Dealing with scale
High utilization
Quality of Service (QoS)
A wide variety of non-functional requirements (e.g. throughout, latency, reliability, availability, security) that affect the quality of a service
17
Compute/Memory Storage Network
© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
Requirements
18
ETSI
ETSI GS NFV 004 V1.1.1 (2013-10) 3
Contents
Intellectual Property Rights ................................................................................................................................ 4
Foreword ...................................................................................................................... ....................................... 4
1 Scope ....................................................................................................................... ................................. 5
2 References .................................................................................................................. .............................. 52.1 Normative references ...................................................................................................... ................................... 5
2.2 Informative references .................................................................................................... .................................... 5
3 Definitions and abbreviations ............................................................................................... .................... 63.1 Definitions ............................................................................................................... ........................................... 6
3.2 Abbreviations ............................................................................................................. ........................................ 6
4 General Description ......................................................................................................... ......................... 64.1 Introduction .............................................................................................................. .......................................... 6
4.2 Objectives ................................................................................................................ ........................................... 6
5 High level requirements ..................................................................................................... ...................... 75.1 General ................................................................................................................... ............................................ 7
5.2 Portability ............................................................................................................... ............................................ 7
5.3 Performance ............................................................................................................... ........................................ 8
5.4 Elasticity ................................................................................................................ ............................................. 8
5.5 Resiliency ................................................................................................................ ........................................... 8
5.6 Security .................................................................................................................. ............................................ 9
5.7 Service Continuity ........................................................................................................ .................................... 10
5.8 Service Assurance ......................................................................................................... ................................... 11
5.9 Operational and Management requirements ................................................................................... .................. 11
5.10 Energy Efficiency requirements .......................................................................................... ............................. 12
5.11 Coexistence with existing networks - Transition........................................................................... ................... 13
6 Service Models .............................................................................................................. ......................... 146.1 General ................................................................................................................... .......................................... 14
6.2 Deployment models ......................................................................................................... ................................. 14
6.3 Service models ............................................................................................................ ..................................... 14
6.4 Maintenance models ........................................................................................................ ................................. 15
Annex A (informative): Authors & contributors ................................................................................. 16
History ....................................................................................................................... ....................................... 17
© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
Requirements
19
ETSI
ETSI GS NFV 004 V1.1.1 (2013-10) 3
Contents
Intellectual Property Rights ................................................................................................................................ 4
Foreword ...................................................................................................................... ....................................... 4
1 Scope ....................................................................................................................... ................................. 5
2 References .................................................................................................................. .............................. 52.1 Normative references ...................................................................................................... ................................... 5
2.2 Informative references .................................................................................................... .................................... 5
3 Definitions and abbreviations ............................................................................................... .................... 63.1 Definitions ............................................................................................................... ........................................... 6
3.2 Abbreviations ............................................................................................................. ........................................ 6
4 General Description ......................................................................................................... ......................... 64.1 Introduction .............................................................................................................. .......................................... 6
4.2 Objectives ................................................................................................................ ........................................... 6
5 High level requirements ..................................................................................................... ...................... 75.1 General ................................................................................................................... ............................................ 7
5.2 Portability ............................................................................................................... ............................................ 7
5.3 Performance ............................................................................................................... ........................................ 8
5.4 Elasticity ................................................................................................................ ............................................. 8
5.5 Resiliency ................................................................................................................ ........................................... 8
5.6 Security .................................................................................................................. ............................................ 9
5.7 Service Continuity ........................................................................................................ .................................... 10
5.8 Service Assurance ......................................................................................................... ................................... 11
5.9 Operational and Management requirements ................................................................................... .................. 11
5.10 Energy Efficiency requirements .......................................................................................... ............................. 12
5.11 Coexistence with existing networks - Transition........................................................................... ................... 13
6 Service Models .............................................................................................................. ......................... 146.1 General ................................................................................................................... .......................................... 14
6.2 Deployment models ......................................................................................................... ................................. 14
6.3 Service models ............................................................................................................ ..................................... 14
6.4 Maintenance models ........................................................................................................ ................................. 15
Annex A (informative): Authors & contributors ................................................................................. 16
History ....................................................................................................................... ....................................... 17
© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
Requirements (Examples)
[Per.1] The NFV framework shall be able to instantiate and configure any given VNF over the underlying infrastructure so that the behavior…in terms of performance is conforming to the requirementsexpressed in the VNF information model….
….
[OaM.14] The NFV framework shall be able to manage the assignment of NFVI resources to a VNF in a way that resources (compute hardware, storage, network) can be shared between VNFs.
20
From ETSI NFV ISG WPU
© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
Low
Bandw
idth
Sm
all
VM
Volu
me
Div
ersi
ty z
one
Lar
ge
VM H
igh B
andw
idth
Scale of VNF clouds
21 © 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
Scale of VNF clouds
22 © 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
Cell sites
Central offices
Customer premises
SOME SOLUTIONS
23 © 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
Tools
24
1. Virtualization
Containers, DPDK, SR-IOV
VM Replication, state replication
Failure detection
Leader election, consensus
Cloud
Infrastructure
© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
2. “Cloudification”
Decoupling state from VNF replicas
Auto-scaling
Auto-repair
Auto-diagnosis
…
Cloud QoS
Automation
Scalable data collection
Scalable orchestration
Optimization
Cloud QoS Project (at AT&T Labs – Research)
Vision
• QoS plus all the advantages of a multi-tenant cloud infrastructure
Architecture
• Compute, network, storage (OpenStack++, SDN, Software-Defined Storage)
Techniques
• QoS specification
• Network control (Open vSwitch - rate limiting, packet classification)
• Hypervisor level controls (e.g., cgroups, interrupt steering)
• Admission control
• Optimization
• Holistic placement of application resources in OpenStack
25 © 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
VALET
HOLISTIC PLACEMENT AND OPTIMIZATION SERVICE FOR OPENSTACK
26 © 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
Reminder: VNFs have complex requirements
VM1
VM2VM1
VM1
VM1 must have 4 vCPUs, 2 GiB of memory. Must have assured access to the vCPUs (no overbooking).Must run on a trusted host. Must support 10K packets-per-second, 1 MbpsRequire SR-IOV or DPDK. …
10 Mbps
VOL 1
VOL 1 VOL 1 must be 100 GB, high performance (SSD), 1000 IOPS, 0.999 available, 0.9999 reliable, …
HSS-FEHSS-FE
VM1
VMs 1, 2, and 3 must be in different racks (or hosts). Or on exclusive hosts (security).
VMs VM1 and VM2 require a guaranteed network link of 10 Mbps.
500 IOPS VM1 requires 500 IOPS connection to VOL1.
© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
AT&T Proprietary (Internal Use Only) Not for use or disclosure outside the AT&T companies except under written agreement 28
28
Low Bandwidth
Small VM Volume Diversity zoneLarge VM
High Bandwidth
ToR
Switch1
Host1-1
Disk1-1
ToR
Switch2
Host2-1
Disk2-1
ToR
Switch3
Host3-1
Disk3-1
ToR
Switch4
Host4-1
Disk4-1
……
ToR
Switch(m-1)
Host(m-1)-1
Disk(m-1)-1
ToR
Switchm
Hostm-1
Diskm-1
Pod Switch1 Pod Switch2
Root
iSCSI
Storage
Data center 2
Data center 3Data center 1
Placement
Valet’s Mission
CONTEXT
Valet implemented as an extension to OpenStack.
Start with a historical perspective on OpenStack with focus on resource placement.
© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
30
First there was Nova
OpenStack’s Compute Service – allows the creation and management of virtual machines.
# nova boot --image imageID --flavor flavorID --nic net-id=nicID
A number of constraints on on which host the VM can be and should be deployed:
• Must have enough memory, CPU, local disk, ..
• Host must have special capabilities such as SSD, trusted, 1:1 CPU over-subscription ratio,..
• Must be on the same host/different host as some other VM, …
• ….
Nova
© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
31
Nova scheduler filters
Each filter implements one scheduling constraint check.
A host that passes all filters is a candidate for VM placement.
More filters in each OpenStack release (34 in Kilo).
Nova
RamFilter
CoreFilter
AvailabilityZoneFilter
SameHostFilter
. . .
© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
32
Cloud apps keep on getting more complicated
May consist of 10s of VMs and volumes.
VMs have dependencies, e.g., the software in one VM needs to know the IP address of another VM.
Creating an application one VM at a time becomes a tedious and error prone process.
© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
33
Then came Heat
OpenStack’s Orchestration Service – allows the creation and management of stacks, where each stack is described by a Heat template.
Heat template: specifies the cloud resources (VMs, volumes, networks, ports, etc), software configuration, even autoscaling of the application.
#heat stack-create my_first_stack –template_file=my_template.yaml
A complete application can be deployed, configured, and started with one command!
Heat
© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
34
Cloud applications have requirements
Each VM/volume has its own requirements but the application often has requirements across a set of VMs/volumes.
- A group of VMs replicating a service should be placed on different racks.
- Two VMs should be placed so that a 1 Gbpsbandwidth can be guaranteed between them.
- VM and volume should be placed so that 1000 IOPS can be guaranteed.
- …
© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
35
We have a problem ….
Nova and Cinder schedule each VM/volume independently without considering how they relate to other VMs/volumes in the same application.
- Makes it hard for applications to express and satisfy their constraints.
- Satisfying application constraints may require support from the cloud Ops (e.g., create a host aggregate, availability zone).
- Expensive, error prone, brittle, and leads into resource fragmentation.
- Poor application performance, inefficient use of cloud resources.
© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
36
SOLUTION: Valet Placement Service
Valet is a holistic placement service for cloud resources within a data center.
It hides the underlying details of the hardware layer, and allows the application/VNF/service to express placement requirements at an abstract level.
Valet maintains a detailed, up to date view of the data center’s resources, and uses powerful constraint solving and optimization methods to satisfy all application requirements while attaining the best use of capital.
© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
37
Impact of Valet
Without Valet With Valet
© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
SPECIFICATION OF APPLICATION PROPERTIES
Let’s extend Heat …
© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
39
Application specification
Standard OpenStack: Specify VM flavor, volume size, possibly volume QoS, limited affinity/anti-affinity, availability zones.
Valet provides new Heat resource types. For example:
• ATT::Valet::Pipe (VM to VM bandwidth reservation)
• ATT::Valet::GroupAssignment (exclusivity, diversity and affinity groups)
© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
40
Specifying bandwidth requirements
Application may require an end-to-end bandwidth guarantee between VMs.
Valet pick’s hosts with enough bandwidth between them.
MS_CS1_Bandwidth_Reservation:
type: ATT::Valet::Pipe
properties:
bandwidth: 5.0
resources:
- {get_resource: MetaServer}
- {get_resource: ChunkServer}
© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
41
Specifying affinity
Application may want VMs/volumes to be close to one another.
mon1-affinity:
type: ATT::Valet::GroupAssignment
properties:
group_type: affinity
level: host
resources:
- { get_resource: mon1-ceph }
- { get_resource: vol-mon1-ceph }
© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
42
Specifying diversity
Application may want VMs/volumes to be spread across multiple hosts, racks, (or even sites).
monitor-diversity:
type: ATT::Valet::GroupAssignment
properties:
group_type: diversity
level: rack
resources:
- { get_resource: mon1-affinity }
- { get_resource: mon2-affinity }
- { get_resource: mon3-affinity }
© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
43
Specifying exclusivity
Application, or group of applications, may require exclusive placement for security reasons.
my_exclusive_group:
type: ATT::Valet::GroupAssignment
properties:
group_name: Core_Infrastructure_VNFs
group_type: exclusivity
level: host
resources:
- { get_resource: <first_VM> }
- { get_resource: <second_VM> }
© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
How Valet operates in three simple steps
Well, one of them is pretty hard … actually NP-Hard.
© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
45
Valet bootstrap
Heat (Kilo or later)
CinderNova …
Valet NovaScheduler
Filter
Valet
Oslo Message Bus
When Valet starts up it gets information from Nova (and other OpenStack services)
Resource Plugins
Valet HeatLifecycle Plugin
Existing OpenStack
Valet component
© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
46
Valet placement planning
Heat (Kilo or later)
CinderNova …
Valet NovaScheduler
Filter
Oslo Message Bus
Tenant invokes Heat with template. Lifecycle plugin passes info to Valet.
Valet’s constraint-solving optimization algorithm finds a placement that satisfies all requirements while optimizing the resource usage of the OpenStack site.
Valet remembers the decision locally.
Resource Plugins
Valet HeatLifecycle Plugin
Existing OpenStack
Valet component
Extended Heat
Template
Valet
© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
47
VM placement and creation
Heat (Kilo or later)
CinderNova …
Valet NovaScheduler
Filter
Oslo Message Bus
Heat calls Nova to create a VM. Valet Nova scheduler filter queries Valet for the stored decision; resources are placed according to the decision.
Resource Plugins
Valet HeatLifecycle Plugin
Existing OpenStack
Valet component
Valet
© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
48
Valet and OpenStack
Valet is compatible with OpenStack Kilo. It does not require any changes in the code of existing OpenStackservices.
Valet is in the process of being released as AT&T Open Source projects.
Valet was presented to the OpenStack community for the first time at the OpenStack Summit in April 2016.
© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
AT&T Proprietary (Internal Use Only) Not for use or disclosure outside the AT&T companies except under written agreement 49
49
Low Bandwidth
Small VM Volume Diversity zoneLarge VM
High Bandwidth
ToR
Switch1
Host1-1
Disk1-1
ToR
Switch2
Host2-1
Disk2-1
ToR
Switch3
Host3-1
Disk3-1
ToR
Switch4
Host4-1
Disk4-1
……
ToR
Switch(m-1)
Host(m-1)-1
Disk(m-1)-1
ToR
Switchm
Hostm-1
Diskm-1
Pod Switch1 Pod Switch2
Root
iSCSI
Storage
Data center 2
Data center 3Data center 1
Placement
Valet Summary
LOOKING FORWARD
50 © 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
VNFs in massively distributed clouds
51
Specification of service requirements
(proximity, latency, affinity, diversity, ..)
© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
Service owner Cloud provider
Optimization of resource usage.
Scalable data collection and optimization.
Service Chaining in massively distributed clouds
52
VNF management
© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
Traffic engineering
Latency
Resource costs
License costs
IoT and cloud computing
53 © 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
CONCLUSIONS
54 © 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
Conclusions
VNFs, SDN, and cloud computing are key enabling technologies for telco services TODAY.
Many business opportunities and benefits, but also numerous challenges for the research community.
QoS in a multi-tenant cloud.
Scale of the massively distributed NFV cloud.
Cloud-aware VNFs.
AT&T Labs – Research is addressing many of the challenges.
Emphasis on using/extending open source software (OpenStack, Zookeeper, Cassandra, Ceph, etc) and contributing back to the open source community.
55 © 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.56
Questions?
© 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.57
Thank You