The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.
Difference between revisions of "Galaxy workflows with EC3"
Jump to navigation
Jump to search
| Line 7: | Line 7: | ||
== Objectives == | == Objectives == | ||
In this guide we will | In this guide we will show how to: | ||
* Deploy an elastic cluster of VMs in the RECAS-BARI resource of the EGI Federation | * Deploy an elastic cluster of VMs in the RECAS-BARI resource of the EGI Federation | ||
* Install a Galaxy web-based platform for data intensive research with a Torque Server as backend | * Install a Galaxy web-based platform for data intensive research with a Torque Server as backend | ||
* Install CLUE as elasticity manager | * Install CLUE as elasticity manager | ||
* Install custom Galaxy tool (booties2) | * Install custom Galaxy tool (booties2) | ||
Revision as of 16:09, 6 October 2016
| Overview | For users | For resource providers | Infrastructure status | Site-specific configuration | Architecture |
Galaxy workflows with EC3
Introduction
This guide is intended for researchers who want to use Galaxy, an open web-based platform for data-intensive research, in the cloud-based resources provided by the EGI Long Tail of Science Platform.
Objectives
In this guide we will show how to:
- Deploy an elastic cluster of VMs in the RECAS-BARI resource of the EGI Federation
- Install a Galaxy web-based platform for data intensive research with a Torque Server as backend
- Install CLUE as elasticity manager
- Install custom Galaxy tool (booties2)