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 @ egi.eu.

Difference between revisions of "Fedcloud-tf:FederatedCloudsTaskForce"

From EGIWiki
Jump to navigation Jump to search
 
(39 intermediate revisions by 4 users not shown)
Line 1: Line 1:
<b>This page is obsolete, for information about the EGI Cloud Federation please refer to:
[[Fedcloud-tf:Main| EGI Federated Cloud]]
</b>
{{Fedcloud-tf:Menu}} {{TOC_right}}  
{{Fedcloud-tf:Menu}} {{TOC_right}}  


Line 8: Line 12:
Objectives:  
Objectives:  


* develop a blueprint document for EGI resource centres that wish to securely federate and share their virtualised environments as part of the production infrastructure;  
* 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;  
* define and prototype in conjunction with the relevant parties integrations with EGI’s existing production infrastructure for solutions for monitoring, accounting and advertising through the information services virtualised resources;  
* 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 requirements for future new community facing services for infrastructure deployment;  
* investigate and catalogue the [[Fedcloud-tf:WorkGroups:_Outreach#Requirements|requirements]] for community facing services based on or deployed through virtualised resources;  
* provide feedback to relevant technology providers (both within and external to the TCB) on their implementations and any changes needed for deployment into the production infrastructure;  
* 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 user communities willing to be early adopters of the resulting virtualised infrastructure to help prioritise its development;  
* 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 issues that need to be addressed by other areas of EGI (e.g. policy, operations, support &amp; dissemination).
* 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).
 
== 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 [[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.  


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:
* 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.


== Activities ==
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 activities take place 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 focused on six workgroups, one for each [Fedcloud-tf:WorkGroups:Workbenches scenario]. Each workgroup is led by a member of the Task Force. Each member of the Task Force is free to contribute to any workgroup or to suggest the creation of a new workgroup. Analogously, 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>


{| border="1" cellspacing="0" cellpadding="5" class="wikitable" style="border-collapse: collapse; border:1px solid black; text-align:center;"
Full details on meeting attendance are published in the [[Fedcloud-tf:Administrativa#Meeting_attendance| administrative]] section
|- style="background-color: lightgray;"
-->
! rowspan="2" | Members
! align="left" rowspan="2" style="border-left:1px dotted silver" |  
<span style="background:green">&nbsp;&nbsp;&nbsp;</span> = Attended<br> <span style="background:yellow">&nbsp;&nbsp;&nbsp;</span> = Apologies<br> <span style="background:red">&nbsp;&nbsp;&nbsp;</span> = Not attended<br> <span style="background:silver">&nbsp;&nbsp;&nbsp;</span> = Not a member
! colspan="4" | October 2011
! colspan="6" | November 2001
! colspan="4" | December 2011
|- style="background-color:lightgray;"
! <span class="plainlinks">[https://www.egi.eu/indico/conferenceDisplay.py?confId=586 04]</span>
! <span class="plainlinks">[https://www.egi.eu/indico/conferenceDisplay.py?confId=587 11]</span>
! <span class="plainlinks">[https://www.egi.eu/indico/conferenceDisplay.py?confId=588 18]</span>
! <span class="plainlinks">[https://www.egi.eu/indico/conferenceDisplay.py?confId=589 25]</span>
! <span class="plainlinks">[https://www.egi.eu/indico/conferenceDisplay.py?confId=590 01]</span>
! <span class="plainlinks">[https://www.egi.eu/indico/conferenceDisplay.py?confId=591 08]</span>
! <span class="plainlinks">[https://www.egi.eu/indico/conferenceDisplay.py?confId=592 15]</span>
! <span class="plainlinks">[https://www.egi.eu/indico/conferenceDisplay.py?confId=593 22]</span>
! <span class="plainlinks">[https://www.egi.eu/indico/conferenceDisplay.py?confId=684 24]</span>
! <span class="plainlinks">[https://www.egi.eu/indico/conferenceDisplay.py?confId=594 29]</span>
! <span class="plainlinks">[https://www.egi.eu/indico/conferenceDisplay.py?confId=595 06]</span>
! <span class="plainlinks">[https://www.egi.eu/indico/conferenceDisplay.py?confId=596 13]</span>
! <span class="plainlinks">[https://www.egi.eu/indico/conferenceDisplay.py?confId=597 20]</span>
! <span class="plainlinks">[https://www.egi.eu/indico/conferenceDisplay.py?confId=598 27]</span>
|-
| nowrap="nowrap" align="left" colspan="2" | <span title="Matteo Turilli">Chair</span>
| style="background:green" |
| style="background:green" |
| style="background:green" |
| style="background:green" |
| style="background:green" |
| style="background:green" |
| style="background:green" |
| style="background:green" |
|
|
|
|
|
|
|-
| nowrap="nowrap" align="left" colspan="2" | <span title="Michel Drescher">Technology Manager</span>
| style="background:green" |
| style="background:green" |
| style="background:yellow" |
| style="background:green" |
| style="background:green" |
| style="background:green" |
| style="background:green" |
| style="background:yellow" |
|
|
|
|
|
|
|-
| nowrap="nowrap" align="left" colspan="2" | <span title="Tiziana Ferrari; Peter Solagna">Operations Officer</span>
| style="background:green" |
| style="background:green" |
| style="background:green" |
| style="background:yellow" |
| style="background:green" |
| style="background:green" |
| style="background:green" |
| style="background:green" |
|
|
|
|
|
|
|-
| nowrap="nowrap" align="left" colspan="2" | <span title="Steve Brewer; Gergely Sipos">Community Officer</span>
| style="background:green" |
| style="background:green" |
| style="background:green" |
| style="background:green" |
| style="background:red" |
| style="background:yellow" |
| style="background:red" |
| style="background:red" |
|
|
|
|
|
|
|-
| nowrap="nowrap" align="left" colspan="2" | <span title="Ivan Diaz; Esteban Freire">CESGA (IBERgrid)</span>
| style="background:lightgray" |
| style="background:lightgray" |
| style="background:lightgray" |
| style="background:lightgray" |
| style="background:lightgray" |
| style="background:green" |
| style="background:green" |
| style="background:green" |
|
|
|
|
|
|
|-
| nowrap="nowrap" align="left" colspan="2" | <span title="Miroslav Ruda; Boris Parak">CESNET (NGI CZ)</span>
| style="background:green" |
| style="background:red" |
| style="background:green" |
| style="background:yellow" |
| style="background:green" |
| style="background:red" |
| style="background:green" |
| style="background:green" |
|
|
|
|
|
|
|-
| nowrap="nowrap" align="left" colspan="2" | <span title="Micheal Higgins; Robert Jenkins">CloudSigma</span>
| style="background:lightgray" |
| style="background:green" |
| style="background:green" |
| style="background:green" |
| style="background:green" |
| style="background:yellow" |
| style="background:green" |
| style="background:green" |
|
|
|
|
|
|
|-
| nowrap="nowrap" align="left" colspan="2" | <span title="Tomasz Szepieniec; Marcin Radecki">CYFRONET (NGI PL)</span>
| style="background:green" |
| style="background:yellow" |
| style="background:green" |
| style="background:green" |
| style="background:yellow" |
| style="background:yellow" |
| style="background:green" |
| style="background:green" |
|
|
|
|
|
|
|-
| nowrap="nowrap" align="left" colspan="2" | <span title="Domenico Vicinanza; Richard Hughes-Jones">DANTE</span>
| style="background:lightgray" |
| style="background:lightgray" |
| style="background:lightgray" |
| style="background:red" |
| style="background:yellow" |
| style="background:green" |
| style="background:yellow" |
| style="background:green" |
|
|
|
|
|
|
|-
| nowrap="nowrap" align="left" colspan="2" | <span title="Ramin Yahyapour; Philipp Wieder; Florian Feldhaus; Piotr Kasprzak">GWDG</span>
| style="background:red" |
| style="background:red" |
| style="background:red" |
| style="background:red" |
| style="background:green" |
| style="background:green" |
| style="background:green" |
| style="background:green" |
|
|
|
|
|
|
|-
| nowrap="nowrap" align="left" colspan="2" | <span title="Daniele Cesini; Emir Imamagic; Alvaro Simon">EGI-InSPIRE JRA1</span>
| style="background:green" |
| style="background:green" |
| style="background:green" |
| style="background:yellow" |
| style="background:green" |
| style="background:green" |
| style="background:green" |
| style="background:green" |
|
|
|
|
|
|
|-
| nowrap="nowrap" align="left" colspan="2" | <span title="Björn Hagemeier; Shahbaz Memon">FZ Jülich</span>
| style="background:lightgray" |
| style="background:green" |
| style="background:red" |
| style="background:green" |
| style="background:yellow" |
| style="background:green" |
| style="background:green" |
| style="background:yellow" |
|
|
|
|
|
|
|-
| nowrap="nowrap" align="left" colspan="2" | <span title="Michel Jouvin">GRIF</span>
| style="background:lightgray" |
| style="background:lightgray" |
| style="background:lightgray" |
| style="background:lightgray" |
| style="background:lightgray" |
| style="background:lightgray" |
| style="background:red" |
| style="background:red" |
|
|
|
|
|
|
|-
| nowrap="nowrap" align="left" colspan="2" | <span title="Panos Louridas; Vangelis Floros">GRNET</span>
| style="background:lightgray" |
| style="background:lightgray" |
| style="background:lightgray" |
| style="background:lightgray" |
| style="background:lightgray" |
| style="background:lightgray" |
| style="background:green" |
| style="background:red" |
|
|
|
|
|
|
|-
| nowrap="nowrap" align="left" colspan="2" | <span title="Giacinto Donvito; Paolo Veronesi">IGI</span>
| style="background:lightgray" |
| style="background:lightgray" |
| style="background:red" |
| style="background:green" |
| style="background:green" |
| style="background:green" |
| style="background:green" |
| style="background:green" |
|
|
|
|
|
|
|-
| nowrap="nowrap" align="left" colspan="2" | <span title="Helene Cordier; Gilles Mathie; Mattieu Puel">IN2P3 (NGI FR)</span>
| style="background:lightgray" |
| style="background:lightgray" |
| style="background:lightgray" |
| style="background:lightgray" |
| style="background:lightgray" |
| style="background:red" |
| style="background:red" |
| style="background:green" |
|
|
|
|
|
|
|-
| nowrap="nowrap" align="left" colspan="2" | <span title="Elisabetta Ronchieri; Davide Salomoni">INFN/CNAF</span>
| style="background:lightgray" |
| style="background:lightgray" |
| style="background:lightgray" |
| style="background:red" |
| style="background:red" |
| style="background:green" |
| style="background:green" |
| style="background:green" |
|
|
|
|
|
|
|-
| nowrap="nowrap" align="left" colspan="2" | <span title="Zeeshan Ali Shah; Ake Edlund">KTH</span>
| style="background:yellow" |
| style="background:green" |
| style="background:green" |
| style="background:green" |
| style="background:yellow" |
| style="background:red" |
| style="background:yellow" |
| style="background:green" |
|
|
|
|
|
|
|-
| nowrap="nowrap" align="left" colspan="2" | <span title="David Wallom; Matteo Turilli">OeRC (UK NGI)</span>
| style="background:green" |
| style="background:green" |
| style="background:green" |
| style="background:green" |
| style="background:green" |
| style="background:green" |
| style="background:green" |
| style="background:green" |
|
|
|
|
|
|
|-
| nowrap="nowrap" align="left" colspan="2" | <span title="Alexander Papaspyrou">OGF DCIFed</span>
| style="background:red" |
| style="background:green" |
| style="background:red" |
| style="background:green" |
| style="background:yellow" |
| style="background:yellow" |
| style="background:red" |
| style="background:red" |
|
|
|
|
|
|
|-
| nowrap="nowrap" align="left" colspan="2" | <span title="Floris Sluite; Maurice Bouwhuis; Machiel Jansen">SARA (NGI NL)</span>
| style="background:yellow" |
| style="background:green" |
| style="background:red" |
| style="background:red" |
| style="background:yellow" |
| style="background:red" |
| style="background:green" |
| style="background:red" |
|
|
|
|
|
|
|-
| nowrap="nowrap" align="left" colspan="2" | <span title="Daniele Lezzi">SIENA Project</span>
| style="background:green" |
| style="background:red" |
| style="background:red" |
| style="background:red" |
| style="background:red" |
| style="background:red" |
| style="background:red" |
| style="background:red" |
|
|
|
|
|
|
|-
| nowrap="nowrap" align="left" colspan="2" | <span title="Alison Packer; John Gordon">STFC (UK NGI)</span>
| style="background:lightgray" |
| style="background:lightgray" |
| style="background:lightgray" |
| style="background:green" |
| style="background:green" |
| style="background:green" |
| style="background:green" |
| style="background:green" |
|
|
|
|
|
|
|-
| nowrap="nowrap" align="left" colspan="2" | <span title="Carl Loomis">StratusLab</span>
| style="background:green" |
| style="background:green" |
| style="background:red" |
| style="background:yellow" |
| style="background:red" |
| style="background:green" |
| style="background:yellow" |
| style="background:red" |
|
|
|
|
|
|
|-
| nowrap="nowrap" align="left" colspan="2" | <span title="David O'Callahan; Stuart Kenny">TCD (NGI IE)</span>
| style="background:green" |
| style="background:green" |
| style="background:green" |
| style="background:red" |
| style="background:green" |
| style="background:green" |
| style="background:green" |
| style="background:green" |
|
|
|
|
|
|
|-
| nowrap="nowrap" align="left" colspan="2" | <span title="Alexandre Bonvin; Marco Verlato">WeNMR</span>
| style="background:yellow" |
| style="background:green" |
| style="background:green" |
| style="background:green" |
| style="background:yellow" |
| style="background:green" |
| style="background:yellow" |
| style="background:yellow" |
|
|
|
|
|
|
|}


== Cloud Resources Status ==
== Roadmap ==


The Task Force is developing a resource monitor solution for the clouds federation based on Nagios. Meanwhile, here a table showing the current status of the cloud resources made available by the resource providers that have joined the Task Force. This table is updated weekly by the resource providers.  
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="0" cellpadding="5" class="wikitable" style="border-collapse: collapse; border:1px solid black; text-align:center;"
{| border="1" cellspacing="5" cellpadding="5" class="wikitable" style="border-collapse: collapse; border:1px solid black; text-align:center;"
|- style="background-color: lightgray;"
|- style="background-color: lightgray;"
! Providers
! colspan="3" |  Phase 1. Setup: Sept 2011 - March 2012
! align="left" style="border-left:1px dotted silver" |  
|- style="background-color: lightgray;"
<span style="background:green">&nbsp;&nbsp;&nbsp;</span> = Available<br> <span style="background:red">&nbsp;&nbsp;&nbsp;</span> = Not available<br>
! Scenarios
! User registration
! Workbenches
! User access
! Capabilities
! VM availability
! Elastic IPs
! Object Storage
! Persistent Storage
|-
|-
| nowrap="nowrap" align="left" colspan="2" | [[Fedcloud-tf:Resources#cesga|CESGA (IBERgrid)]]
| 1
|  
| align="left" | [[Fedcloud-tf:WorkGroups:Scenario1|Running a pre-defined VM Image]]
|  
| align="left" | [[Fedcloud-tf:Blueprint:Capabilities:VMManagement|VM Management]]
|
|
|
|  
|-
|-
| nowrap="nowrap" align="left" colspan="2" | [[Fedcloud-tf:Resources#cesnet|CESNET (NGI CZ)]]
| 2
|  
| align="left" | [[Fedcloud-tf:WorkGroups:Scenario2|Managing users' data and VMs]]
|  
| align="left" | [[Fedcloud-tf:Blueprint:Capabilities:Data_Management|Data management]]
|
|
|
|  
|-
|-
| nowrap="nowrap" align="left" colspan="2" | [[Fedcloud-tf:Resources#cloudsigma|CloudSigma]]
| 3
|  
| align="left" | [[Fedcloud-tf:WorkGroups:Scenario3|Integrating information from multiple resource providers]]
|  
| align="left" | [[Fedcloud-tf:Blueprint:Capabilities:InformationDiscovery|Information discovery]]
|
|
|
|  
|-
|-
| nowrap="nowrap" align="left" colspan="2" | [[Fedcloud-tf:Resources#cyfronet|CYFRONET (NGI PL)]]
| 4
|  
| align="left" | [[Fedcloud-tf:WorkGroups:Scenario4|Accounting across Resource Providers]]
|  
| align="left" | [[Fedcloud-tf:Blueprint:Capabilities:Accounting|Accounting]]
|
|
|
|  
|-
|-
| nowrap="nowrap" align="left" colspan="2" | [[Fedcloud-tf:Resources#gwdg|GWDG]]  
| 5
|  
| align="left" | [[Fedcloud-tf:WorkGroups:Scenario5|Reliability/Availability of Resource Providers]]
|  
| align="left" | [[Fedcloud-tf:Blueprint:Capabilities:Monitoring|Monitoring]]
|
|
|
|  
|-
|-
| nowrap="nowrap" align="left" colspan="2" | [[Fedcloud-tf:Resources#fz|FZ Jülich]]
| 6
|  
| align="left" | [[Fedcloud-tf:WorkGroups:Scenario6|VM/Resource state change notification]]
|  
| align="left" | [[Fedcloud-tf:Blueprint:Capabilities:Notification|Notification]]
|
|
|
|  
|-
|-
| nowrap="nowrap" align="left" colspan="2" | [[Fedcloud-tf:Resources#igi|IGI]]
| 7
|  
| align="left" | [[Fedcloud-tf:WorkGroups:_Federated_AAI|AA across Resource Providers]]
|  
| align="left" | [[Fedcloud-tf:Blueprint:Capabilities:Authentication_and_Authorisation|Authentication and Authorisation]]
|
|
|
|  
|-
|-
| nowrap="nowrap" align="left" colspan="2" | [[Fedcloud-tf:Resources#in2p3|IN2P3 (NGI FR)]]
| 8
|  
| align="left" | [[Fedcloud-tf:WorkGroups:VM_Marketplace|VM images across Resource Providers]]
|  
| align="left" | [[Fedcloud-tf:Blueprint:Capabilities:VM_Sharing|VM sharing]]
|
|- style="background-color: lightgray;"
|  
! colspan="3" | Phase 2. Consolidation: April 2012 - Sept 2012
|  
|  
|-
|-
| nowrap="nowrap" align="left" colspan="2" | [[Fedcloud-tf:Resources#kth|KTH]]
| colspan="3" align="left" |  
|
<ul>
|
<li>Engagement of [[Fedcloud-tf:UserCommunities| user communities]].
|
<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>
| nowrap="nowrap" align="left" colspan="2" | [[Fedcloud-tf:Resources#oerc|OerC (UK NGI)]]
|- style="background-color: lightgray;"
|  
! colspan="3" | Phase 3. Integration: Sept 2012 - Mar 2013
|
|
|
|
|
|-
| nowrap="nowrap" align="left" colspan="2" | [[Fedcloud-tf:Resources#sara|SARA (NGI NL)]]
|  
|  
|
|
|
|
|-
| nowrap="nowrap" align="left" colspan="2" | [[Fedcloud-tf:Resources#tcd|TCD (NGI IE)]]
|
|
|
|
|
|
|-
|-
| colspan="3" align="left" |
<ul>
<li>Set up of a User [[Fedcloud-tf:UserCommunities| Community Support Team (UCST)]] dedicated to the task force use cases.
<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.
<li>Publication of the [[Fedcloud-tf:Blueprint| Blueprint document]].
<li>Demo and poster for each supported use case.
<li>Tutorials and live demo of the federation test bed.
</ul>
|}
|}


== Task Force Resources ==
== Resources ==
 
#'''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 at [https://www.egi.eu/indico/categoryDisplay.py?categId=56 https://www.egi.eu/indico/categoryDisplay.py?categId=56])
#'''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]


# [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]


== References ==
== References ==

Latest revision as of 16: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