Designing a Federated Testbed as a Distributed System

Ricci, Robert; Duerig, Jonathon; Stoller, Leigh; Wong, Gary; Chikkulapelly, Srikanth; Seok, Woojin

doi:10.1007/978-3-642-35576-9_26

Cited by 22 publications

(8 citation statements)

References 27 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The Emulab software also forms the basis for ProtoGENI, a GENI prototype and control framework, which extends the Emulab model to bridge multiple physical sites and support the GENI API (Ricci et al 2012).…”

Section: Emulabmentioning

confidence: 99%

Testbeds for WSNs

Fahmy

2016

Signals and Communication Technology

View full text Add to dashboard Cite

Simulation is imagining … Testbed is sore reality. WSN Testbeds PrinciplesAs iterated throughout this book, WSNs are large-scale distributed embedded systems incorporating small, limited energy, and resource constrained sensor nodes communicating over wireless media. Because of their massively distributed nature, the design, implementation and evaluation of sensor network applications, middleware and communication protocols are difficult tasks. The first design steps can often be made with the help of simulations; however, they frequently force the designer to make non-realistic assumptions about traffic, failure patterns and topologies. The coming after steps of implementation, and evaluation of application performance, as well as assessment of error resilience, and other nonfunctional properties, require the use of real hardware, realistic environments and realistic experimental setups.Practically, real experiments with distributed systems like WSNs become very cumbersome if the number of nodes exceeds a few dozens. In fact, all the phases of the experiment are almost infeasible without a targeted, specialized support, specifically:

show abstract

Section: Emulabmentioning

confidence: 99%

Testbeds for WSNs

Fahmy

2016

Signals and Communication Technology

View full text Add to dashboard Cite

show abstract

“…Connectivity to the VMs is maintained by the underlying infrastructure, relieving the GEE from maintaining and repairing this connectivity; instead, we can rely on the underlying GENI tools. InstaGENI PlanetLab was always envisioned as a subservice running over Proto-GENI [29] on the InstaGENI racks [4], and a convenient way for GENI users to run VM-based experiments. The GEE now replaces InstaGENI PlanetLab in this system, with four major enhancements:…”

Section: The Gee Compute Service (Fad Architecture)mentioning

confidence: 99%

The GENI Experiment Engine

Bavier

Chen

Mambretti

et al. 2015

Proceedings of the 10th EAI International Conference on Testbeds and Research Infrastructures for the Development of Networks &

View full text Add to dashboard Cite

We describe the GENI Experiment Engine, a Distributed-Platform-as-a-Service facility designed to be implemented on a distributed testbed or infrastructure. The GEE is intended to provide rapid and convenient access to a distributed infrastructure for simple, easy-to-configure experiments and applications. Specifically, the design goal of the GEE is to permit experimenters and application writers to: (a) allocate a GEE slicelet; (b) deploy a simple experiment or application; (c) run the experiment; (d) collect the results; and (e) tear down the experiment, starting from scratch, within five minutes. The GEE consists of a set of cooperating services over the GENI infrastructure, which together with rapidly-allocated slicelets and a rapidly-allocated network offers a complete, ready to use, sliceable platform over the GENI Infrastructure. The GEE is designed to use off-the-shelf components and infrastructure; unlike previous PaaS offerings, it can be nested nicely inside a GENI slice, or any other IaaS infrastructure. Further, the GEE's southbound interface is extremely small and lightweight, making it portable to other underlying infrastructures.

show abstract

“…InstaGENI PlanetLab was always envisioned as a subservice running over ProtoGENI [15] on the InstaGENI racks, and a convenient way for GENI users to run VM-based ex-periments. We have augmented this for GEE in three ways:…”

Section: The Gee Compute Servicementioning

confidence: 99%

The GENI experiment engine

Bavier¹,

Chen²,

Mambretti³

et al. 2014

2014 26th International Teletraffic Congress (ITC)

View full text Add to dashboard Cite

We describe the GENI Experiment Engine, a Distributed-Platform-as-a-Service facility designed to be implemented on a distributed testbed or infrastructure. The GEE is intended to provide rapid and convenient access to a distributed infrastructure for simple, easy-to-configure experiments and applications. Specifically, the design goal of the GEE is to permit experimenters and application writers to: (a) allocate a GEE slicelet; (b) deploy a simple experiment or application; (c) run the experiment; (d) collect the results; and (e) tear down the experiment, starting from scratch, within five minutes. The GEE consists of four cooperating services over the GENI infrastructure, which together with pre-allocated slicelets and a pre-allocated network offers a complete, ready to use, sliceable platform over the GENI Infrastructure.

show abstract

Designing a Federated Testbed as a Distributed System

Cited by 22 publications

References 27 publications

Testbeds for WSNs

Testbeds for WSNs

The GENI Experiment Engine

The GENI experiment engine

Contact Info

Product

Resources

About