User Tools

Site Tools


0x13:reports:d3t1t05-industry-perspectives

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
0x13:reports:d3t1t05-industry-perspectives [2019/04/04 09:57] ehalep0x13:reports:d3t1t05-industry-perspectives [2019/09/28 17:04] (current) – external edit 127.0.0.1
Line 1: Line 1:
-Day 3 / Track / Talk 5+Day 3 / Common Track / Talk 5
 Panel: Industry Perspectives Panel: Industry Perspectives
 Panelists:  Panelists: 
Line 12: Line 12:
 Report by: Anjali Singhai Report by: Anjali Singhai
  
-This session started with the three panelists presenting their view on how Linux networking is being used in the industry followed by questions and discussion.+This session started with the three panelists presenting their view on how Linux networking is being used in the industryfollowed by questions and discussion.
  
 The first presenter was Vikram Siwach, a product manager from MobiledgeX. The first presenter was Vikram Siwach, a product manager from MobiledgeX.
-Vikram started his talk by discussing that latency is becoming important as well as AI and machine learning followed by the current state of networks. Currently there are more than 3.7 billion devices. The network CAPEX the last ten years are around 1.7 Trillion USD ( mainly used as bit pipe). The cloud capex the last ten years is at 300 billion USD.+Vikram started his talk by discussing that not only latency is becoming important, but AI as well as machine learning following the current state of networks. Currently there are more than 3.7 billion devices. The network CAPEX the last ten years was around 1.7 Trillion USD (mainly used as bit pipe). The cloud CAPEX the last ten years is at 300 billion USD.
  
-The major issue is that a client is mobile while the cloud is static and has no notion of location of the use. Vikram proposed a new better way: CloudNet, an architecture to bring the devices closer to the cloud which features Device Native and Zero touch. The goal is to build a better cloud for these Applications: Mobile Data thinning, IOT, Mobile Gaming, New pervasive and Immersive Experiences, Drone swarming, Compliance and Privacy.+The major issue is that a client is mobile while the cloud is static and as such has no notion of location of the user. Vikram proposed a new better way: CloudNet, an architecture to bring the devices closer to the cloud which features Device Native and Zero touch. The goal is to build a better cloud for these Applications: Mobile Data thinning, IOT, Mobile Gaming, New pervasive and Immersive Experiences, Drone swarming, Compliance and Privacy.
    
-Vikram then introduced the cloudlet architecture with the Distributed Matching Engine finding the best Cloudlet. The cloudlets software stack will spawn a cluster for a particular client and validate User/Client Identity and location,+Vikram then introduced the cloudlet architecture with the Distributed Matching Engine finding the best Cloudlet. The cloudlets software stack will spawn a cluster for a particular client and validate User/Client Identity and location.
  
 Vikram made the cast to invest in Linux. Multitenancy model emerging at Edge, workload served at Real Edge can span multiple providers to provide consistent service and APIs to developers. Vikram made the cast to invest in Linux. Multitenancy model emerging at Edge, workload served at Real Edge can span multiple providers to provide consistent service and APIs to developers.
Line 33: Line 33:
 Artur continued with the fact that they own the code and that enabled them to control their own destiny with higher velocity, more granular rollouts, while having flexibility and simplicity. Artur continued with the fact that they own the code and that enabled them to control their own destiny with higher velocity, more granular rollouts, while having flexibility and simplicity.
  
-Their data Center Design is a single SKU data ceter, single chip architecture, 5 stage BGP Clos. Their design principles include simplicity works at scale, openness by using community tools when possible, independent maintaining a vendor agnostic profile, and programmability.+Their data Center Design is a single SKU data center, single chip architecture, 5 stage BGP Clos. Their design principles include simplicity works at scale, openness by using community tools when possible, independent maintaining a vendor agnostic profile, and programmability.
  
 Their hardware is a custom designed merchant Silicon, no big chassis Their hardware is a custom designed merchant Silicon, no big chassis
Line 39: Line 39:
  
 The last speaker was Marek Majkowski from Cloudflare talking about Linux at Cloudflare. The last speaker was Marek Majkowski from Cloudflare talking about Linux at Cloudflare.
-Cloudflare has two types of Data Centers, Edge & Core. Edge Networks are in 100 locations around the world and uses anycast network. The software management of edge networks are through uUniform Config, No Virtualization, no containers, raw metal, thousands of IP and multiple Applications, such as HTTP, DNS and OtherTheir moving their hardware server to ARM for less power consumption for the same amount of performance.+Cloudflare has two types of Data Centers, Edge & Core. Edge Networks are in 100 locations around the world and uses anycast network. The software management of edge networks are through Uniform Config, No Virtualization, no containers, raw metal, thousands of IP and multiple Applications, such as HTTP, DNS and othersThey’re moving their hardware server to ARM for less power consumption for the same amount of performance.
  
 The edge Network has a uniform stack and a uniform software. The edge Network has a uniform stack and a uniform software.
-Marek explained that they use XDP for classification and load balancing, protocols and workers (engineX). +Marek explained that they use XDP for classification and load balancing, protocols and workers (engineX). XDP doesn't do rate limiting right now.
-XDP doesn't do rate limiting right now.+
  
 In regards to DoS consideration in Socket Dispatch, the case of 30k UDP sockets is solved by using ebpf token bucket in SO_FILTER In regards to DoS consideration in Socket Dispatch, the case of 30k UDP sockets is solved by using ebpf token bucket in SO_FILTER
Line 69: Line 68:
 Linkedin: Challenge is collecting the data at scale at real time…to do the analytics. Where does the network start? Collect closed to the application or socket. Linkedin: Challenge is collecting the data at scale at real time…to do the analytics. Where does the network start? Collect closed to the application or socket.
  
-Site: https://www.netdevconf.org/0x13/session.html?panel-industry-perspectives +Site: https://www.netdevconf.info/0x13/session.html?panel-industry-perspectives
-Slides:  +
-Videos:  +
- +
0x13/reports/d3t1t05-industry-perspectives.1554371871.txt.gz · Last modified: 2019/09/28 17:04 (external edit)

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki