Difference between revisions of "Cloud & VM status"
From GridPP Wiki
Line 191: | Line 191: | ||
|style="background-color:#CCFFCC"|X | |style="background-color:#CCFFCC"|X | ||
| | | | ||
− | | | + | |style="background-color:#CCFFCC"|X |
| | | | ||
Revision as of 11:32, 23 February 2016
This page will collect information from GridPP sites regarding their current deployment of job execution systems providing VMs, including Clouds. The information will help with wider considerations and strategy. The GridPP DIRAC SAM monitoring can be used to see the current state of many of these sites. There is a complementary page about batch system status.
For sites with multiple VM Provider / VM Lifecycle Manager implementations, please create multiple rows.
Site | VM Provider | VM Lifecycle Manager | Experiment/VO | APEL accounting | Notes | |||||
GridPP DIRAC | ALICE | ATLAS | CMS | LHCb | Others (specify) | |||||
Birmingham | Vac | Vac | X | X | ||||||
Bristol | ||||||||||
Brunel | OpenVZ | |||||||||
Cambridge |
| |||||||||
CERN | OpenStack | Vcycle | X | X | X | X | Vcycle at Manchester | |||
Durham |
| |||||||||
Edinburgh |
| |||||||||
Glasgow | ||||||||||
Imperial | OpenStack | CloudScheduler | X | |||||||
Imperial | OpenStack | Vcycle | X | X | X | X | Vcycle at Manchester | |||
Lancaster | OpenStack (offsite) | X | ||||||||
Lancaster | Vac | Vac | X | X | X | X | Downtime for upgrade | |||
Liverpool | Vac | Vac | X | X | X |
| ||||
Manchester | Vac | Vac | X | X | X | X | X | |||
Oxford | OpenStack | CloudScheduler | ||||||||
Oxford | Vac | Vac | X | X | X | X | X |
| ||
QMUL | CloudStack | Also looking at cloud storage
| ||||||||
RAL PPD | ||||||||||
RAL Tier-1 | HTCondor | Condor Vacuum | X | X | X | X | ||||
RAL Tier-1 | OpenNebula |
| ||||||||
RHUL |
| |||||||||
Sheffield |
| |||||||||
Sussex |
| |||||||||
UCL | Vac | Vac | X | X | X |