TelcoCloudRequirements:WhatVNFsAreAskingFor

TobyFord– AT&TMarcoRodrigues– Juniper

OpenstackSummit– Telco/NFVTrackAustin,TX(April2016)

TelcoVNF(n)

Agenda

1. WhatistheTelcoCloud?2. TelcoCloudRequirementstoDate3. SolvingforVNFUniqueRequirements4. EvolvingTelcoCloudRequirements

WhatistheTelcoCloud?TheExistentialThreat:WhyshouldTelco’swantit?Introducing’TheValueStack’

Future

SMS

Physical (Copper/Fiber /Radio)

Voice

Data (Internet / IP )

SMS

Physical (Copper/Fiber/Radio)

Voice

Data(Internet/IP)

2000s– 2010s

SMS

Physical (Copper/Fiber/Radio)

Voice

1960s-2000s

Physical (Copper/Fiber/Radio)

Voice

1900s-1990s

Services/ContentSaaS

CentralizedPlatformsPaaS,IaaS,etc

SMS

Physical (Copper/Fiber /Radio)

Voice

Data (Internet / IP )

Today

Services/ContentSaaS

CentralizedPlatformsPaaS,IaaS,,etc.

DistributedTelcoCloud

ValueTheRealValue:

ValueMovingUpTheValueStackandawayfromTelco’s

OpenstackNeutron&NeutronExtensions, etc.

IP orMPLSTransports

BGPL3VPN,BGPEVPN

MPLS,VXLANServiceOverlays

1. Physical distribution providing fungible cloud resources close to Telco consumer and business eyeballs.

2. Enables applications to have:1. Low Latency2. High Availability (through

distribution)3. High volume of last mile

throughput; minimizing network wide capacity growth (choke points)

3. Seamless Integration of DC and WAN technologies leveraging existing network and operational procedures.

WhatistheTelcoCloud?HighLevelTargetArchitecture

Key Properties

~50-250

~250-1000

> 1000

Connectivity Building Blocks

WAN/METROBGP (Control Plane)

MPLS (Service)MPLS (Transport)

DC FabricBGP / OSPF (Control Plane)

IP (Transport)

+

DC OverlaysMPLS, VXLAN, IP, GRE, etc.

+

Telco Cloud

WAN METRO

METROWAN

WAN

WAN

WAN

WAN

WAN

METRO

WAN

WhatistheTelcoCloud?ExampleVNFUseCases

Use-Case FunctionalProperties(i.e.VM, ContainerandBareMetal)

Networking(L2-L7) EdgeRouting/Switching, CPE,etc.

Security Firewall, NAT, IDS/IPS,IPsec/SSLVPN,etc.

3GPP(MPC/EPC) SGW, PGW, MME, Probes, ePDG, GiLan, MMSC,etc

Voice VoLTE,SBC,etc.

CDN/Caching Databases, Storage,HaaS (BM),etc.

Access OLT,BNG,RGW’s,etc.

Video ContentManagement Transcoding,NetworkDVR,etc.

TelcoCloudRequirementstoDateWhatweknowaboutTelcoCloudVNF(s)Applications

1. Akintowebapps• MME,HSS,BackendDatabases,Application/Business

Tiers,PCRF,etc.

2. PacketForwardingandManipulation• Network&Security,EPC/MPC,etc.

3. CombinationoftraditionalNetworkingelements• SBC+Firewall+LoadBalancing+SIP

server/management

4. CDN/Proxies5. TransformationElements

• Transcoding/Encoding/Decoding/Encryption

WhatWeKnow

Multi-tenancy(ReservationandSeparation)

SelfService

ApplicationHighAvailability

GeneralQoS(IOPS,CPU,Resources)

OrchestrationInventory,Event/LogManagement,Config

Management,CI/CD/Testing,Monitoring,ITSM/ITIL/FCAPS/OSS,Probing/CALEA

BrownfieldApp/VNF Support(CattleTransition)

CommonCloudandVNFRequirements

Unique TelcoCloudVNFRequirements

LowLatency/LowJitter(i.e.Voice/Gaming/M2M/SmallPackets)

HighPacketPerSecondThroughput (i.e.DNS,NetworkI/O)

NetworkQoS(MarkingandTreatment)

MigrationofHApettomidgetcowVNFs

(i.e.BGP,HA,VRRP,etc.)

Geo-DependencyofWorkloadstoConnections

(i.e.Servicemobilityandnetworkavailability)

KPIMeasurementsofVNFRequirements

(i.e.RichNetworkAnalytics)

OperationalTransitions/Events(WorkloadandDCDryOut)

Dynamic/TieredTopology Creation,ScaleOutandServiceChaining

SolvingforUniqueRequirements1. ToSRIOVornotSRIOV2. Creatingtrulyscaleoutrouting3. BrownfieldEnablement4. CommunicatingandAligningonTelco'sUniqueness

©2016AT&T IntellectualProperty.All rights reserved.AT&T,Globe logo,Mobilizing YourWorld andDIRECTVareregistered trademarksandservicemarksofAT&T IntellectualPropertyand/or AT&Taffiliatedcompanies.All othermarksarethepropertyof their respectiveowners.AT&TProprietary (InternalUseOnly). Not foruseordisclosureoutside theAT&Tcompaniesexceptunderwritten agreement.

1.DesiredvRPacketPerformanceperServer

~75%ofVNFsmaybesatisfiedat7MPPS

2.DesiredvRFlowsperServer

~70%ofVNFsmaybesatisfiedat1.5Mflowsperserver

3.DesiredvRPeakFlowRate

