使用“KubeEdgeBus”处理边缘云网络

1 .Handle Edge Cloud Network with KubeBus Yulin Sun, yulin.sun@huawei.com Seattle Cloud Lab, Huawei R&D USA, Bellevue WA 

2 .Agenda • Edge sample user scenarios • Edge network characteristics • Related work for edge • KubeBus target user scenario • KubeBus architecture • Summary 

3 .User Sample Scenarios Huawei Hilens Campus HiLens surveillance 

4 .Edge network characteristics • Edge Nodes running at private network • Connect to Cloud behind NAT gateway • Mightn’t have direct connection between Edges • Edge Nodes connect to Cloud with Internet • Low bandwidth • High latency 

5 .Related Work --Edge/Cloud collaboration Some of services are moved from Cloud to Edge • Sample Scenarios • IOT • Edge: Data local filter/aggregation • Cloud: Global aggregation • AI • Cloud: Model training, face recognition IOT Device Cloud • Edge: Face detect IOT Device Edge Cloud Intelligent Edge + Intelligent Cloud Can the Cloud services running MQTT at Edge without change? MQTT Broker Communication Protocol Edge Node Cloud Services Device Cloud MQTT Edge Service IOT Device Edge to Cloud Protocol Device Edge MQTT • IOT Protocol : e.g. MQTT MQTT MQTT Broker Or • Cloud Protocol: e.g. Http Edge Cloud MQTT or Http? Cloud IOT Device Edge 

6 .KubeBus target user scenario Edge Node Management Edge/Cloud Cluster Management • Edge Node Management • Small numbers Edge nodes needs to be managed from Cloud, such as HiLens, • Services running in Edge nodes needs Service Publishing to Internet • Services running at Edge nodes needs little orchestration • Edge nodes count per tenants is so small so needs multi-tenant management/data plane to save cost • Edge/Cloud Cluster Management • There is cloud cluster, edge cluster, i.e. multiple nodes running in private network • Edge nodes, Edge cluster and cloud cluster needs acting as a single cluster 

7 .KubeBus Architecture --Edge Node Management Http Client Cloud Cluster (Internet) Http Client (Cloud Cluster) Http WebService • KubeBus Protocol Stack • L2/L3/L4 over TCP KubeBus@Cloud KubeBus Client KubeBus Server • KubeBus Client/Server Proxy to proxy Http Proxy Proxy packets KubeBus Tansport L4 • Multiplex https connections over TCP connection, i.e. “L7 tunnel” KubeBus Network L3 KubeBus Data Link L2 • Multitenant service publishing TCP Server Socket • Global namespace URL definition Edge Node • Host Name Http Client Http WebService • Edge Node Http client access: Localhost • Internet access Http client access: EIP KubeBus ... Edge Node Edge Node KubeBus Client Proxy KubeBus Server Proxy • Sample scenario KubeBus Tansport L4 Tcp Connecction • Edge remote login: Shellinabox KubeBus Network L3 • Edge file remote access: Http File Server KubeBus Data Link L2 • Edge video streaming: Http video server TCP Client Socket 

8 .KubeBus Architecture --Edge/Cloud Cluster Cloud Cluster VM VM VM Container Network, e.g. Flannel 10.244.0.0/16 KubeBus ... Virtual Router Edge Network IP: 192.168.6.4 EIP: 35.160.180.205 192.168.23.129 192.168.23.130 VM IP: 192.168.23.131 • L3 tunnel • over KubeBus L3/L2 KubeBus KubeBus Edge Network: 192.168.6.2 Edge Network: 192.168.6.3 • Build edge nodes subnet Container Network 10.243.0.0/16 Container Network 10.242.0.0/16 ... • Virtual Cluster Network • Edge nodes subnet: 192.168.6.0/24 EdgeNode EdgeNode • VM subnet: 192.168.23.0/24 Container • Container subnets: 10.244.0.0/16, 10.243.0.0/16, 10.242.0.0/16 

9 .Summary • Edge network characters (Vs data center network) • Topology: Edge nodes running behind NAT • Performance: Connect to Cloud through Internet • Low throughput • High latency • Edge Scenario: • Some services moved from Cloud to Edge • Can cloud services be deployed to and run at Edge without change • KubeBus • Link Edge node/Edge cluster/Cloud cluster as single cluster with VPN • Support multitenant management/data plane for tenants with few edge nodes 

10 .