Open Networking Enables Deutsche Telekom to Sail the Cloud Native Seas.pdf

1、Open Networking Enables Deutsche Telekom Sail the Cloud Native SeasDeploymentsOpen Networking Enables Deutsche Telekom Sail the Cloud Native SeasKamran Naqvi,Principal Architect,BroadcomJens Jetzork,DevOps Engineer,Deutsche TelekomIP Fabric Broadcom Silicon based Edge-Core switchesOpen-Source Networ

2、k Operating System-SONiCBGP underlay with VXLAN EVPN based overlays to provide multi-tenancyCaters for multiple connectivity types:MCLAG Routing on the HostInter-VRF Route LeakingFlexible Management Framework facilitates Automation SpineLeafLeafLeafSpineLeafHypervisorHypervisorFRRBGP PeeringVXLAN EV

3、PN“An internal,GitOpsbased Kubernetes Cluster as a Service Platform for Network Technology(NT)Workloads almost exclusively built using open-source components.”Das SCHIFF/T-CaaS in Deutsche Telekom 150+clusters 1200+bare metal servers 6 data centers 170+OCP Accepted SONiC devices 7800+network ports 4

4、0+Apps(e.g.5GC,PCF.)Traditional Layer 2 ModelNetwork#1Network#2VLAN Kubernetes TenantCalico Full-Meshbased on BGP andIPinIP or VXLANGWVLAN/VRF combination for backbone connectivityVLAN/VXLAN for LOM and storageonlyVLAN/VXLAN for customers using SRIOV Static-Anycast-Gateway(SAG)BGP EVPN Type 2 and Ty

5、pe 5BGP unnumbered for underlay and serverBGP numbered for backboneDHCP for LOMUsed Features/ProtocolsNew Cloud VXLAN ModelNetwork#1Network#2Pod IPs per Node announced into Cluster VXLANAttaching standard hosts|Border-Leaf|Spine|Leaf|Leaf-Tbase|ServerBGPNetwork#1Network#2BGP EVPN Type 5(Cloud native

6、)Attaching SRIOV hosts|Border-Leaf|Spine|Leaf|Leaf-Tbase|ServerBGPTrunkNetwork#1Network#2BGP EVPN Type 5(SRIOV)Cross Fabric and Host communication|Border-Leaf|Spine|Leaf|Leaf-TbaseNetwork#1Network#2EVPN Type 2(MGMT)BGP EVPN Type 5(Cluster)BGP EVPN Type 2(SRIOV)|ServerNetwork OperatorNetworkOperatorL