analysis of network traffic. These growth and flexibility requirements are driving the telecommunications companies to consider a new architecture for the CO . Figure 4 Transition to Cloudified Architecture in the CO – Figure 4 shows how the CO is transforming from traditional, proprietary, dedicated hardware functions to a CO that relies upon industry standard servers, virtualization and industry standard Ethernet switches. Operators are learning from IT vendors to build clusters of virtualized servers, which can be provisioned as needed to address adaptive demand. The virtual servers are running software-based telecommunication functions and must still meet the same low latency, high performance and high availability requirements of their traditional dedicated hardware brethren. The cloudified central office is challenged to meet these objectives when the network fabric improperly addresses congestion and packet loss. Parallelism One attribute that all of the use cases have in common is parallelism. In order for largescale cloud services to meet real-time interactive latency requirements, the applications and storage must divide and conquer. There is simply too much data to process, and the true value of data is how quickly it can be rendered into human consumable information and action. As Figure 5 suggests, parallelism in a distributed system depends upon an enormous amount of messaging for synchronization and parameter distribution. Inherent in this messaging are traffic patterns that create congestion due to incast and disorderly flows. Left unattended, congestion leads to overall loss in the network: packet loss, latency loss and throughput loss. These network issues exacerbate application issues and result in bad user experiences. Successful data centers of the future must minimize these issues. Figure 5 The Problem with Network Congestion – Why Today’s Data Centers Aren’t Keeping Up Whether building a public cloud or a private data center that operates as an internal cloud service for enterprises, a common set of problems need to be addressed. Network designers need to build a highly flexible fabric for rapidly changing environments that carry a diverse set of traffic: application, storage and control. ommon goal to minimize or eliminate packet loss, provide high throughput and maintain low latency. These goals are especially important to support the applications of OLDI, Deep Learning, NVMe over Fabrics and the Cloudified CO. Today’s data centers typically use fat-tree architectures derived from the basic Clos network illustrated in Figure 6. The Clos network achieves non-blocking performance and resiliency through equal cost multi-paths. Layer 3 networking is typically used between the switches
analysis of network traffic. These growth and flexibility requirements are driving the telecommunications companies to consider a new architecture for the CO . Figure 4 – Transition to Cloudified Architecture in the CO Figure 4 shows how the CO is transforming from traditional, proprietary, dedicated hardware functions to a CO that relies upon industry standard servers, virtualization and industry standard Ethernet switches. Operators are learning from IT vendors to build clusters of virtualized servers, which can be provisioned as needed to address adaptive demand. The virtual servers are running software-based telecommunication functions and must still meet the same low latency, high performance and high availability requirements of their traditional dedicated hardware brethren. The cloudified central office is challenged to meet these objectives when the network fabric improperly addresses congestion and packet loss. Parallelism One attribute that all of the use cases have in common is parallelism. In order for largescale cloud services to meet real-time interactive latency requirements, the applications and storage must divide and conquer. There is simply too much data to process, and the true value of data is how quickly it can be rendered into human consumable information and action. As Figure 5 suggests, parallelism in a distributed system depends upon an enormous amount of messaging for synchronization and parameter distribution. Inherent in this messaging are traffic patterns that create congestion due to incast and disorderly flows. Left unattended, congestion leads to overall loss in the network: packet loss, latency loss and throughput loss. These network issues exacerbate application issues and result in bad user experiences. Successful data centers of the future must minimize these issues. Figure 5 – The Problem with Network Congestion Why Today’s Data Centers Aren’t Keeping Up Whether building a public cloud or a private data center that operates as an internal cloud service for enterprises, a common set of problems need to be addressed. Network designers need to build a highly flexible fabric for rapidly changing environments that carry a diverse set of traffic: application, storage and control. ommon goal to minimize or eliminate packet loss, provide high throughput and maintain low latency. These goals are especially important to support the applications of OLDI, Deep Learning, NVMe over Fabrics and the Cloudified CO. Today’s data centers typically use fat-tree architectures derived from the basic Clos network illustrated in Figure 6. The Clos network achieves non-blocking performance and resiliency through equal cost multi-paths. Layer 3 networking is typically used between the switches
1-18-0007-06-ICne-draft-report-lossless-data-center-networks.docx