end-to-end service chains in a multi-cloud...• iot battery life (50-75% improvement with edge...
TRANSCRIPT
End-to-EndServiceChainsinaMulti-Cloud– AKeyEnablerfortheEdgeCloud–
LarryPeterson
EdgeProcessingisVital“TheEdgeWillEattheCloud”
GartnerMaverickResearchReporthttps://www.gartner.com/doc/reprints?id=1-4GH0FTL&ct=171004&st=sb
“ReturntotheEdgeandtheEndofCloudComputing”
PeterLevine,A16zhttps://a16z.com/2016/12/16/the-end-of-cloud-computing/
TheEdge… WheretheHypeIs
PublicCloud
Users
CentralOffices Telco&IXCloud
AnUntappedOpportunity
PublicCloud
Users
EdgeCloud Telco&IXCloud
AnUntappedOpportunity
PublicCloud
Users
EdgeCloud Telco&IXCloud
• Subscriberexperiencedictatedfromhere
• HumanReactiontime: 210ms• LatencytoCentralizedCloud: 100– 400ms
• EmergingApplicationsRequireEdgeProcessing• ARvisualoverlays/ImmersiveUIs• AutonomousVehicleCoordination• IoT BatteryLife(50-75%improvementwithedgeprocessing)
EdgeProcessingisVital
AnUntappedOpportunity
Lidars
Cameras
RadarSensorsUltrasonic Sensors
OdometrySensors
C-V2XConnectivity
GPSConnectivity
MiniDataCenter
AVERAGEVEHICLEUTILIZATIONINTHEUSIS4%
EACHVEHICLEWILLGENERATEAPPROXIMATELY8Gb/s
EDGECLOUDONWHEELS(On-Prem)
EDGECLOUD(CentralOffice)
Example:AutonomousVehicles
What’sDifferent?
7
Accessx Cloudà EdgePlatformwillhostmultipletypesofservices• AccessServices(e.g.,vRAN,vOLT)• ConvergedNetworkServices(e.g,.vEPC,vBNG)• EdgeCloudServices(e.g.ImmersiveUIs,Internet-of-Things)
Multi-Cloudà End-to-EndFunctionalitywillspanmultipleclouds• On-premise• CentralOffices• InternetExchanges• PublicClouds
Roleof5G
8
Earliergenerationswereaboutimprovingbroadbandtechnology
5Gisfundamentallyaboutsupportingnewservices• Internet-of-Things• ImmersiveUIs• PublicSafety
Whatuniquecapabilitydoesthemobileaccessnetworkoffer?• Low-latencyproximitytoend-users• Intrinsicsupport formobility
Challengeof5GistoSimultaneouslySupport…• LowLatency– Moving functionality totheedge,closertodevices• Mobility– Accessingthatedgefunctionalitywhilecontinuing tobemobile
MobileBroadband(2G– 4G)
9
Datacenter
Access-Edge
MoveFunctionalitytotheEdge
10
Datacenter
Access-Edge
MobileCloud(5G)
11
Datacenter
Access-Edge
MobileCloud(5G)
12
Datacenter
Access-Edge
EDGECLOUD
TELCOCLOUD
PUBLICCLOUD
OWNEDBYEDGECLOUDPROVIDER
OWNEDBYCONNECTIVITYPROVIDER
OWNEDBYPUBLICCLOUDPROVIDER
OWNEDBYOTTSERVICEPROVIDERS
Multi-TenantEdge
OneCompany(e.g.AT&T,AMAZON,CROWNCASTLE,GOOGLE)MayPlayMultipleRoles
EdgeCloudEcosystem
TelcoCloud
EDGECLOUD
EDGECLOUD
AT&TCLOUD
AWS
AT&TCORE CP
TOYOTAML
AT&TCOREUP TOYOTA
INFER
TOYOTAIOTHUB
AT&TCOREUP TESLA
INFER
TESLAIOTHUB
AUTONOMOUSDRIVING
OWNEDBYEDGECLOUDPROVIDER
OWNEDBYCONNECTIVITYPROVIDER
OWNEDBYPUBLICCLOUDPROVIDER
OWNEDBYOTTSERVICEPROVIDER
TESLAML
ServiceMeshisMulti-TenantandServiceChainsareMobile
EdgeCloudEcosystem
Factors
15
Performancedictatesthatfunctionalitybeimplementedinthemostappropriatehardware(e.g.,GPUs,SwitchingFabric).
Autonomydictatesthatdifferentstakeholderswillberesponsibleforcontrollingandmanagingdifferentcomponents.
Monetizationdictatestheneedtoofferdifferentiatedservicestodifferentclassesofsubscribers/applications.
Costdictatesadistributedsolution,withsomefunctionsrunninginthedatacentersandsomerunninginascalablenumberofedgesites.
Dynamicitydictateslocal(edge)controlwithtightcontrolloops.
RequirementsHeterogeneous– Rangeoffunctionalelementimplementations
Multi-Tenant– Multiplestakeholdersmanagingfunctionalelements
Isolation– Differentiatedresourceallocationbetweenservicechains
Dynamicity– Localcontrolloopswithminimalglobaldependencies
Distributed– Functionalelementsspanmultipleclouds
Mobility– Moveservicechainsfromoneedgecloudtoanother
16
17
Service Service
Service
Service Service
B
C
E
LegacyVNFRunningin
aVM
HorizontallyScalable
Micro-Service
SDNControlApp
PublicCloudService
…
ServiceMeshandServiceChains
ServiceAbstraction
ServiceImplementation
ServiceMesh
FunctionalElements
A D
18
Service Service
Service
Service Service
B
C
E
ServiceMeshandServiceChains
ServiceMesh
A D
VPN,MPLS,SD-WAN,…
ProviderX ProviderY
19
ServiceMeshandServiceChains
ServiceChains
Service Service
Service
Service Service
C
Subscriber 1Subscriber 2
D EBA
BaseServiceModel
20
Service
Slice
Instance
Slice
InstanceInstance
Slice
ComputeInstanceComputeInstanceComputeInstance
(Resources)
ServiceInstanceServiceInstanceServiceInstanceServiceInstance
(Control)
Service
Slice
Instance
ServiceInstanceServiceInstanceServiceInstanceServiceInstance
Slice
InstanceInstance
Slice
(Resources)
(Control)
ONOS
Ctl App
(ServiceDependency)
BaseServiceModel
21
Service
ServiceInstanceServiceInstanceServiceInstanceServiceInstance
(Distributed, Layered,CompositeandCommodityServices)
(Control)
RequirementsRevisitedHeterogeneous– Rangeoffunctionalelementimplementations• DemonstratedinCORD(VMs,Containers,SDNControlApps,PublicSaaS)
Multi-Tenant– Multiplestakeholdersmanagingfunctionalelements• DemonstratedinCORD(XOSdefinespolicylanguageforaccesscontrol)
Isolation– Differentiatedresourceallocationbetweenservicechains• DemonstratedinM-CORD(networkslicing)&R-CORD(subscriberprovisioning)
22
RequirementsRevisitedDynamicity– Localcontrolloopswithminimalglobaldependencies• DemonstratedinSEBAbyNetworkEdgeMediator(NEM)
Distributed– Functionalelementsspanmultipleclouds• Proof-of-Conceptinprogress(CORDasEdge/GoogleCloudPlatform)
Mobility– Moveservicechainsfromoneedgecloudtoanother• PaperDesign(migratecontrolstate,re-instantiatedataplane)
23