Speaker
Description
4. Conclusions / Future plans
We have experimented DeployWare on Grid'5000, the french experimental grid infrastructure with the automatic deployment of OpenCCM application servers on 1000 nodes of Grid'5000, on several clusters. Performance results have shown that, firstly, the execution time of the deployment process grows linearly with the number of nodes, secondly, the execution time decreases with the number of used DeployWare nodes. We plan to deploy more grid-specific middleware such as GridCCM or the Globus Toolkit.
URL for further information:
http://fdf.gforge.inria.fr/
Provide a set of generic keywords that define your contribution (e.g. Data Management, Workflows, High Energy Physics)
Software Deployment, Middleware, Distributed Applications, Grid'5000
3. Impact
DeployWare addresses the complexity, heterogeneity and scalability challenges of deployment on grids. The framework can be used by Grid Computing scientists coming from various disciplines (Physics, Earth Sciences, etc.), i.e. by non-computer science experts, to easily deploy and execute their applications on grids. DeployWare provides a metamodel that captures abstract concepts of deployment, a concrete syntax to describe software system, a virtual machine (named FDF, Fractal Deployment Framework) that interprets this description and executes the deployment process, and a graphical console allowing to manage, at runtime, the deployed system. DeployWare, implemented using the component-based approach, can deploy itself in order to address very large scale deployment (thousands of nodes).
Currently, DeployWare can deploy CORBA-based systems, SOA-based systems, JEE-based systems, Database systems, or grid-based services such as the OAR tool used in the Grid'5000 platform to reserve nodes
1. Short overview
DeployWare is a framework allowing to automatically deploy and manage heterogeneous and distributed software systems, including middleware, application servers and applications, on large scale infrastructures such as grids. It is independant of the paradigm/technology of the software that compose the system to deploy, automatically orchestrates the deployment process, dealing with software dependencies, and the heterogeneity of the targeted physical infrastructure (hardware, network, protocols).