Alert.png 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 @

Difference between revisions of "Fedcloud-tf:ResourceProviders"

From EGIWiki
Jump to navigation Jump to search
Line 247: Line 247:
| style="border-bottom:1px dotted silver;" | Scheduled - Apr '14
| style="border-bottom:1px dotted silver;" | Scheduled - Apr '14
| style="border-bottom:1px dotted silver;" |  
| style="border-bottom:1px dotted silver;" |  
| style="border-bottom:1px dotted silver;" |  
| style="border-bottom:1px dotted silver;" | 200 Cores, 400 GB RAM, 20 TB storage at launch, with further posibility to dynamic scale-up to 5000 cores and 10 TB RAM (when needed)

Revision as of 10:58, 29 April 2014

Main Roadmap and Innovation Technology For Users For Resource Providers Media

EGI Federated Cloud Resource Providers

EGI Federated Cloud resource providers are institutions and companies that contribute to the FedCloud providing access to their cloud infrastructure via the Federation. Resource providers are free to use any Cloud Manafement Framework (OpenNebula, OpenStack, etc...), the only requirement is that the CMF exposes interfaces compliant to the FedCloud standards.

Join as a Resource Provider

Every institution and company is invited to join the EGI Federated Cloud. The members of the EGI Federated Cloud have also the opportunity to join the EGI Federated Cloud Task Force, contributing directly to the creation and implementation of the clouds federation.

If you want to join the EGI Federated Cloud, you can send en email to the EGI Federated Cloud Task Force, specifying the following information (fields with * are mandatory)

  • Name*
  • Institute*
  • Email address*
  • One paragraph long description of your organization
  • Envisaged timeline (is there a deadline to finish the setup? for how long do you wish to contribute to the EGI Federated project?)
  • Estimated number and size of machines that you may provide to EGI
  • Type of Cloud Management Framework you are using
  • Link to webpage, document or other online resource for further information

Current Resource Providers

Fully integrated Resource Providers

Sites that have a valid GOCDB entry, with all mandatory service types configured. Also either the Cloud compute service, or the Cloud storage service, or both must be listed properly. Monitoring via must be working, and probes for all mandatory and minimum Cloud services operational.

To get an impression of each site's availability and reliability, please have a look at MyEGI

Affiliation CC Main contact Deputies Host Site CMF Certification Resource Endpoints Committed Production Launch resources
100 Percent IT Ltd UK David Blundell 100IT OpenStack certified OCCI -
UNIZAR / BIFI ES Ruben Valles Jaime Ibar Yubero BIFI OpenStack certified OCCI - 360 cores with 370GB RAM ( in Xeon servers 2xhexacore 24GB RAM local HD 500GB)
BSC ES Daniele Lezzi Roger Rafanell BSC-Cloud Emotive CDMI -
FCTSG ES Alvaro Simon Esteban Freire CESGA OpenNebula certified OCCI - 296 Cores 592GB RAM (37 Xeon servers with 8 cores, 16GB de RAM and local HD 500GB).
CESNET CZ Miroslav Ruda Boris Parak CESNET-MetaCloud OpenNebula certified



240 cores with 960 GB of RAM and 44 TB
FZ Jülich DE Björn Hagemeier Shahbaz Memon FZJ OpenStack Planned



144 Cores

294 GB RAM

~18TB Object Storage

~15TB block storage

GWDG DE Piotr Kasprzak Ramin Yahyapour, Philipp Wieder GoeGrid OpenNebula certified



192 Core, 768 GB RAM, 40 TB storage
CSIC/IFCA ES Alvaro Lopez Garcia Enol Fernandez, Pablo Orviz IFCA-LCG2 OpenStack certified OCCI -

32 nodes x 8 vcpus x 16GB RAM

36 nodes x 24 vcpus x 48GM RAM

34 nodes x 32 vcpus x 128GB RAM

1 node x 80 vcpus x 1TB RAM

II SAS SK Viet Tran Martin Bobak IISAS-FedCloud OpenStack certified



96 cores, 3GB RAM per core, 16TB storage
INFN - Catania IT Roberto Barbera Giuseppe La Rocca, Diego Scardaci INFN-CATANIA-NEBULA OpenNebula certified OCCI - 120 cores and about 6 TB of storage
INFN-CATANIA-STACK OpenStack certified OCCI -
KTH SE Zeeshan Ali Shah Ake Edlund KTH-CLOUD OpenNebula certified OCCI - 192 Cores, 384 GB RAM with 6 TB of storage
INFN - Bari IT Marica Antonacci Giacinto Donvito, Stefano Nicotri, Vincenzo Spinoso PRISMA-INFN-BARI OpenStack certified OCCI - 300 Virtual CPU, 600GB of RAM and about 50TB of Storage.
MTA SZTAKI HU Sandor Acs Peter Kotcauer, Gabor Kecskemeti SZTAKI OpenNebula certified OCCI -

