Libra

Ammons, Glenn; Appavoo, Jonathan; Butrico, Maria; Silva, Dilma Da; Grove, David; Kawachiya, Kiyokuni; Krieger, Orran; Rosenburg, Bryan S.; Hensbergen, Eric Van; Wisniewski, Robert W.

doi:10.1145/1254810.1254817

Cited by 59 publications

(3 citation statements)

References 22 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Compared to a system emulation for binary compatibility, a libOS is more efficient because it runs in the same address space as the user application. It has been shown that a libOS can successfully run sophisticated commercial applications [6], [7], [11].…”

Section: Backward Compatibilitymentioning

confidence: 99%

“…In this paper we claim that OS virtualization allows dependable, predictable, and real-time computing since the operating system can consistently manage all system resources while exporting relevant information to the application. In Osprey, we combine OS virtualization with library 978-1-4673-2266-9/12/$31.00 ©2012 IEEE operating systems [6], [7], [8], which implement legacy OS personalities in the user space providing compatibility with legacy software. We implement library OSes on top of the Osprey kernel to enable high performance, real-time guarantees, and scalability on modern, massively multicore hardware.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Osprey: Operating system for predictable clouds

Šácha¹,

Napper²,

Mullender³

et al. 2012

IEEE/IFIP International Conference on Dependable Systems and Networks Workshops (DSN 2012)

View full text Add to dashboard Cite

Cloud computing is currently based on hardware virtualization wherein a host operating system provides a virtual machine interface nearly identical to that of physical hardware to guest operating systems. Full transparency allows backward compatibility with legacy software but introduces unpredictability at the guest operating system (OS) level. The time perceived by the guest OS is non-linear. As a consequence, it is difficult to run real-time or latency-sensitive applications in the cloud. In this paper we describe an alternative approach to cloud computing where we run all user applications on top of a single cloud operating system called Osprey. Osprey allows dependable, predictable, and real-time computing by consistently managing all system resources and exporting relevant information to the applications. Osprey ensures compatibility with legacy software through OS emulation provided by libraries and by porting runtime environments. Osprey's resource containers fully specify constraints between applications to enforce full application isolation for real-time execution guarantees. Osprey pushes much of the state out of the kernel into user applications for several benefits: full application accounting, mobility support, and efficient networking. Using a kernel-based packet filter, Osprey dispatches incoming packets to the user application as quickly as possible, eliminating the kernel from the critical path. A real-time scheduler then decides on the priority and order in which applications process their incoming packets while maintaining the limits set forth in the resource container. We have implemented a mostly complete Osprey prototype for the x86 architecture and we plan to port it to ARM and PowerPC and to develop a Linux library OS.

show abstract

Section: Backward Compatibilitymentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Osprey: Operating system for predictable clouds

Šácha¹,

Napper²,

Mullender³

et al. 2012

IEEE/IFIP International Conference on Dependable Systems and Networks Workshops (DSN 2012)

View full text Add to dashboard Cite

show abstract

“…FSVAs leverage VMs and existing hypervisor support to avoid the upfront implementation costs that held back microkernels. Libra enables quick construction of specialty OSs by reusing existing OS components in another VM [2]. In contrast to Libra, our FSVA design seeks deep integration between the user OS and the FSVA.…”

Section: Additional Related Workmentioning

confidence: 99%

File System Virtual Appliances: Third-Party File System Implementations Without the Pain

Abd-El-Malek¹,

Wachs²,

Cipar³

et al. 2008

View full text Add to dashboard Cite

File system virtual appliances (FSVAs) address a major headache faced by third-party FS developers: OS version compatibility. By packaging their FS implementation in a VM, separate from the VM that runs user applications, they can avoid the need to provide an FS port for every kernel version and OS distribution. A small FS-agnostic proxy, maintained by the core OS developers, connects the FSVA to whatever kernel version the user chooses. Evaluation of prototype FSVA support in Linux, using Xen as the VM platform, demonstrates that this separation can be efficient and maintain desired OS and virtualization features. Using three existing file systems and a cooperative caching extension as a case study, we demonstrate that the FSVA architecture can insulate FS implementations from user OS differences that would otherwise require explicit porting changes. Acknowledgements:We thank the members and companies of the CyLab Corporate Partners and the PDL Consortium (including APC, Cisco, EMC, Google, Hewlett-Packard, Hitachi, IBM, Intel, LSI, Microsoft, Network Appliance, Oracle, Seagate, Symantec, and VMware) for their interest, insights, feedback, and support. This material is based on research sponsored in part by the National Science Foundation, via grants CNS-0326453 and CCF-0621499, by the Department of Energy, under Award Number DE-FC02-06ER25767, and by the Army Research Office, under agreement number DAAD19-02-1-0389. Matthew Wachs was supported in part by an NDSEG Fellowship, which is sponsored by the Department of Defense. We thank Intel and Network Appliance for hardware donations that enabled this work. Report Documentation Page

show abstract

Predictable Cloud Computing

Mullender¹

2012

Bell Labs Tech. J.

View full text Add to dashboard Cite

The standard tools for cloud computing-processor and network virtualization-make it difficult to achieve dependability, both in terms of real time operations and fault tolerance. Virtualization multiplexes virtual resources onto physical ones, typically by time division or statistical multiplexing. Time, in the virtual machine, is therefore as virtual as the machine itself. And fault tolerance is difficult to achieve when redundancy and independent failure in the virtual environment do not necessarily map to those properties in the physical environment. Virtualization adds a level of indirection that creates overhead, and makes it all but impossible to achieve predictable performance. Osprey uses an alternative to virtualization that achieves the same goals of scalability and flexibility but carries neither the overhead of virtualization, nor the restrictions on dependability. The result is a programming environment that achieves most of the compatibility offered by traditional virtualization efforts and provides much better and much more predictable performance. One technique we use is called Library OS, which stems from high-performance computing. The technique consists of linking applications with a library that implements most services normally provided by the operating system, creating an application that can run practically stand alone, or at least with a very minimal operating system. The Library OS approach moves the boundary between application and operating system down to a level where interactions with the operating system consist of sending/receiving messages (e.g., network packets) and scheduling resources (processor, memory, network bandwidth, and device access). These interactions, as we demonstrate, form a relatively weak bond between an application and the particular instance of the operating system on which it runs-one that can be broken and re-established elsewhere. In fact, we make sure this is the case. Legacy applications that cannot be recompiled or relinked can make use of a Library OS server that runs as a tandem process along with the legacy application processes. System calls from the legacy process are catapulted into the Library OS server which executes them. Applications can still migrate, taking their server process along with them.

show abstract

Libra

Cited by 59 publications

References 22 publications

Osprey: Operating system for predictable clouds

Osprey: Operating system for predictable clouds

File System Virtual Appliances: Third-Party File System Implementations Without the Pain

Predictable Cloud Computing

Contact Info

Product

Resources

About