| 6686 | <a class="EntryGoto" id="Rakotoarivelo, Thierry and Jourjon, Guillaume and Mehani, Olivier and Ott, Maximilian and Zink, Mike"></a> |
| 6687 | <b class="myheading" style="position: relative; left: 5%;">Rakotoarivelo, Thierry and Jourjon, Guillaume and Mehani, Olivier and Ott, Maximilian and Zink, Mike</b> |
| 6688 | |
| 6689 | <div class="BibEntry"> |
| 6690 | |
| 6691 | <table class="EntryTable" style="position: relative; left: 5%; width: 90%; border:thin solid black; border-spacing:10px;"> |
| 6692 | |
| 6693 | <li> |
| 6694 | |
| 6695 | |
| 6696 | <tr> |
| 6697 | <td valign="top">Author</td> |
| 6698 | <td valign="top">Rakotoarivelo, Thierry and Jourjon, Guillaume and Mehani, Olivier and Ott, Maximilian and Zink, Mike</td> |
| 6699 | </tr> |
| 6700 | |
| 6701 | <tr> |
| 6702 | <td valign="top">Title</td> |
| 6703 | <td valign="top">Repeatable Experiments with LabWiki</td> |
| 6704 | </tr> |
| 6705 | |
| 6706 | <tr> |
| 6707 | <td valign="top">Year</td> |
| 6708 | <td valign="top">2014</td> |
| 6709 | </tr> |
| 6710 | |
| 6711 | <tr> |
| 6712 | <td valign="top">Abstract</td> |
| 6713 | <td valign="top">The ability to repeat the experiments from a research study and obtain similar results is a corner stone in experiment-based scientific discovery. This essential feature has been often ignored by the distributed computing and networking community. There are many reasons for that, such as the complexity of provisioning, configuring, and orchestrating the resources used by experiments, their multiple external dependencies, and the difficulty to seamlessly record these dependencies. This paper describes a methodology based on well-established principles to plan, prepare and execute experiments. We propose and describe a family of tools, the LabWiki workspace, to support an experimenter's workflow based on that methodology. This proposed workspace provides services and mechanisms for each step of an experiment-based study, while automatically capturing the necessary information to allow others to repeat, inspect, validate and modify prior experiments. Our LabWiki workspace builds on existing contributions, and de-facto protocol and model standards, which emerged from recent experimental facility initiatives. We use a real experiment as a thread to guide and illustrate the discussion throughout this paper.</td> |
| 6714 | </tr> |
| 6715 | |
| 6716 | |
| 6717 | |
| 6718 | |
| 6719 | |
| 6720 | <tr> |
| 6721 | <td valign="top">URL</td> |
| 6722 | <td valign="top"><a href="http://arxiv.org/abs/1410.1681">http://arxiv.org/abs/1410.1681</a></td> |
| 6723 | </tr> |
| 6724 | |
| 6725 | |
| 6726 | </li> |
| 6727 | |
| 6728 | </table></div><br><br> |
| 6729 | |
| 6730 | |
| 6731 | |
| 6732 | |
| 7080 | <a class="EntryGoto" id="Seetharam, Sripriya and Calyam, Prasad and Beyene, Tsegereda"></a> |
| 7081 | <b class="myheading" style="position: relative; left: 5%;">Seetharam, Sripriya and Calyam, Prasad and Beyene, Tsegereda</b> |
| 7082 | |
| 7083 | <div class="BibEntry"> |
| 7084 | |
| 7085 | <table class="EntryTable" style="position: relative; left: 5%; width: 90%; border:thin solid black; border-spacing:10px;"> |
| 7086 | |
| 7087 | <li> |
| 7088 | |
| 7089 | |
| 7090 | <tr> |
| 7091 | <td valign="top">Author</td> |
| 7092 | <td valign="top">Seetharam, Sripriya and Calyam, Prasad and Beyene, Tsegereda</td> |
| 7093 | </tr> |
| 7094 | |
| 7095 | <tr> |
| 7096 | <td valign="top">Title</td> |
| 7097 | <td valign="top">ADON: Application-Driven Overlay Network-as-a-Service for Data-Intensive Science</td> |
| 7098 | </tr> |
| 7099 | |
| 7100 | <tr> |
| 7101 | <td valign="top">Year</td> |
| 7102 | <td valign="top">2014</td> |
| 7103 | </tr> |
| 7104 | |
| 7105 | <tr> |
| 7106 | <td valign="top">Abstract</td> |
| 7107 | <td valign="top">Campuses are increasingly adopting hybrid cloud architectures for supporting data-intensive science applications that require ” on-demand” resources, which are not always available locally on-site. Policies at the campus edge for handling multiple such applications competing for remote resources can cause bottlenecks across applications. These bottlenecks can be proactively avoided with pertinent profiling, monitoring and control of application flows using software-defined networking principles. In this paper, we present an ” Application-driven Overlay Network-as-a-Service” (ADON) that can manage the hybrid cloud requirements of multiple applications in a scalable and extensible manner using features such as: programmable ” custom templates” and a ” virtual tenant handler”. Our solution approach involves scheduling transit selection and traffic engi- neering at the campus-edge based on real-time policy control that ensures predictable application performance delivery for multi-tenant traffic profiles. We validate our ADON approach with an implementation on a wide-area overlay network testbed across two campuses, and present a workflow that eases the orchestration of network programmability for campus network providers and data-intensive application users. Lastly, we present an emulation study of the ADON effectiveness in handling temporal behavior of multi-tenant traffic burst arrivals using profiles from a diverse set of actual data-intensive applications.</td> |
| 7108 | </tr> |
| 7109 | |
| 7110 | |
| 7111 | |
| 7112 | |
| 7113 | |
| 7114 | <tr> |
| 7115 | <td valign="top">URL</td> |
| 7116 | <td valign="top"><a href="http://people.cs.missouri.edu/~calyamp/publications/adon-cloudnet14.pdf">http://people.cs.missouri.edu/~calyamp/publications/adon-cloudnet14.pdf</a></td> |
| 7117 | </tr> |
| 7118 | |
| 7119 | |
| 7120 | </li> |
| 7121 | |
| 7122 | </table></div><br><br> |
| 7123 | |
| 7124 | |
| 7125 | |
| 7126 | |