Integrating Resource Providers

Reporting period: 1 Feb 2014 - 28 Feb 2014

Sites that have a valid GOCDB entry, and at least one service type listed and monitored via

Affiliation CC Main Contact Deputies Host Site CMF Certification Resource Endpoints Comment
GRNET GR Kostas Koumantaros Athanasia Assiki HG-09-Okeanos-Cloud Synnefo Scheduled OCCI - 20 CPUS, 40 GB RAM and 400GB Storage
CRNS/IN2P3-CC FR Gilles MATHIEU‎ Mattieu Puel IN2P3-CC OpenStack OCCI -
Cyfronet (NGI PL) PL Tomasz Szepieniec Marcin Radecki, Jan Meizner OpenStack Scheduled - Apr '14 200 Cores, 400 GB RAM, 20 TB storage at launch, with further posibility to dynamic scale-up to 5000 cores and 10 TB RAM (when needed)

Interested Resource Providers

Affiliation CC Representative Deputies CMF Integration plans Comment
KISTI KR Soonwook Hwang Sangwan Kim, Taesang Huh, Jae-Hyuck Kwak OpenStack 64 cores with 256 GB RAM and 6TB HDD
IICT-BAS BG Emanouil Atanassov Todor Gurov OpenStack
INFN - Napoli IT Silvio Pardi OpenStack
INFN - CNAF IT Elisabetta Ronchieri Davide Salomoni, Andrea Cristofori OpenStack
INFN - Torino IT Andrea Guarise OpenStack
INFN - Padova IT Marco Verlato Eric Frizziero OpenStack
CETA-CIEMAT ES Guillermo Díaz Herrero, Miguel Ángel Díaz, Abel Paz OpenStack Havana Scheduled - Apr '14
CETA-CIEMAT ES Rubio Montero Rafael Mayo García, Manuel Aurelio Rodríguez Pascual OpenNebula
SURFsara NL Jhon Masschelein Maurice Bouwhuis, Machiel Jansen OpenNebula
CRNS/IPHC FR Jérôme Pansanel OpenStack
ISRGrid/IUCC IL Yossi Baruch
TUBITAK ULAKBIM TR Huseyin Cotuk Feyza Eryol, Onur Temizsoylu OpenStack Scheduled - Apr '14
DESY DE Patrick Furhmann Paul Millar dCache Storage only
STFC/RAL UK Ian Collier Frazer Barnsley, Alan Kyffin
STFC/RAL Harwell Science UK Jens Jensen Castor Cloud storage only
UKIM MK Boro Jakimovski
IFAE / PIC ES Victor Mendez
SAGrid ZA Bruce Becker
CSC FI Jura Tarus Luís Alves, Ulf Tigerstedt, Kalle Happonen OpenStack Planned - H1 '14 Status: Testing resource integration
SRCE HR Emir Imamagic Luko Gjenero OpenStack Planned - April 2014 Status: Deploying OpenStack cluster, investigating storage options
GridPP UK Adam Huffman OpenStack Hosted at Imperial College
CRNS/IN2P3-LAL FR Michel Jouvin Mohammed Araj StratusLab


More information about the Resource Providers belonging to the FedCloud Testbed are available here.

Cloud Management Frameworks

The federation of IaaS Cloud resources in EGI is built upon the extensive autonomy of Resource Providers in terms of ownership of exposed resources. The different cloud providers may have different Cloud Managemnt Frameworks (ex. OpenNebula, OpenStack, etc...), the federation implies only that the CMF exposes a set of common interfaces (ex. OCCI for VM management, CDMI for Data management, etc...)

More in-depth information about the EGI Federated Cloud architecture and technology is provided here.

Compatible CMFs

The table below provides a list of the most famous CMFs and the status of the support of the EGI Federated Cloud interfaces.

Cloud Mgmt. Fram. Fed. AAI Monitoring[1] Accounting Img. Mgmt. OCCI CDMI
OpenStack Yes Yes Yes Yes Yes Yes
OpenNebula Yes Yes Yes Yes Yes Yes
StratusLab Yes Yes Yes - Yes[2] -
WNoDeS Yes Yes Yes - - -
Synnefo Yes Yes InProgress InProgress Yes Yes


Guides for deployment of the FedCloud interfaces for the most used Cloud Management Frameworks are reported below:


  1. Monitoring happens passive, i.e. no active integration from the side of Cloud Management Frameworks necessary.
  2. StratusLab’s OCCI support is based on OpenNebula. Since StratusLab will discontinue its integration with OpenNebula (see below), the future of StratusLab OCCI interface is unknown at this point in time.