The Experts below are selected from a list of 55260 Experts worldwide ranked by ideXlab platform
John H. Hartman - One of the best experts on this subject based on the ideXlab platform.
-
Stork: secure Package Management for vm environments
2008Co-Authors: John H. Hartman, Justin CapposAbstract:Package managers are a common tool for installing, removing, and updating software on modern computer systems. Unfortunately existing Package managers have two major problems. First, inadequate security leads to vulnerability to attack. There are nine feasible attacks against modern Package managers, many of which are enabled by flaws in the underlying security architecture. Second, in Virtual Machine (VM) environments such as Xen, VMWare, and VServers, different VMs on the same physical machine are treated as separate systems by Package managers leading to redundant Package downloads and installations. This dissertation focuses on the design, development, and evaluation of a Package manager called Stork that does not have these problems. Stork provides a security architecture that prevents the attacks other Package managers are vulnerable to. Stork also is efficient in VM environments and reduces redundant Package Management actions. Stork is a real system that has been in use for four years and has managed half a million VM instantiations.
-
stork Package Management for distributed vm environments
USENIX Large Installation Systems Administration Conference, 2007Co-Authors: Justin Cappos, Scott E Baker, Jeremy Plichta, Duy Nyugen, Jason Hardies, Matt Borgard, Jeffry Johnston, John H. HartmanAbstract:In virtual machine environments each application is often run in its own virtual machine (VM), isolating it from other applications running on the same physical machine. Contention for memory, disk space, and network bandwidth among virtual machines, coupled with an inability to share due to the isolation virtual machines provide, leads to heavy resource utilization. Additionally, VMs increase Management overhead as each is essentially a separate system. Stork is a Package Management tool for virtual machine environments that is designed to alleviate these problems. Stork securely and efficiently downloads Packages to physical machines and shares Packages between VMs. Disk space and memory requirements are reduced because shared files, such as libraries and binaries, require only one persistent copy per physical machine. Experiments show that Stork reduces the disk space required to install additional copies of a Package by over an order of magnitude, and memory by about 50%. Stork downloads each Package once per physical machine no matter how many VMs install it. The transfer protocols used during download improve elapsed time by 7X and reduce repository traffic by an order of magnitude. Stork users can manage groups of VMs with the ease of managing a single machine - even groups that consist of machines distributed around the world. Stork is a real service that has run on PlanetLab for over four years and has managed thousands of VMs.
-
LISA - Stork: Package Management for distributed VM environments
2007Co-Authors: Justin Cappos, Scott E Baker, Jeremy Plichta, Duy Nyugen, Jason Hardies, Matt Borgard, Jeffry Johnston, John H. HartmanAbstract:In virtual machine environments each application is often run in its own virtual machine (VM), isolating it from other applications running on the same physical machine. Contention for memory, disk space, and network bandwidth among virtual machines, coupled with an inability to share due to the isolation virtual machines provide, leads to heavy resource utilization. Additionally, VMs increase Management overhead as each is essentially a separate system. Stork is a Package Management tool for virtual machine environments that is designed to alleviate these problems. Stork securely and efficiently downloads Packages to physical machines and shares Packages between VMs. Disk space and memory requirements are reduced because shared files, such as libraries and binaries, require only one persistent copy per physical machine. Experiments show that Stork reduces the disk space required to install additional copies of a Package by over an order of magnitude, and memory by about 50%. Stork downloads each Package once per physical machine no matter how many VMs install it. The transfer protocols used during download improve elapsed time by 7X and reduce repository traffic by an order of magnitude. Stork users can manage groups of VMs with the ease of managing a single machine - even groups that consist of machines distributed around the world. Stork is a real service that has run on PlanetLab for over four years and has managed thousands of VMs.
Justin Cappos - One of the best experts on this subject based on the ideXlab platform.
-
Stork: secure Package Management for vm environments
2008Co-Authors: John H. Hartman, Justin CapposAbstract:Package managers are a common tool for installing, removing, and updating software on modern computer systems. Unfortunately existing Package managers have two major problems. First, inadequate security leads to vulnerability to attack. There are nine feasible attacks against modern Package managers, many of which are enabled by flaws in the underlying security architecture. Second, in Virtual Machine (VM) environments such as Xen, VMWare, and VServers, different VMs on the same physical machine are treated as separate systems by Package managers leading to redundant Package downloads and installations. This dissertation focuses on the design, development, and evaluation of a Package manager called Stork that does not have these problems. Stork provides a security architecture that prevents the attacks other Package managers are vulnerable to. Stork also is efficient in VM environments and reduces redundant Package Management actions. Stork is a real system that has been in use for four years and has managed half a million VM instantiations.
-
stork Package Management for distributed vm environments
USENIX Large Installation Systems Administration Conference, 2007Co-Authors: Justin Cappos, Scott E Baker, Jeremy Plichta, Duy Nyugen, Jason Hardies, Matt Borgard, Jeffry Johnston, John H. HartmanAbstract:In virtual machine environments each application is often run in its own virtual machine (VM), isolating it from other applications running on the same physical machine. Contention for memory, disk space, and network bandwidth among virtual machines, coupled with an inability to share due to the isolation virtual machines provide, leads to heavy resource utilization. Additionally, VMs increase Management overhead as each is essentially a separate system. Stork is a Package Management tool for virtual machine environments that is designed to alleviate these problems. Stork securely and efficiently downloads Packages to physical machines and shares Packages between VMs. Disk space and memory requirements are reduced because shared files, such as libraries and binaries, require only one persistent copy per physical machine. Experiments show that Stork reduces the disk space required to install additional copies of a Package by over an order of magnitude, and memory by about 50%. Stork downloads each Package once per physical machine no matter how many VMs install it. The transfer protocols used during download improve elapsed time by 7X and reduce repository traffic by an order of magnitude. Stork users can manage groups of VMs with the ease of managing a single machine - even groups that consist of machines distributed around the world. Stork is a real service that has run on PlanetLab for over four years and has managed thousands of VMs.
-
LISA - Stork: Package Management for distributed VM environments
2007Co-Authors: Justin Cappos, Scott E Baker, Jeremy Plichta, Duy Nyugen, Jason Hardies, Matt Borgard, Jeffry Johnston, John H. HartmanAbstract:In virtual machine environments each application is often run in its own virtual machine (VM), isolating it from other applications running on the same physical machine. Contention for memory, disk space, and network bandwidth among virtual machines, coupled with an inability to share due to the isolation virtual machines provide, leads to heavy resource utilization. Additionally, VMs increase Management overhead as each is essentially a separate system. Stork is a Package Management tool for virtual machine environments that is designed to alleviate these problems. Stork securely and efficiently downloads Packages to physical machines and shares Packages between VMs. Disk space and memory requirements are reduced because shared files, such as libraries and binaries, require only one persistent copy per physical machine. Experiments show that Stork reduces the disk space required to install additional copies of a Package by over an order of magnitude, and memory by about 50%. Stork downloads each Package once per physical machine no matter how many VMs install it. The transfer protocols used during download improve elapsed time by 7X and reduce repository traffic by an order of magnitude. Stork users can manage groups of VMs with the ease of managing a single machine - even groups that consist of machines distributed around the world. Stork is a real service that has run on PlanetLab for over four years and has managed thousands of VMs.
Todd Gamblin - One of the best experts on this subject based on the ideXlab platform.
-
Preserving Command Line Workflow for a Package Management System Using ASCII DAG Visualization
IEEE transactions on visualization and computer graphics, 2018Co-Authors: Katherine E. Isaacs, Todd GamblinAbstract:Package managers provide ease of access to applications by removing the time-consuming and sometimes completely prohibitive barrier of successfully building, installing, and maintaining the software for a system. A Package dependency contains dependencies between all Packages required to build and run the target software. Package Management system developers, Package maintainers, and users may consult the dependency graph when a simple listing is insufficient for their analyses. However, users working in a remote command line environment must disrupt their workflow to visualize dependency graphs in graphical programs, possibly needing to move files between devices or incur forwarding lag. Such is the case for users of Spack, an open source Package Management system originally developed to ease the complex builds required by supercomputing environments. To preserve the command line workflow of Spack, we develop an interactive ASCII visualization for its dependency graphs. Through interviews with Spack maintainers, we identify user goals and corresponding visual tasks for dependency graphs. We evaluate the use of our visualization through a command line-centered study, comparing it to the system's two existing approaches. We observe that despite the limitations of the ASCII representation, our visualization is preferred by participants when approached from a command line interface workflow.
Yuan Tao - One of the best experts on this subject based on the ideXlab platform.
-
Construction and Maintenance of Embedded Linux Based on Ipkg Package Management Program
Computer Engineering, 2007Co-Authors: Yuan TaoAbstract:With ipkg Package Management program,developers can avoid trivial steps involving cross compilation,quickly build up embedded Linux system,and enable the software to upgrade automatically.This paper introduces the concept of ipkg Package Management and the Package format,and presents the bootstrap process.Taking embedded Web server as an example,the construction of an application system is illustracted.And a Package construction process with a Qt graphic system is introduced.
Inge Jonassen - One of the best experts on this subject based on the ideXlab platform.
-
RASflow: an RNA-Seq analysis workflow with Snakemake
BMC Bioinformatics, 2020Co-Authors: Xiaokang Zhang, Inge JonassenAbstract:Background With the cost of DNA sequencing decreasing, increasing amounts of RNA-Seq data are being generated giving novel insight into gene expression and regulation. Prior to analysis of gene expression, the RNA-Seq data has to be processed through a number of steps resulting in a quantification of expression of each gene/transcript in each of the analyzed samples. A number of workflows are available to help researchers perform these steps on their own data, or on public data to take advantage of novel software or reference data in data re-analysis. However, many of the existing workflows are limited to specific types of studies. We therefore aimed to develop a maximally general workflow, applicable to a wide range of data and analysis approaches and at the same time support research on both model and non-model organisms. Furthermore, we aimed to make the workflow usable also for users with limited programming skills. Results Utilizing the workflow Management system Snakemake and the Package Management system Conda, we have developed a modular, flexible and user-friendly RNA-Seq analysis workflow: RNA-Seq Analysis Snakemake Workflow (RASflow). Utilizing Snakemake and Conda alleviates challenges with library dependencies and version conflicts and also supports reproducibility. To be applicable for a wide variety of applications, RASflow supports the mapping of reads to both genomic and transcriptomic assemblies. RASflow has a broad range of potential users: it can be applied by researchers interested in any organism and since it requires no programming skills, it can be used by researchers with different backgrounds. The source code of RASflow is available on GitHub: https://github.com/zhxiaokang/RASflow . Conclusions RASflow is a simple and reliable RNA-Seq analysis workflow covering many use cases.
