Difference between revisions of "Fedcloud-tf:FederatedCloudsTaskForce"

From EGIWiki
Jump to: navigation, search
m
 
(66 intermediate revisions by 4 users not shown)
Line 1: Line 1:
{{TOC_right}}
+
<b>This page is obsolete, for information about the EGI Cloud Federation please refer to:
 +
[[Fedcloud-tf:Main| EGI Federated Cloud]]
 +
</b>
  
= Federating virtualised computing resources in EGI  =
+
{{Fedcloud-tf:Menu}} {{TOC_right}}
  
This blueprint document will be assembled and written by the Task Force members providing EGI Resource Centres with all information necessary to provision and configure computing and storage resources so that they can be easily and securely federated as part of the EGI production infrastructure.
 
  
The blueprint itself is planned to be developed at this sub-space: [[Fedcloud-tf:Blueprint EGI Federated Clouds]]
+
== Mandate ==
  
==== Related material and surveys  ====
+
EGI is a federation of national and domain specific resource infrastructure providers comprised of individual resource centres. Many of these resource centres have been experimenting with the deployment of virtualised management environments to improve the local delivery of services. Many of EGI’s current and new user communities would like to access the flexibility provided by virtualisation across the infrastructure on demand in a ‘cloud like’ environment. Federating these individual virtualised resources is a major priority for EGI that has started with the [http://go.egi.eu/uvw1 EGI User Virtualisation Workshop], and the drafting of the [http://go.egi.eu/435 EGI Cloud Integration Profile].
  
*'''Intentory survey''': Available at [[Fedcloud-tf:InventoryOfAvailableSoftware|Inventories on available implementation and actually used software]]
+
Objectives:  
*'''SARA HPC Cloud''': [https://documents.egi.eu/document/793 Presentation] at the BigGrid colloquium, 29 June 2011
 
*'''WNoDeS Requirements''': [https://documents.egi.eu/public/ShowDocument?docid=815 WNoDeS Requirements v1.0.0]
 
  
= Members  =
+
* write a [[Fedcloud-tf:Blueprint|blueprint document]] for EGI Resource Providers that wish to [[Fedcloud-tf:WorkGroups:_Federated_AAI|securely federate]] and share their virtualised environments as part of the EGI production infrastructure;
 +
* deploy a [[Fedcloud-tf:Testbed|test bed]] to evaluate the integration of virtualised resources within the existing EGI production infrastructure for [[Fedcloud-tf:WorkGroups:Scenario5|monitoring]], [[Fedcloud-tf:WorkGroups:Scenario4|accounting]] and [[Fedcloud-tf:WorkGroups:Scenario3|information services]];
 +
* investigate and catalogue the [[Fedcloud-tf:WorkGroups:_Outreach#Requirements|requirements]] for community facing services based on or deployed through virtualised resources;
 +
* provide [[Fedcloud-tf:Blueprint:Solutions_Intentory|feedback]] to relevant technology providers on their implementations and any changes needed for deployment into the production infrastructure;
 +
* identify and work with [[Fedcloud-tf:WorkGroups:_Outreach|user communities]] willing to be early adopters of the test bed infrastructure to help prioritise its future development;
 +
* identify [[Fedcloud-tf:Blueprint:Security_and_Policy|issues]] that need to be addressed by other areas of EGI (e.g. policy, operations, support &amp; dissemination).
  
{| cellspacing="0" cellpadding="5" style="border:1px solid black; text-align:left;" class="wikitable"
+
== Activities ==
|- style="background-color:darkgray;"
+
 
! style="border-bottom:1px solid black; text-align:left;" | Function
+
The Task Force mandate lasts eighteen months, from Sept 2011 to March 2013. The Task Force activities are organised in three, six-months long phases. During each phase, the Task Force evaluates a set of [[Fedcloud-tf:WorkGroups|scenarios]] that an EGI federation of clouds should support. The scenarios are chosen by collecting use cases and requirements among user communities, resource providers and technology providers that have already adopted cloud computing or are planning to do so in a near future.
! style="border-bottom:1px solid black; text-align:left;" | Affiliation
+
 
! style="border-bottom:1px solid black; text-align:left;" | Representative
+
One or more [[Fedcloud-tf:WorkGroups|work group]] is created inside the Task Force in order to evaluate each scenario. A leader is appointed for each work group and one or more collaborators are chosen among the Task Force members. The scenario evaluation performed by each work group is recorded in [[Fedcloud-tf:WorkGroups|workbenches]] and consists into:
! style="border-bottom:1px solid black; text-align:left;" | Deputy
+
* defining the set of capabilities that an EGI cloud infrastructure should have in order to support the given scenario;
 +
* evaluating whether and what standards are available to implement the required capabilities;
 +
* evaluating whether and what software solution is available to implement the required standards;
 +
* evaluating the level of support of such software solutions by the Resource Providers members of the Task Force;
 +
* evaluating the procedures to deploy the required software solutions into the infrastructure of the Resource Providers;
 +
* devising tests to be run on the cloud infrastructure of the Resource Providers in order to simulate the given scenario.
 +
 
 +
Once the scenario has been evaluated and, when possible, the required software and tests have been deployed in the Task Force [[Fedcloud-tf:Testbed|test bed]] federated cloud, the members of the work group proceed to write a section of the [[Fedcloud-tf:Blueprint|blueprint]] document. Altogether, the blueprint document describes the set of capabilities that define an EGI Cloud Federation. The blueprint focuses on the infrastructure layer of the federation and each work group is tasked with documenting at least one core capability. Each section of the blueprint is structured as follow.
 +
* '''Overview'''. The scenario and use cases from which the capability has been investigated are briefly introduced.
 +
* '''Definition of the capability'''. The functional properties, interfaces and available standards for implementation are described and analysed. A reasoned choice is made about what standards and implementations should be endorsed by an EGI cloud federation.
 +
* '''Deployment scenarios'''. The deployment infrastructure(s) and topology(ies) for the implementation of the capabilities are described and analysed.
 +
* '''Testing the capability'''. When possible, a description is given of the tests used to simulate the scenario requiring the capability under exam.
 +
* '''Security considerations'''. Security is a particularly sensitive topic in a federated infrastructure. Each capability has its own security evaluation with references to the EGI policy documents and security guidelines.
 +
* '''Solution inventory'''. A critical review of how the capability under exams is implemented – or not implemented - by the Virtual Machine Management platforms deployed by the Resource Providers participating to the Task Force.
 +
 
 +
The progress of the activity of each work group is available in the [[Fedcloud-tf:WorkGroups:Workbenches|workbenches summary]] section.
 +
 
 +
== Operations ==
 +
 
 +
The Task Force operates on its [mailto:fedcloud-tf@mailman.egi.eu mailing list] and on a [https://www.egi.eu/indico/categoryDisplay.py?categId=56 weekly conference call]. At the moment, our effort is organised in [[Fedcloud-tf:WorkGroups:Workbenches| work groups]] that any member of the Task Force is free to lead or to contribute to. Each member of Task Force can organise a meeting dedicated to further progress a specific workgroup activity. 
 +
 
 +
The Task Force meet every Tuesday at 11:00 CET in a [https://www.egi.eu/indico/categoryDisplay.py?categId=56 conference call]. Minutes of the meetins are [[Fedcloud-tf:Administrativa#Task_Force_Conference_Calls_Agendas_and_Minutes|publicly available]].
 +
<!--
 +
<div style="width:100%; height:100%; overflow:hidden;>
 +
<div style="width:56%; float:left; text-align:center;">
 +
High attendance
 +
<pBars ymin='0' ymax='100' angle='60' yunit='%' size='510x400' titlecolor='#000000' boxcolor='#000000' axiscolor='#000000' colors='#00AF33' marginx='15'>
 +
OeRC (UK NGI),100
 +
Chair,100
 +
EGI-InSPIRE SA2,100
 +
STFC (UK NGI),100
 +
STFC (e-Science),100
 +
EGI.eu,100
 +
Operations Officer,92
 +
TCD (NGI IE),90
 +
Technology Manager,84
 +
CESGA (IBERgrid),80
 +
Community Officer,76
 +
IGI,75
 +
CYFRONET (NGI PL),69
 +
CloudSigma,66
 +
INFN/CNAF,66
 +
EGI-InSPIRE JRA1,66
 +
FZ Julich,66
 +
</pBars>
 +
</div>
 +
<div style="width:23%; float:left; text-align:center;">
 +
Medium attendance
 +
<pBars ymin='0' ymax='100' angle='60' yunit='%'  size='210x400' titlecolor='#000000' boxcolor='#000000' axiscolor='#000000' colors='#FCD116' marginx='15'>
 +
CESNET (NGI CZ),61
 +
DANTE,57
 +
GWDG,54
 +
GRNET,50
 +
WeNMR,45
 +
KTH,41
 +
IN2P3 (NGI FR),40
 +
</pBars>
 +
</div>
 +
<div style="width:20%; float:left; text-align:center;">
 +
Low attendance
 +
<pBars ymin='0' ymax='100' angle='60' yunit='%' size='180x385' titlecolor='#000000' boxcolor='#000000' axiscolor='#000000' colors='#FF0000' marginx='15'>
 +
SARA (NGI NL),30
 +
StratusLab,23
 +
OGF DCIFed,18
 +
SIENA Project,9
 +
IPHC,0
 +
GRIF,0
 +
</pBars>
 +
<br>
 +
</div>
 +
</div>
 +
 
 +
Full details on meeting attendance are published in the [[Fedcloud-tf:Administrativa#Meeting_attendance| administrative]] section
 +
-->
 +
 
 +
== Roadmap ==
 +
 
 +
The Task Force roadmap is organised in three, six-months long phases. Every six months, the output of the Task Force activities are disseminated through the EGI.eu conferences and a new phase is started.
 +
 
 +
{| border="1" cellspacing="5" cellpadding="5" class="wikitable" style="border-collapse: collapse; border:1px solid black; text-align:center;"
 +
|- style="background-color: lightgray;"
 +
! colspan="3" | Phase 1. Setup: Sept 2011 - March 2012
 +
|- style="background-color: lightgray;"
 +
! Scenarios
 +
! Workbenches
 +
! Capabilities
 
|-
 
|-
| style="border-bottom:1px dotted silver;" | Chair
+
| 1
| style="border-bottom:1px dotted silver;" | Oxford University
+
| align="left" | [[Fedcloud-tf:WorkGroups:Scenario1|Running a pre-defined VM Image]]
| style="border-bottom:1px dotted silver;" | Matteo Turilli
+
| align="left" | [[Fedcloud-tf:Blueprint:Capabilities:VMManagement|VM Management]]
| style="border-bottom:1px dotted silver;" | Michel Drescher (see below)
 
 
|-
 
|-
| style="border-bottom:1px dotted silver;" | EGI.eu Management Observer
+
| 2
| style="border-bottom:1px dotted silver;" | EGI.eu
+
| align="left" | [[Fedcloud-tf:WorkGroups:Scenario2|Managing users' data and VMs]]
| style="border-bottom:1px dotted silver;" | Steven Newhouse
+
| align="left" | [[Fedcloud-tf:Blueprint:Capabilities:Data_Management|Data management]]
| style="border-bottom:1px dotted silver;" | n/a
 
 
|-
 
|-
| style="border-bottom:1px dotted silver;" | EGI.eu Operations Office
+
| 3
| style="border-bottom:1px dotted silver;" | EGI.eu
+
| align="left" | [[Fedcloud-tf:WorkGroups:Scenario3|Integrating information from multiple resource providers]]
| style="border-bottom:1px dotted silver;" | Tiziana Ferrari
+
| align="left" | [[Fedcloud-tf:Blueprint:Capabilities:InformationDiscovery|Information discovery]]
| style="border-bottom:1px dotted silver;" | Peter Solagna
 
 
|-
 
|-
| style="border-bottom:1px dotted silver;" | EGI.eu Chief Community Officer <br>EGI Outreach liaison
+
| 4
| style="border-bottom:1px dotted silver; vertical-align:top;" | EGI.eu
+
| align="left" | [[Fedcloud-tf:WorkGroups:Scenario4|Accounting across Resource Providers]]
| style="border-bottom:1px dotted silver; vertical-align:top;" | Steve Brewer
+
| align="left" | [[Fedcloud-tf:Blueprint:Capabilities:Accounting|Accounting]]
| style="border-bottom:1px dotted silver;" | Gergely Sipos
 
 
|-
 
|-
| style="border-bottom:1px solid black;" | EGI.eu Technology Manager
+
| 5
| style="border-bottom:1px solid black;" | EGI.eu
+
| align="left" | [[Fedcloud-tf:WorkGroups:Scenario5|Reliability/Availability of Resource Providers]]
| style="border-bottom:1px solid black;" | Michel Drescher
+
| align="left" | [[Fedcloud-tf:Blueprint:Capabilities:Monitoring|Monitoring]]
| style="border-bottom:1px solid black;" | n/a
 
|- style="background:lightgray;"
 
| style="border-bottom:1px solid black;" | User Community
 
| style="border-bottom:1px solid black;" | WeNMR
 
| style="border-bottom:1px solid black;" | Alexandre Bonvin
 
| style="border-bottom:1px solid black;" | Marco Verlato
 
 
|-
 
|-
| style="border-bottom:1px dotted silver;" | Resource Provider
+
| 6
| style="border-bottom:1px dotted silver;" | FZ Jülich
+
| align="left" | [[Fedcloud-tf:WorkGroups:Scenario6|VM/Resource state change notification]]
| style="border-bottom:1px dotted silver;" | Björn Hagemeier
+
| align="left" | [[Fedcloud-tf:Blueprint:Capabilities:Notification|Notification]]
| style="border-bottom:1px dotted silver;" | Shahbaz Memon
 
 
|-
 
|-
| style="border-bottom:1px dotted silver;" | Resource Provider
+
| 7
| style="border-bottom:1px dotted silver;" | CESNET (NGI_CZ)
+
| align="left" | [[Fedcloud-tf:WorkGroups:_Federated_AAI|AA across Resource Providers]]
| style="border-bottom:1px dotted silver;" | Miroslav Ruda
+
| align="left" | [[Fedcloud-tf:Blueprint:Capabilities:Authentication_and_Authorisation|Authentication and Authorisation]]
| style="border-bottom:1px dotted silver;" | Boris Parak
 
 
|-
 
|-
| style="border-bottom:1px dotted silver;" | Resource Provider
+
| 8
| style="border-bottom:1px dotted silver;" | CloudSigma
+
| align="left" | [[Fedcloud-tf:WorkGroups:VM_Marketplace|VM images across Resource Providers]]
| style="border-bottom:1px dotted silver;" | Micheal Higgins
+
| align="left" | [[Fedcloud-tf:Blueprint:Capabilities:VM_Sharing|VM sharing]]
| style="border-bottom:1px dotted silver;" | Robert Jenkins
+
|- style="background-color: lightgray;"
 +
! colspan="3" | Phase 2. Consolidation: April 2012 - Sept 2012
 
|-
 
|-
| style="border-bottom:1px dotted silver;" | Resource Provider
+
| colspan="3" align="left" |
| style="border-bottom:1px dotted silver;" | Cyfronet (NGI PL)
+
<ul>
| style="border-bottom:1px dotted silver;" | Tomasz Szepieniec
+
<li>Engagement of [[Fedcloud-tf:UserCommunities| user communities]].
| style="border-bottom:1px dotted silver;" | Marcin Radecki
+
<li>Implementing [https://indico.egi.eu/indico/getFile.py/access?contribId=91&sessionId=12&resId=0&materialId=slides&confId=1019| interoperability] among different cloud platforms (OpenNebula, OpenStack) federated into the [[Fedcloud-tf:Testbed| test bed]].
 +
<li>Supporting the first use case: [https://wiki.egi.eu/wiki/FedCloudBNCweb| BNCweb].
 +
<li>Draft of the [[Fedcloud-tf:Blueprint|Blueprint document]].
 +
<li>[https://indico.egi.eu/indico/contributionDisplay.py?sessionId=12&contribId=91&confId=1019| Live demo] at the [http://tf2012.egi.eu/| EGI Technical Forum 2012].
 +
</ul>
 +
|- style="background-color: lightgray;"
 +
! colspan="3" | Phase 3. Integration: Sept 2012 - Mar 2013
 
|-
 
|-
| style="border-bottom:1px dotted silver;" | Resource Provider
+
| colspan="3" align="left" |  
| style="border-bottom:1px dotted silver;" | GWDG
+
<ul>
| style="border-bottom:1px dotted silver;" | Ramin Yahyapour
+
<li>Set up of a User [[Fedcloud-tf:UserCommunities| Community Support Team (UCST)]] dedicated to the task force use cases.
| style="border-bottom:1px dotted silver;" | Philipp Wieder, Florian Feldhaus, Piotr Kasprzak<br>
+
<li>Integration of the federation test bed into the EGI infrastructure: [https://goc.egi.eu/portal/| GOCDB], [https://grid-monitoring.egi.eu/myegi| SAM], [http://accounting.egi.eu/egi.php| APEL].
|-
+
<li>Open the federation [[Fedcloud-tf:Testbed| test bed]] to early adopters.
| style="border-bottom:1px dotted silver;" | Resource Provider
+
<li>Publication of the [[Fedcloud-tf:Blueprint| Blueprint document]].
| style="border-bottom:1px dotted silver;" | Oxford University (NGI_UK)
+
<li>Demo and poster for each supported use case.
| style="border-bottom:1px dotted silver;" | David Wallom
+
<li>Tutorials and live demo of the federation test bed.
| style="border-bottom:1px dotted silver;" | Matteo Turilli
+
</ul>
|-
 
| style="border-bottom:1px dotted silver;" | Resource Provider
 
| style="border-bottom:1px dotted silver;" | SARA (NGI_NL)  
 
| style="border-bottom:1px dotted silver;" | Floris Sluiter
 
| style="border-bottom:1px dotted silver;" | Maurice Bouwhuis
 
|-
 
| style="border-bottom:1px dotted silver;" | Resource Provider
 
| style="border-bottom:1px dotted silver;" | TCD (NGI_IE)
 
| style="border-bottom:1px dotted silver;" | David O'Callahan
 
| style="border-bottom:1px dotted silver;" | Stuart Kenny
 
|-
 
| style="border-bottom:1px dotted silver;" | Resource Provider
 
| style="border-bottom:1px dotted silver;" | STFC (NGI_UK)
 
| style="border-bottom:1px dotted silver;" | Alison Packer
 
| style="border-bottom:1px dotted silver;" | John Gordon
 
|-
 
| style="border-bottom:1px dotted silver;" | Resource Provider
 
| style="border-bottom:1px dotted silver;" | IGI
 
| style="border-bottom:1px dotted silver;" | Giacinto Donvito
 
| style="border-bottom:1px dotted silver;" | Paolo Veronesi
 
|-
 
| style="border-bottom:1px solid black;" | Resource Provider,<br>Technology Provider
 
| style="border-bottom:1px solid black; vertical-align:top;" | KTH/Venus-C
 
| style="border-bottom:1px solid black; vertical-align:top;" | Zeeshan Ali Shah
 
| style="border-bottom:1px solid black; vertical-align:top;" | Ake Edlund
 
|- style="background:lightgray;"
 
| style="border-bottom:1px dotted black;" | Technology Provider
 
| style="border-bottom:1px dotted black;" | IGI/INFN
 
| style="border-bottom:1px dotted black;" | Elisabetta Ronchieri
 
| style="border-bottom:1px dotted black;" | Davide Salomoni
 
|- style="background:lightgray;"
 
| style="border-bottom:1px dotted black;" | Technology Provider
 
| style="border-bottom:1px dotted black;" | EGI-InSPIRE JRA1
 
| style="border-bottom:1px dotted black;" | Daniele Cesini
 
| style="border-bottom:1px dotted black;" | Emir Imamagic, Alvaro Simon
 
|- style="background:lightgray;"
 
| style="border-bottom:1px dotted black;" | Technology Provider
 
| style="border-bottom:1px dotted black;" | DANTE
 
| style="border-bottom:1px dotted black;" | Domenico Vicinanza
 
| style="border-bottom:1px dotted black;" | Richard Hughes-Jones
 
|- style="background:lightgray;"
 
| style="border-bottom:1px solid black;" | Technology Provider
 
| style="border-bottom:1px solid black;" | StratusLab
 
| style="border-bottom:1px solid black;" | Carl Loomis (interim)
 
| style="border-bottom:1px solid black;" | &nbsp;????
 
|-
 
| style="border-bottom:1px dotted silver;" | SIENA liaison
 
| style="border-bottom:1px dotted silver;" | SIENA
 
| style="border-bottom:1px dotted silver;" | Daniele Lezzi
 
| style="border-bottom:1px dotted silver;" | n/a
 
|-
 
| OGF Standards liaison
 
| OGF DCIFed chair
 
| Alexander Papaspyrou
 
| n/a
 
 
|}
 
|}
  
= Task Force constituting conference call  =
+
== Resources ==
  
The first conference call of the Task Force has taken place on 6 September 2011, with minutes available [https://www.egi.eu/indico/conferenceDisplay.py?confId=580 here].  
+
# [https://wiki.egi.eu/wiki/Fedcloud-tf Wiki]
 +
# [mailto:fedcloud-tf@mailman.egi.eu Mailing list] (incl. [https://mailman.egi.eu/mailman/private/fedcloud-tf/ Mailing list archive])
 +
# [https://www.egi.eu/indico/categoryDisplay.py?categId=56 Meeting planner]  
 +
# [https://oerc.basecamphq.com/projects/7732005-egi-federated-cloudstask-force/log Task Force Management &amp; Actions tracker]
  
== Poll on proposed time slots for weekly conference calls  ==
+
== References ==
  
On today's call we agreed to find as soon as possible a suitable slot for weekly conference calls. Please provide your suggestions on the dedicated [[Fedcloud-tf:ProposedCallSlots]] Wiki page until Wednesday 7 September 2011 16:00 CET.
+
#'''Task Force Mandate''': [https://documents.egi.eu/document/720 https://documents.egi.eu/document/720]  
 
+
#'''Task Force Roadmap''': [https://documents.egi.eu/secure/RetrieveFile?docid=803&version=1&filename=lyon_20092011_v3.pdf https://documents.egi.eu/secure/RetrieveFile?docid=803&version=1&filename=lyon_20092011_v3.pdf]
= References  =
 
 
 
=== Task Force infrastructure  ===
 
 
 
#'''Wiki:''' https://wiki.egi.eu/wiki/Fedcloud-tf:FederatedCloudsTaskForce
 
#'''Mailing list:''' [mailto:fedcloud-tf@mailman.egi.eu fedcloud-tf@mailman.egi.eu]
 
#'''Meeting planner:''' EGI Indico; [https://www.egi.eu/indico/categoryDisplay.py?categId=56 https://www.egi.eu/indico/categoryDisplay.py?categId=56]  
 
#'''Conference calls:''' On a weekly basis, every Tuesday at 11:00 CET, using EGI.eu's HiDef conferencing system (Call-in details will be made available on the respective Indico entries)
 
#'''Task Force Management &amp; Actions tracker''' OERC Basecamp, [https://oerc.basecamphq.com/projects/7732005-egi-federated-cloudstask-force/log https://oerc.basecamphq.com/projects/7732005-egi-federated-cloudstask-force/log]
 
 
 
=== Task Force mandate and other activities  ===
 
 
 
#'''Task Force Mandate''': Permanently available at [https://documents.egi.eu/document/720 https://documents.egi.eu/document/720]  
 
 
#'''Other EGI Virtualisation activities''': https://wiki.egi.eu/wiki/EGI_Virtualisation_Activities
 
#'''Other EGI Virtualisation activities''': https://wiki.egi.eu/wiki/EGI_Virtualisation_Activities
 
+
 
 
 
 
--[[User:Michel|Michel]] 16:20, 13 September 2011 (UTC)
 
  
 
[[Category:Fedcloud-tf]]
 
[[Category:Fedcloud-tf]]

Latest revision as of 17:32, 24 October 2016

This page is obsolete, for information about the EGI Cloud Federation please refer to: EGI Federated Cloud

Main Roadmap and Innovation Technology For Users For Resource Providers Media




Mandate

EGI is a federation of national and domain specific resource infrastructure providers comprised of individual resource centres. Many of these resource centres have been experimenting with the deployment of virtualised management environments to improve the local delivery of services. Many of EGI’s current and new user communities would like to access the flexibility provided by virtualisation across the infrastructure on demand in a ‘cloud like’ environment. Federating these individual virtualised resources is a major priority for EGI that has started with the EGI User Virtualisation Workshop, and the drafting of the EGI Cloud Integration Profile.

Objectives:

  • write a blueprint document for EGI Resource Providers that wish to securely federate and share their virtualised environments as part of the EGI production infrastructure;
  • deploy a test bed to evaluate the integration of virtualised resources within the existing EGI production infrastructure for monitoring, accounting and information services;
  • investigate and catalogue the requirements for community facing services based on or deployed through virtualised resources;
  • provide feedback to relevant technology providers on their implementations and any changes needed for deployment into the production infrastructure;
  • identify and work with user communities willing to be early adopters of the test bed infrastructure to help prioritise its future development;
  • identify issues that need to be addressed by other areas of EGI (e.g. policy, operations, support & dissemination).

Activities

The Task Force mandate lasts eighteen months, from Sept 2011 to March 2013. The Task Force activities are organised in three, six-months long phases. During each phase, the Task Force evaluates a set of scenarios that an EGI federation of clouds should support. The scenarios are chosen by collecting use cases and requirements among user communities, resource providers and technology providers that have already adopted cloud computing or are planning to do so in a near future.

One or more work group is created inside the Task Force in order to evaluate each scenario. A leader is appointed for each work group and one or more collaborators are chosen among the Task Force members. The scenario evaluation performed by each work group is recorded in workbenches and consists into:

  • defining the set of capabilities that an EGI cloud infrastructure should have in order to support the given scenario;
  • evaluating whether and what standards are available to implement the required capabilities;
  • evaluating whether and what software solution is available to implement the required standards;
  • evaluating the level of support of such software solutions by the Resource Providers members of the Task Force;
  • evaluating the procedures to deploy the required software solutions into the infrastructure of the Resource Providers;
  • devising tests to be run on the cloud infrastructure of the Resource Providers in order to simulate the given scenario.

Once the scenario has been evaluated and, when possible, the required software and tests have been deployed in the Task Force test bed federated cloud, the members of the work group proceed to write a section of the blueprint document. Altogether, the blueprint document describes the set of capabilities that define an EGI Cloud Federation. The blueprint focuses on the infrastructure layer of the federation and each work group is tasked with documenting at least one core capability. Each section of the blueprint is structured as follow.

  • Overview. The scenario and use cases from which the capability has been investigated are briefly introduced.
  • Definition of the capability. The functional properties, interfaces and available standards for implementation are described and analysed. A reasoned choice is made about what standards and implementations should be endorsed by an EGI cloud federation.
  • Deployment scenarios. The deployment infrastructure(s) and topology(ies) for the implementation of the capabilities are described and analysed.
  • Testing the capability. When possible, a description is given of the tests used to simulate the scenario requiring the capability under exam.
  • Security considerations. Security is a particularly sensitive topic in a federated infrastructure. Each capability has its own security evaluation with references to the EGI policy documents and security guidelines.
  • Solution inventory. A critical review of how the capability under exams is implemented – or not implemented - by the Virtual Machine Management platforms deployed by the Resource Providers participating to the Task Force.

The progress of the activity of each work group is available in the workbenches summary section.

Operations

The Task Force operates on its mailing list and on a weekly conference call. At the moment, our effort is organised in work groups that any member of the Task Force is free to lead or to contribute to. Each member of Task Force can organise a meeting dedicated to further progress a specific workgroup activity.

The Task Force meet every Tuesday at 11:00 CET in a conference call. Minutes of the meetins are publicly available.

Roadmap

The Task Force roadmap is organised in three, six-months long phases. Every six months, the output of the Task Force activities are disseminated through the EGI.eu conferences and a new phase is started.

Phase 1. Setup: Sept 2011 - March 2012
Scenarios Workbenches Capabilities
1 Running a pre-defined VM Image VM Management
2 Managing users' data and VMs Data management
3 Integrating information from multiple resource providers Information discovery
4 Accounting across Resource Providers Accounting
5 Reliability/Availability of Resource Providers Monitoring
6 VM/Resource state change notification Notification
7 AA across Resource Providers Authentication and Authorisation
8 VM images across Resource Providers VM sharing
Phase 2. Consolidation: April 2012 - Sept 2012
Phase 3. Integration: Sept 2012 - Mar 2013
  • Set up of a User Community Support Team (UCST) dedicated to the task force use cases.
  • Integration of the federation test bed into the EGI infrastructure: GOCDB, SAM, APEL.
  • Open the federation test bed to early adopters.
  • Publication of the Blueprint document.
  • Demo and poster for each supported use case.
  • Tutorials and live demo of the federation test bed.

Resources

  1. Wiki
  2. Mailing list (incl. Mailing list archive)
  3. Meeting planner
  4. Task Force Management & Actions tracker

References

  1. Task Force Mandate: https://documents.egi.eu/document/720
  2. Task Force Roadmap: https://documents.egi.eu/secure/RetrieveFile?docid=803&version=1&filename=lyon_20092011_v3.pdf
  3. Other EGI Virtualisation activities: https://wiki.egi.eu/wiki/EGI_Virtualisation_Activities