~25%ofVNFsmaybesatisfiedat25Kflowspersecondperserver

0

2

4

6

8

10

12

14

16

18

20

22

24

vVM

vCP*

vNTP

vDNS vLB

vIPCI

vCDN

vUSP vCE

vNAT

vVIG vPE

PPS(m

illions)

0

0.5

1

1.5

2

2.5

3

3.5

4

4.5

5

vVM

vCP*

vNTP

vDNS vLB

vIPCI

vCDN

vUSP vCE

vNAT

vVIG vPE

DesiredFlow

sperServer(m

illions)

0

0.1

0.2

0.3

0.4

0.5

0.6

vVM

vCP*

vNTP

vDNS vLB

vIPCI

vCDN

vUSP vCE

vNAT

vVIG vPE

DesiredFlow

sRateperServer(m

illions)

FlowRate

1.6MFPS

Agg.Flows

50M

FourdimensionsofvRouterForwardperformance

• PacketProcessingAggregateFlowsPeakFlowRate

• Features

Allfoursaredimensions areimportantforVNFtomakeuseofoverlaynetworking

1234& &

SolvingforUniqueRequirementsToSRIOVornotSR-IOV(PerformanceClassification)

VNFProfile(s)VNFProfile(s) VNFProfile(s)

SolvingforUniqueRequirementsToSRIOVornotSR-IOV

ProposedSolutions1. BuildCloudNativeVNFs

• ..andifyoucan’ttherealquestionyouneedtoansweris:• ShouldIbevirtualizingvs.shouldIbeautomatingthisxNF?

2. JudicioususeofSR-IOVandtraditionalCloudworkloads• Governance:AsternremindertotenantsstillusingSR-IOV:

• Thebarrier toentryisnowremoved.• TechnicalCo-existence

3. Moore'sLaw(Hardware)totheRescue• SR-IOVworkflowintegrationintoTORs(silicon)• SmartNICoffloadofSR-IOVworkloadpropertiesintosilicon

4. SoftwaretotheRescue(optimizedlinuxkernel,drivers,vR/vS,memorymanagement,etc.)

World’sCollide

CloudNativeAppsvs.

TraditionalVFs(i.e.appliances)

SolvingforUniqueRequirementsTrulyScaledOutRouting

• Leveragethenetwork,protocolsandtoolsyoualreadyhave.• Exampleofascale-outplatform/solution:

UnderlaySwitch

vRouter

ControlNode

ControlNode

UnderlaySwitch

vRouterVM VM

IBGP

XMPP

MPLSoverGREorVXLAN

ConfigNode

Orchestrator

AnalyticsNode

SDNSystem

OpenContrail

P PPE PE

RouteReflector

RouteReflector

CECE

IBGP

IBGP

MPLSoverMPLS

NetworkManagementSystem(NMS)

DMI

MP-BGP/BGPMPLSL3VPN/EVPN

Gateway(PE)

BGP

Moredetails:http://www.opencontrail.org/opencontrail-architecture-documentation

SolvingforUniqueRequirementsBrownfieldEnablement

• PhysicalNetworkFunctions(PNFs)bynaturearelegacyandexpectcertainbehaviorsaroundit

• TraditionalPNFvendorsnotincentivizedtore-write/port• PNFowners(internalorexternal)havemovedon

• TypicaltechnologysolutionsneededforPNFtoVNFmigration:• LivelinessdetectionandHighAvailability

• PING,HTTPURI(TCP)levelchecks,BGP,BFD,etc.• DynamicInsertionofNetworkReachability

• ThinkSSL/IPSecTunnelTerminationofremoteendpoints(UE’s,SmallCellSite,etc.)• i.e.BGPaaShttps://blueprints.launchpad.net/juniperopenstack/+spec/bgp-as-a-service

• LiveMigrationofVNFssupportinglegacybehaviorsasacrutch• GeoDistributingVNFswherepossible

SolvingforUniqueRequirementsCommunicatingandAligningonTelco'sUniqueness

1. DocumentedTelcoClouduse-casesforoperationalalignment• OPNFV

2. DocumentedAPIsandDataModels• Openstack• OpenConfig• IETF• OPNFV• Others..

EvolvingTelcoCloudRequirementsLookingForward..

1. Operationalfocusofin-serviceupgradesofTelcoCloudplatformtoavoidlegacy/semi-cloudVNFdisruptions• Betterdefinedandindustryaccepteddryoutprocedures(OPNFV)

2. Moreoptionswithoutcompromisetoperformanceandscale• OpenPower,RISCv,ARM

3. Hardwareaccelerationincomputeofcommonapplicationandnetworkpatterns• NetworkI/O,Databaselookups,Encryption,Security,tonameafew.

4. DistributedPersistenceandState

References/URLs• AT&T

• Domain2Whitepaperhttps://www.att.com/Common/about_us/pdf/AT&T%20Domain%202.0%20Vision%20White%20Paper.pdf

• ECOMPhttp://about.att.com/content/dam/snrdocs/ecomp.pdf• OpenStack

• https://wiki.openstack.org/wiki/Neutron• http://docs.openstack.org/developer/networking-bgpvpn/

• OPNFV• https://www.opnfv.org

• IETF• L3VPN(RFC4364)/EVPN(RFC7432)• draft-ietf-l3vpn-end-system-05• draft-ietf-bess-service-chaining-00

• OpenConfig• https://github.com/openconfig/public

• OpenContrail• http://www.opencontrail.org/opencontrail-architecture-documentation/• https://github.com/Juniper/contrail-controller

VNF(n)