The use of name spaces in plan 9

Pike, Rob; Presotto, Dave; Thompson, Ken; Trickey, Howard; Winterbottom, Phil

doi:10.1145/506378.506413

Cited by 25 publications

(17 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The idea of containers dates back to 1992 [16] and have matured over the years with the introduction of Linux namespace [2] and the LXC project [10], a solution designed to execute full operating system images in containers. Application containers [12] are an evolution of operating system virtualization.…”

Section: Container Technologiesmentioning

confidence: 99%

Measuring Docker Performance

Casalicchio

Perciballi

2017

Proceedings of the 8th ACM/SPEC on International Conference on Performance Engineering Companion

View full text Add to dashboard Cite

Today, a new technology is going to change the way platforms for the internet of services are designed and managed. This technology is called container (e.g. Docker and LXC). The internet of service industry is adopting the container technology both for internal usage and as commercial offering. The use of container as base technology for largescale systems opens many challenges in the area of resource management at run-time, for example: autoscaling, optimal deployment and monitoring. Specifically, monitoring of container based systems is at the ground of any resource management solution, and it is the focus of this work. This paper explores the tools available to measure the performance of Docker from the perspective of the host operating system and of the virtualization environment, and it provides a characterization of the CPU and disk I/O overhead introduced by containers.

show abstract

Section: Container Technologiesmentioning

confidence: 99%

Measuring Docker Performance

Casalicchio

Perciballi

2017

Proceedings of the 8th ACM/SPEC on International Conference on Performance Engineering Companion

View full text Add to dashboard Cite

show abstract

“…Plan 9 [12] was the first operating system to introduce a filesystem-based pattern or style for accessing arbitrary IO systems, e.g. general filesystems, network interfaces, and processes.…”

Section: Background and Related Workmentioning

confidence: 99%

Stroll: A Universal Filesystem-Based Interface for Seamless Task Deployment in Grid Computing

Azab

Meling

2012

Distributed Applications and Interoperable Systems

View full text Add to dashboard Cite

Abstract. Developing applications for solving compute intensive problems is not trivial. Despite availability of a range of Grid computing platforms, domain specialists and scientists only rarely take advantage of these computing facilities. One reason for this is the complexity of Grid computing, and the need to learn a new programming environment to interact with the Grid. Typically, only a few programming languages are supported, and often scientists use special-purpose languages that are not supported by most Grid platforms. Moreover, users cannot easily deploy their compute tasks to multiple Grid platforms without rewriting their program to use different task submission interfaces.In this paper we present Stroll, a universal filesystem-based interface for seamless task submission to one or more Grid facilities. Users interact with the Grid through simple read and write filesystem commands. Stroll allows all categories of users to submit and manage compute tasks both manually, and from within their programs, which may be written in any language. Stroll has been implemented on Windows and Linux, and we demonstrate that we can submit the same compute tasks to both Condor and Unicore clusters. Our evaluation shows the overhead of Stroll to negligible. Comparing the code complexity of a Stroll compute task with command-line clients and Grid APIs show that Stroll can eliminated up to 95% of the complexity.

show abstract

“…Following the plan 9 paradigm [10]. "every resource in the system, either local or remote, is represented by a hierarchical file system; and a user or process assembles a private view of the system by constructing a file name space that connects these resources".…”

Section: Logical and Physical Mobilitymentioning

confidence: 99%

A distributed resource management architecture for interconnecting Web-of-Things using uBox

Namatame

Ding

Riedel

et al. 2011

Proceedings of the Second International Workshop on Web of Things

View full text Add to dashboard Cite

Although there are many smart devices and networked embedded object applications using World Wide Web technologies, it is still a big step to go towards a true Web of Things. It is e.g. difficult to build ubiquitous WoT applications that work in and accross multiple environments. Approaches which aggregate WoT ressources by centralizing all the resource information, have problems: total dependency on external infrasture, lack of private WoT management, inflexible communication patterns and limited dynamic ressource discovery and mapping. To solve these problems, we propose uBox, a local WoT platform which can be a stand-alone server to make your WoT environment, with interfaces to connect the other local WoT platforms. This way, which we call uBoXing, we can create World Wide WoT platform with a distributed architecture. This paper describes the concept of a distributed resource management architecture, and how we implement the concept into software. Also, we will discuss the platform with the example application in SmartTecO environment.

show abstract

The use of name spaces in plan 9

Cited by 25 publications

References 0 publications

Measuring Docker Performance

Measuring Docker Performance

Stroll: A Universal Filesystem-Based Interface for Seamless Task Deployment in Grid Computing

A distributed resource management architecture for interconnecting Web-of-Things using uBox

Contact Info

Product

Resources

About