CORONET: Testbeds, Cloud Computing, and Lessons Learned
A. Von Lehmen, Robert D. Doverspike, George Clapp, Douglas M. Freimuth, Joel W. Gannett, Keith Kim, Haim Kobrinski, Emmanuil Mavrogiorgis, Jorge L. Pastor, Michael E. Rauch, Kadangode K. Ramakrishnan, Ron Skoog, Brian J. Wilson, Sheryl L. Woodward · Optical Fiber Communication Conference · 2014
Abstract: We summarize the DARPA CORONET program approach to bandwidth-on-demand, and implementation and demonstration of Cloud Computing applications in network testbeds. OCIS codes: (060.4253) Networks, circuit-switched; (060.4265) Networks, wavelength routing Recently, there has been major impetus for Bandwidth-on-Demand (BoD) in carrier networks, driven by the burgeoning demand for cloud computing services and a desire to reduce costs through bandwidth sharing. Applications such as file transfer, scheduled and unscheduled backup, virtual machine (VM) transfer, data fusion, etc. have spawned a large variety of potential requirements for bandwidth, latency, connection setup times, Quality of Service (QoS), etc. The DARPA CORONET program [1] laid out a vision for a highly dynamic IP and optical networking environment anticipating the broad spectrum of requirements for such services. CORONET bandwidth requirements span several orders of magnitude, from ~ 100 Mbps to nearly a Tbps per service request, across multiple layers in the network. Service setup time requirements range from very fast subsecond setup times to scheduled services, with acceptable blocking constrained to be below 10-3. CORONET also includes stringent QoS metrics for packet loss (10-5), as well as requirements for resilience against up to three failures. Traffic level objectives are 20-100 Tbps network-wide, representing a carrier network of the future, with a mix of IP and private line traffic along with highly variable BoD traffic. Finally, the CORONET program requires that these requirements