The Federated Clouds Task Force aims to integrate virtualized resources into EGI's production infrastructure through standards-based interfaces. Over 18 months, workgroups will investigate capabilities for federated cloud computing and produce a blueprint and testbed. The Task Force includes diverse stakeholders from resource providers, technology providers, and user communities. Initial workgroups will focus on interfaces for VM management, data management, accounting, monitoring, and federated identity and access management. The first cycle ends in March 2012 with a workshop and demonstration.

1. Federated Clouds Task Force
Cloud PlugFest
Matteo Turilli
Chair – Federated Clouds Task Force
matteo.turilli@oerc.ox.ac.uk
1

2. Outline
• Objectives
• Outputs
• Guiding principles
• Mandate and Operations
• TF Members
• Workgroups
• Federation Testbed Interfaces
• Blueprint
• Conclusions

3. Objectives
• Integration: integration of virtualised resources with EGI’s production
infrastructure – e.g. monitoring, accounting and resource publishing.
• Technical feedback: feedback to technology providers on any changes
needed for the deployment of their implementations.
• Early adopters: identify and work with user communities willing to be early
adopters of the resulting virtualised infrastructure.
• Recommendations: identify issues that need to be addressed by other areas
of EGI – e.g. policies, operations, support and dissemination.

4. Outputs
• Blueprint document: advice/full documentation to resource providers/users on
how to engage with the federated virtualised environment. This will be a living
document on the EGI Wiki.
• Testbed: implement interfaces and services for a federated cloud on the basis
of the Task Force blueprint and the available standards and technologies.
• Engagement: identification of resources centres and user communities willing
to commit actively to this Task Force.
• Dissemination: periodic “success stories” through dissemination channels.

5. Guiding Principles
• Standards and validation: the goal of the TF effort is to produce a validation
procedure for clouds federation based on the emerging standards in Cloud
Computing. E.g. OVF, OCCI, CDMI, etc.
• Resource typologies: EGI offers already a number of validated services to the
community. Virtualisation and Cloud Computing should be considered just as
another type of resource to integrate into the existing production infrastructure.
• Heterogeneous implementation: there should be no specific mandate on the
implementation of virtualisation/cloud technology but only the validation of a
prescribed set of functionalities, standards and interfaces.
• Provider agnosticism: no distinction should be made on the nature of each
provider. Private, public, research and business oriented should make no
difference once the federation criteria have been established and agreed upon.

6. Mandate and Organisation
• Mandate: 18 months, September 2011 – March 2013.
• Activities: divided into 3 blocks of 6 months each. Goals, deadlines and
workgroups leaders are set up at the beginning of each block.
• Workgroups:
– working units within the Task Force.
– Investigate a specified set of capabilities for a federation of clouds.
– Have leaders and collaborators.
• Workbenches: sections of the TF Wiki site collecting and documenting the
activities of each workgroup.
• Meetings: weekly conference call. F2F every 3 months.

7. Task Force Members
SARA TUD
Utrecht KTH
EGI.eu
DANTE GWDG
TCD FZJ
STFC CESNET
OerC Community Driven Cyfronet
• 58 individuals.
SixSq Masaryk
• 23 institutions.
CNRS • 13 countries. LMU
FCTSG SRCE
IFAE INFN
GRNET
BSC

8. Task Force Members
SARA TUD
Utrecht KTH
EGI.eu
DANTE GWDG
TCD FZJ
STFC CESNET
OerC Diverse Stakeholders Cyfronet
• 15 Resource Providers.
SixSq Masaryk
• 7 Technology Providers.
CNRS • 4 User Communities. LMU
FCTSG • 3 Liaisons. SRCE
IFAE INFN
GRNET
BSC

9. Task Force Members
SARA TUD
Utrecht KTH
EGI.eu
DANTE GWDG
TCD FZJ
STFC CESNET
OerC Multiple Technologies Cyfronet
• 7 OpenNebula.
SixSq Masaryk
• 3 StratusLab.
CNRS • 3 OpenStack. LMU
FCTSG • 1 Okeanos. SRCE
• 1 WNoDeS.
IFAE INFN
GRNET
BSC

10. Workgroups – Sep 2011/March 2012
VM Management . OCCI interfaces for multiple IaaS
Data Management . CDMI interfaces for multiple IaaS
. OVF
Information Systems . Extended GLUE2 schema
. LDAP server
Accounting . Cloud Usage Record (UR) schema
. UR server
. UR client for each IaaS
Monitoring . Nagios with cloud probes
Notification . ActiveMQ?
Federated AAI . X509 certificates
. Support for Virtual Organisations (Vos)
Marketplace . StratusLab

11. Federation Testbed Interfaces
VM Mngmt Data Information
OCCI 1.1 CDMI 1.0 GLUE 2.0
OVF 1.1.0 (LDAP)
Clients AAI Resource Providers
X509 OpenNebula, OpenStack, WNoDeS, …
Brokers (SAML & XACML)
Monitoring Accounting Notification
Nagios OGF UR Various
UR+ & StAR
EGI Wide Area Message Bus
ActiveMQ

12. Blueprint
https://wiki.egi.eu/wiki/Fedcloud-tf:Blueprint

13. Conclusions
EGI Community Forum: Munich 26-30 March 2012
• End of the first TF cycle.
• Workshop.
• Demo.
TF cycle #2
• Brokering.
• EGI AAI integration.
• Migration.
Task Force resources
• Mailing List: fedcloud-tf@mailman.egi.eu
• Wiki site: http://go.egi.eu/tf-fedclouds
• Indico site: https://www.egi.eu/indico/categoryDisplay.py?categId=56

14. Thank you
Matteo Turilli
Chair – Federated Clouds Task Force
matteo.turilli@oerc.ox.ac.uk
14