The Experts below are selected from a list of 4530 Experts worldwide ranked by ideXlab platform
Samia Nefti - One of the best experts on this subject based on the ideXlab platform.
-
QUIET: A Methodology for Autonomous Software Deployment using Mobile Agents
Journal of Network and Computer Applications, 2010Co-Authors: Umar Manzoor, Samia NeftiAbstract:Every software setup has an installation wizard that helps the user to install/un-install the software on PCs. Typically user interaction is required and the process cannot proceed without user input. Silent Unattended Installation Package Manager (SUIPM) automates the process of software installation/un-installation and can be used to deploy any software silently without user interaction. In this paper, we have proposed A Methodology for Autonomous Software Deployment using Mobile Agents, which deploys silent unattended installation/un-installation Packages efficiently and smartly on networks without user interaction or intervention, suitable for network of networks, commonly known as CAN (campus area network). The system once initialized is fully autonomous and deployment of the software(s) is performed efficiently and autonomously with the help of mobile agents. We have evaluated this architecture on the university campus having 7 laboratories equipped with 20-300 PCs in various laboratories. Results are very promising and support the implementation of the solution.
-
silent unattended installation Package Manager suipm
Computational Intelligence for Modelling Control and Automation, 2008Co-Authors: Umar Manzoor, Samia NeftiAbstract:An installation that is performed without user interaction and does not display any message or GUI during its progress is known as silent and unattended installation. In this paper we have proposed silent unattended installation Package Manager (SUIPM) that automates the process of silent unattended installations and un-installations and requires the minimal possible level of interaction with the user. Silent unattended installation Package Manager (SUIPM) not only introduces new methodology but generalize the process of silent and unattended installation /un-installation. Agent based activity monitoring system - ABAMS is responsible for the deployment of SUIPM Packages on the specified locations of the network. The process is fully autonomous and does not require any user interaction. SUIPM has been evaluated on large number of softwarepsilas and results were very promising and support the implementation of the solution.
-
CIMCA/IAWTIC/ISE - Silent Unattended Installation Package Manager--SUIPM
2008 International Conference on Computational Intelligence for Modelling Control & Automation, 2008Co-Authors: Umar Manzoor, Samia NeftiAbstract:An installation that is performed without user interaction and does not display any message or GUI during its progress is known as silent and unattended installation. In this paper we have proposed silent unattended installation Package Manager (SUIPM) that automates the process of silent unattended installations and un-installations and requires the minimal possible level of interaction with the user. Silent unattended installation Package Manager (SUIPM) not only introduces new methodology but generalize the process of silent and unattended installation /un-installation. Agent based activity monitoring system - ABAMS is responsible for the deployment of SUIPM Packages on the specified locations of the network. The process is fully autonomous and does not require any user interaction. SUIPM has been evaluated on large number of softwarepsilas and results were very promising and support the implementation of the solution.
Stefano Zacchiroli - One of the best experts on this subject based on the ideXlab platform.
-
Dependency Solving Is Still Hard, but We Are Getting Better at It
2020 IEEE 27th International Conference on Software Analysis Evolution and Reengineering (SANER), 2020Co-Authors: Pietro Abate, Roberto Di Cosmo, Georgios Gousios, Stefano ZacchiroliAbstract:Dependency solving is a hard (NP-complete) problem in all non-trivial component models due to either mutually incompatible versions of the same Packages or explicitly declared Package conflicts. As such, software upgrade planning needs to rely on highly specialized dependency solvers, lest falling into pitfalls such as incompleteness-a combination of Package versions that satisfy dependency constraints does exist, but the Package Manager is unable to find it. In this paper we look back at proposals from dependency solving research dating back a few years. Specifically, we review the idea of treating dependency solving as a separate concern in Package Manager implementations, relying on generic dependency solvers based on tried and tested techniques such as SAT solving, PBO, MILP, etc. By conducting a census of dependency solving capabilities in state-of-the-art Package Managers we conclude that some proposals are starting to take off (e.g., SAT-based dependency solving) while-with few exceptions-others have not (e.g., out-sourcing dependency solving to reusable components). We reflect on why that has been the case and look at novel challenges for dependency solving that have emerged since.
-
using preferences to tame your Package Manager
2014Co-Authors: Pietro Abate, Fabrice Le Fessant, Roberto Di Cosmo, Louis Gesbert, Stefano ZacchiroliAbstract:Determining whether some components can be installed on a system is a complex problem: not only it is NP-complete in the worst case, but there can also be exponentially many solutions to it. Ordinary Package Managers use ad-hoc heuristics to solve this installation problem and choose a particular solution, making extremely difficult to change or sidestep these heuristics when the result is not the one we expect. When software repositories become complex enough, one gets vastly superior results by delegating dependency handling to a specialised solver, and use optimisation functions (or preferences) to control the class of solutions that are found. The opam Package Manager relies on the CUDF pivot format, which allows OCaml users that have a CUDF-compliant solver on their machine to reap the benefits of preferences-based dependency resolution. Thanks to the solver farm provided by Irill, these benefits are now extended to the OCaml community at large. In this talk we will present the preferences language and explain how to use it.
-
A modular Package Manager architecture
Information and Software Technology, 2013Co-Authors: Pietro Abate, Roberto Di Cosmo, Ralf Treinen, Stefano ZacchiroliAbstract:Context: The success of modern software distributions in the Free and Open Source world can be explained, among other factors, by the availability of a large collection of software Packages and the possibility to easily install and remove those components using state-of-the-art Package Managers. However, Package Managers are often built using a monolithic architecture and hard-wired and ad-hoc dependency solvers implementing some customized heuristics. Objective: We aim at laying the foundation for improving on existing Package Managers. Package Managers should be complete, that is find a solution whenever there exists one, and allow the user to specify complex criteria that define how to pick the best solution according to the user's preferences. Method: In this paper we propose a modular architecture relying on precise interface formalisms that allows the system administrator to choose from a variety of dependency solvers and backends. Results: We have built a working prototype-called MPM-following the design advocated in this paper, and we show how it largely outperforms a variety of current Package Managers. Conclusion: We argue that a modular architecture, allowing for delegating the task of constraint solving to external solvers, is the path that leads to the next generation of Package Managers that will deliver better results, offer more expressive preference languages, and be easily adaptable to new platforms.
-
mpm a modular Package Manager
Component-Based Software Engineering, 2011Co-Authors: Pietro Abate, Ralf Treinen, Roberto Dicosmo, Stefano ZacchiroliAbstract:Software distributions in the FOSS world rely on so-called Package Managers for the installation and removal of Packages on target machines. State-of-the-art Package Managers are monolithic in architecture, and each of them is hard-wired to an ad-hoc dependency solver implementing a customized heuristics. In this paper we propose a modular architecture allowing for pluggable dependency solvers and backends. We argue that this is the path that leads to the next generation of Package Managers that will deliver better results, accept more expressive input languages, and can be easily adaptable to new platforms. We present a working prototype---called MPM---which has been implemented following the design advocated in this paper.
-
CBSE - MPM: a modular Package Manager
Proceedings of the 14th international ACM Sigsoft symposium on Component based software engineering - CBSE '11, 2011Co-Authors: Pietro Abate, Ralf Treinen, Roberto Dicosmo, Stefano ZacchiroliAbstract:Software distributions in the FOSS world rely on so-called Package Managers for the installation and removal of Packages on target machines. State-of-the-art Package Managers are monolithic in architecture, and each of them is hard-wired to an ad-hoc dependency solver implementing a customized heuristics. In this paper we propose a modular architecture allowing for pluggable dependency solvers and backends. We argue that this is the path that leads to the next generation of Package Managers that will deliver better results, accept more expressive input languages, and can be easily adaptable to new platforms. We present a working prototype---called MPM---which has been implemented following the design advocated in this paper.
Umar Manzoor - One of the best experts on this subject based on the ideXlab platform.
-
QUIET: A Methodology for Autonomous Software Deployment using Mobile Agents
Journal of Network and Computer Applications, 2010Co-Authors: Umar Manzoor, Samia NeftiAbstract:Every software setup has an installation wizard that helps the user to install/un-install the software on PCs. Typically user interaction is required and the process cannot proceed without user input. Silent Unattended Installation Package Manager (SUIPM) automates the process of software installation/un-installation and can be used to deploy any software silently without user interaction. In this paper, we have proposed A Methodology for Autonomous Software Deployment using Mobile Agents, which deploys silent unattended installation/un-installation Packages efficiently and smartly on networks without user interaction or intervention, suitable for network of networks, commonly known as CAN (campus area network). The system once initialized is fully autonomous and deployment of the software(s) is performed efficiently and autonomously with the help of mobile agents. We have evaluated this architecture on the university campus having 7 laboratories equipped with 20-300 PCs in various laboratories. Results are very promising and support the implementation of the solution.
-
silent unattended installation Package Manager suipm
Computational Intelligence for Modelling Control and Automation, 2008Co-Authors: Umar Manzoor, Samia NeftiAbstract:An installation that is performed without user interaction and does not display any message or GUI during its progress is known as silent and unattended installation. In this paper we have proposed silent unattended installation Package Manager (SUIPM) that automates the process of silent unattended installations and un-installations and requires the minimal possible level of interaction with the user. Silent unattended installation Package Manager (SUIPM) not only introduces new methodology but generalize the process of silent and unattended installation /un-installation. Agent based activity monitoring system - ABAMS is responsible for the deployment of SUIPM Packages on the specified locations of the network. The process is fully autonomous and does not require any user interaction. SUIPM has been evaluated on large number of softwarepsilas and results were very promising and support the implementation of the solution.
-
CIMCA/IAWTIC/ISE - Silent Unattended Installation Package Manager--SUIPM
2008 International Conference on Computational Intelligence for Modelling Control & Automation, 2008Co-Authors: Umar Manzoor, Samia NeftiAbstract:An installation that is performed without user interaction and does not display any message or GUI during its progress is known as silent and unattended installation. In this paper we have proposed silent unattended installation Package Manager (SUIPM) that automates the process of silent unattended installations and un-installations and requires the minimal possible level of interaction with the user. Silent unattended installation Package Manager (SUIPM) not only introduces new methodology but generalize the process of silent and unattended installation /un-installation. Agent based activity monitoring system - ABAMS is responsible for the deployment of SUIPM Packages on the specified locations of the network. The process is fully autonomous and does not require any user interaction. SUIPM has been evaluated on large number of softwarepsilas and results were very promising and support the implementation of the solution.
Stefano Monti - One of the best experts on this subject based on the ideXlab platform.
-
Pipeliner: A Nextflow-Based Framework for the Definition of Sequencing Data Processing Pipelines.
Frontiers in genetics, 2019Co-Authors: Anthony Federico, Tanya T. Karagiannis, Kritika Karri, Dileep Kishore, Yusuke Koga, Joshua D. Campbell, Stefano MontiAbstract:The advent of high-throughput sequencing technologies has led to the need for flexible and user-friendly data preprocessing platforms. The Pipeliner framework provides an out-of-the-box solution for processing various types of sequencing data. It combines the Nextflow scripting language and Anaconda Package Manager to generate modular computational workflows. We have used Pipeliner to create several pipelines for sequencing data processing including bulk RNA-sequencing (RNA-seq), single-cell RNA-seq, as well as digital gene expression data. This report highlights the design methodology behind Pipeliner that enables the development of highly flexible and reproducible pipelines that are easy to extend and maintain on multiple computing environments. We also provide a quick start user guide demonstrating how to setup and execute available pipelines with toy datasets.
Pietro Abate - One of the best experts on this subject based on the ideXlab platform.
-
Dependency Solving Is Still Hard, but We Are Getting Better at It
2020 IEEE 27th International Conference on Software Analysis Evolution and Reengineering (SANER), 2020Co-Authors: Pietro Abate, Roberto Di Cosmo, Georgios Gousios, Stefano ZacchiroliAbstract:Dependency solving is a hard (NP-complete) problem in all non-trivial component models due to either mutually incompatible versions of the same Packages or explicitly declared Package conflicts. As such, software upgrade planning needs to rely on highly specialized dependency solvers, lest falling into pitfalls such as incompleteness-a combination of Package versions that satisfy dependency constraints does exist, but the Package Manager is unable to find it. In this paper we look back at proposals from dependency solving research dating back a few years. Specifically, we review the idea of treating dependency solving as a separate concern in Package Manager implementations, relying on generic dependency solvers based on tried and tested techniques such as SAT solving, PBO, MILP, etc. By conducting a census of dependency solving capabilities in state-of-the-art Package Managers we conclude that some proposals are starting to take off (e.g., SAT-based dependency solving) while-with few exceptions-others have not (e.g., out-sourcing dependency solving to reusable components). We reflect on why that has been the case and look at novel challenges for dependency solving that have emerged since.
-
using preferences to tame your Package Manager
2014Co-Authors: Pietro Abate, Fabrice Le Fessant, Roberto Di Cosmo, Louis Gesbert, Stefano ZacchiroliAbstract:Determining whether some components can be installed on a system is a complex problem: not only it is NP-complete in the worst case, but there can also be exponentially many solutions to it. Ordinary Package Managers use ad-hoc heuristics to solve this installation problem and choose a particular solution, making extremely difficult to change or sidestep these heuristics when the result is not the one we expect. When software repositories become complex enough, one gets vastly superior results by delegating dependency handling to a specialised solver, and use optimisation functions (or preferences) to control the class of solutions that are found. The opam Package Manager relies on the CUDF pivot format, which allows OCaml users that have a CUDF-compliant solver on their machine to reap the benefits of preferences-based dependency resolution. Thanks to the solver farm provided by Irill, these benefits are now extended to the OCaml community at large. In this talk we will present the preferences language and explain how to use it.
-
A modular Package Manager architecture
Information and Software Technology, 2013Co-Authors: Pietro Abate, Roberto Di Cosmo, Ralf Treinen, Stefano ZacchiroliAbstract:Context: The success of modern software distributions in the Free and Open Source world can be explained, among other factors, by the availability of a large collection of software Packages and the possibility to easily install and remove those components using state-of-the-art Package Managers. However, Package Managers are often built using a monolithic architecture and hard-wired and ad-hoc dependency solvers implementing some customized heuristics. Objective: We aim at laying the foundation for improving on existing Package Managers. Package Managers should be complete, that is find a solution whenever there exists one, and allow the user to specify complex criteria that define how to pick the best solution according to the user's preferences. Method: In this paper we propose a modular architecture relying on precise interface formalisms that allows the system administrator to choose from a variety of dependency solvers and backends. Results: We have built a working prototype-called MPM-following the design advocated in this paper, and we show how it largely outperforms a variety of current Package Managers. Conclusion: We argue that a modular architecture, allowing for delegating the task of constraint solving to external solvers, is the path that leads to the next generation of Package Managers that will deliver better results, offer more expressive preference languages, and be easily adaptable to new platforms.
-
mpm a modular Package Manager
Component-Based Software Engineering, 2011Co-Authors: Pietro Abate, Ralf Treinen, Roberto Dicosmo, Stefano ZacchiroliAbstract:Software distributions in the FOSS world rely on so-called Package Managers for the installation and removal of Packages on target machines. State-of-the-art Package Managers are monolithic in architecture, and each of them is hard-wired to an ad-hoc dependency solver implementing a customized heuristics. In this paper we propose a modular architecture allowing for pluggable dependency solvers and backends. We argue that this is the path that leads to the next generation of Package Managers that will deliver better results, accept more expressive input languages, and can be easily adaptable to new platforms. We present a working prototype---called MPM---which has been implemented following the design advocated in this paper.
-
CBSE - MPM: a modular Package Manager
Proceedings of the 14th international ACM Sigsoft symposium on Component based software engineering - CBSE '11, 2011Co-Authors: Pietro Abate, Ralf Treinen, Roberto Dicosmo, Stefano ZacchiroliAbstract:Software distributions in the FOSS world rely on so-called Package Managers for the installation and removal of Packages on target machines. State-of-the-art Package Managers are monolithic in architecture, and each of them is hard-wired to an ad-hoc dependency solver implementing a customized heuristics. In this paper we propose a modular architecture allowing for pluggable dependency solvers and backends. We argue that this is the path that leads to the next generation of Package Managers that will deliver better results, accept more expressive input languages, and can be easily adaptable to new platforms. We present a working prototype---called MPM---which has been implemented following the design advocated in this paper.
