Difference between revisions of "Federated Cloud Task Force"

From EGIWiki
Jump to: navigation, search
(Created page with "== Mandate == EGI is a federation of national and domain specific resource infrastructure providers comprised of individual resource centres. Many of these resource centres hav...")
 
 
(19 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 +
{{Fedcloud_Menu}}
 +
{{FedCloud_TF_Menu}} {{TOC_right}}
 +
 +
{| style="border:1px solid black; background-color:lightgrey; color: black; padding:5px; font-size:140%; width: 90%; margin: auto;"
 +
|-
 +
| style="padding-right: 15px; padding-left: 15px;" |
 +
| [[Image:Alert.png]] This page is '''obsolete'''. The main documentation for FedCloud [https://wiki.egi.eu/wiki/EGI_Federated_Cloud can be found here].
 +
|}
 +
 +
<br>
 +
 
== Mandate  ==
 
== Mandate  ==
  
Line 5: Line 16:
 
Objectives:  
 
Objectives:  
  
*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;  
+
*write a [[Federated_Cloud_Blueprint|blueprint document]] for EGI Resource Providers that wish to [[Federated_Cloud_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]];  
+
*deploy a [[Federated_Cloud_Operation|test bed]] to evaluate the integration of virtualised resources within the existing EGI production infrastructure for [[Federated_Cloud_Monitoring|monitoring]], [[Federated_Cloud_Accounting|accounting]] and [[Federated_Cloud_Information_Discovery|information services]];  
*investigate and catalogue the [[Fedcloud-tf:WorkGroups: Outreach#Requirements|requirements]] for community facing services based on or deployed through virtualised resources;  
+
*investigate and catalogue the 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;  
+
*provide 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 and work with [[Federated Cloud user support|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).
+
*identify issues that need to be addressed by other areas of EGI (e.g. policy, operations, support &amp; dissemination).
  
 
== Activities  ==
 
== Activities  ==
Line 38: Line 49:
 
== Operations  ==
 
== 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 operates on its [mailto:fedcloud-tf@mailman.egi.eu mailing list] and on a [https://indico.egi.eu/indico/categoryDisplay.py?categId=159 weekly conference call]. At the moment, our effort is organised in [[Federated_Cloud_Task_Force#FedCloud_work_groups|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]]. <!--
+
The Task Force meet every Tuesday at 11:00 CET in a [https://indico.egi.eu/indico/categoryDisplay.py?categId=159 conference call]. Minutes of the meetins are publicly available in the INDICO pages. <!--
 
<div style="width:100%; height:100%; overflow:hidden;>
 
<div style="width:100%; height:100%; overflow:hidden;>
 
<div style="width:56%; float:left; text-align:center;">
 
<div style="width:56%; float:left; text-align:center;">
Line 91: Line 102:
  
 
Full details on meeting attendance are published in the [[Fedcloud-tf:Administrativa#Meeting_attendance| administrative]] section
 
Full details on meeting attendance are published in the [[Fedcloud-tf:Administrativa#Meeting_attendance| administrative]] section
-->  
+
--><br>  
  
== Roadmap ==
+
= FedCloud work groups =
  
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.  
+
The FedCloud Task Force activities are split across work groups. A leader is elected for each work group and members of the Task Force are free to spend their effort in one or more groups. Each work group investigates one or more capabilities that are required by a federation of clouds. The work done is recorded in the group workbench and, eventually, translated into the Task Force blueprint.  
  
{| cellspacing="5" cellpadding="5" border="1" style="border-collapse: collapse; border:1px solid black; text-align:center;" class="wikitable"
+
With the development of the testbed and of the blueprint, new capabilities will be investigated and addressed. As a consequence, new work groups are added to the Task Force when required.
|- style="background-color: lightgray;"
+
 
! colspan="3" | Phase 1. Setup: Sept 2011 - March 2012
+
== Running  ==
|- style="background-color: lightgray;"
+
 
! Scenarios
+
*[[Federated_Cloud_VM_Management |VM Management]] - leader: Boris Parák (CESNET)
! Workbenches
+
*[[Federated_Cloud_Data_Management| Data Management]] - leader:&nbsp;<span><span>Christos</span> <span>Loverdos</span> (GRNET)</span>
! Capabilities
+
*[[Federated_Cloud_Information_Discovery| Information Discovery]] - leader:<span><span> Peter</span> <span>Solagna</span> (EGI.EU)</span>
|-
+
*[[Federated_Cloud_Accounting| Accounting]] - leader:&nbsp;<span><span>Stuart</span> <span>Pullinger</span> (STFC)</span>
| 1
+
*[[Federated_Cloud_Monitoring| Monitoring]] - leader:&nbsp;<span><span>Emir</span> <span>Imamagic</span> (SRCE)</span>
| align="left" | [[Fedcloud-tf:WorkGroups:Scenario1|Running a pre-defined VM Image]]  
+
*[[Federated_Cloud_Federated_AAI| federated AAI]] - leader: <span> <span>Paul</span> <span>Millar</span> (DESY)</span>
| align="left" | [[Fedcloud-tf:Blueprint:Capabilities:VMManagement|VM Management]]
+
*[[Federated_Cloud_VM_Image_Management| VM Image Management]] - leader:<span><span> Marios</span> <span>Chatziangelou</span> (IASA)</span>
|-
+
*[[Federated_Cloud_Brokering| Brokering]] - leader: (interim) Enol Fernandez (EGI.eu)  <br>
| 2
+
*[[Federated_Cloud_Security| Security]] - leader:Linda Cornwall (STFC)
| align="left" | [[Fedcloud-tf:WorkGroups:Scenario2|Managing users' data and VMs]]
+
*[[Federated_Cloud_IntraCloud_Networking|Intra Cloud networking]] - leader: Zdenek Sustr(CESNET)
| align="left" | [[Fedcloud-tf:Blueprint:Capabilities:Data Management|Data management]]
+
 
|-
+
== Closed ==
| 3
+
 
| align="left" | [[Fedcloud-tf:WorkGroups:Scenario3|Integrating information from multiple resource providers]]
+
*[https://wiki.egi.eu/wiki/Fedcloud-tf:WorkGroups:Scenario6 Notification]
| align="left" | [[Fedcloud-tf:Blueprint:Capabilities:InformationDiscovery|Information discovery]]
+
*[https://wiki.egi.eu/wiki/Fedcloud-tf:WorkGroups:Contextualisation Contextualisation]
|-
 
| 4
 
| align="left" | [[Fedcloud-tf:WorkGroups:Scenario4|Accounting across Resource Providers]]
 
| align="left" | [[Fedcloud-tf:Blueprint:Capabilities:Accounting|Accounting]]
 
|-
 
| 5
 
| align="left" | [[Fedcloud-tf:WorkGroups:Scenario5|Reliability/Availability of Resource Providers]]
 
| align="left" | [[Fedcloud-tf:Blueprint:Capabilities:Monitoring|Monitoring]]
 
|-
 
| 6
 
| align="left" | [[Fedcloud-tf:WorkGroups:Scenario6|VM/Resource state change notification]]
 
| align="left" | [[Fedcloud-tf:Blueprint:Capabilities:Notification|Notification]]
 
|-
 
| 7
 
| align="left" | [[Fedcloud-tf:WorkGroups: Federated AAI|AA across Resource Providers]]  
 
| align="left" | [[Fedcloud-tf:Blueprint:Capabilities:Authentication and Authorisation|Authentication and Authorisation]]
 
|-
 
| 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
 
|-
 
| align="left" colspan="3" |
 
*Engagement of [[Fedcloud-tf:UserCommunities|user communities]].
 
*Implementing [https://indico.egi.eu/indico/getFile.py/access?contribId=91&sessionId=12&resId=0&materialId=slides&confId=1019%7C interoperability] among different cloud platforms (OpenNebula, OpenStack) federated into the [[Fedcloud-tf:Testbed|test bed]].
 
*Supporting the first use case: [https://wiki.egi.eu/wiki/FedCloudBNCweb%7C BNCweb].
 
*Draft of the [[Fedcloud-tf:Blueprint|Blueprint document]].
 
*[https://indico.egi.eu/indico/contributionDisplay.py?sessionId=12&contribId=91&confId=1019%7C Live demo] at the [http://tf2012.egi.eu/%7C EGI Technical Forum 2012].
 
  
|- style="background-color: lightgray;"
+
= Join the EGI FedCloud Task Force  =
! colspan="3" | Phase 3. Integration: Sept 2012 - Mar 2013
 
|-
 
| align="left" colspan="3" |
 
*Set up of a User [[Fedcloud-tf:UserCommunities|Community Support Team (UCST)]] dedicated to the task force use cases.
 
*Integration of the federation test bed into the EGI infrastructure: [https://goc.egi.eu/portal/%7C GOCDB], [https://grid-monitoring.egi.eu/myegi%7C SAM], [http://accounting.egi.eu/egi.php%7C APEL].
 
*Open the federation [[Fedcloud-tf:Testbed|test bed]] to early adopters.
 
*Publication of the [[Fedcloud-tf:Blueprint|Blueprint document]].
 
*Demo and poster for each supported use case.
 
*Tutorials and live demo of the federation test bed.
 
  
|}
+
If you are interested in joining the EGI FedCloud Task Force, please send a mail to [mailto:fedcloud-tf@mailman.egi.eu fedcloud Mailing list] introducing yourself.
  
== Resources  ==
+
= Resources  =
  
#[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])  
 
#[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://indico.egi.eu/indico/categoryDisplay.py?categId=159 Meeting planner]
#[https://oerc.basecamphq.com/projects/7732005-egi-federated-cloudstask-force/log Task Force Management &amp; Actions tracker]
 
  
== References  ==
+
= References  =
  
 
#'''Task Force Mandate''': [https://documents.egi.eu/document/720 https://documents.egi.eu/document/720]  
 
#'''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&amp;version=1&amp;filename=lyon_20092011_v3.pdf]  
 
#'''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&amp;version=1&amp;filename=lyon_20092011_v3.pdf]  
 
#'''Other EGI Virtualisation activities''': https://wiki.egi.eu/wiki/EGI_Virtualisation_Activities
 
#'''Other EGI Virtualisation activities''': https://wiki.egi.eu/wiki/EGI_Virtualisation_Activities
 +
 +
<br>
 +
 +
[[Category:Federated_Cloud]]

Latest revision as of 11:22, 17 March 2016

Overview For users For resource providers Infrastructure status Site-specific configuration Architecture



Scenarios: Federated AAI Accounting VM Image Management Brokering IntraCloud Networking
Monitoring VM Management Data Management Information Discovery Security



Alert.png This page is obsolete. The main documentation for FedCloud can be found here.


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 in the INDICO pages.

FedCloud work groups

The FedCloud Task Force activities are split across work groups. A leader is elected for each work group and members of the Task Force are free to spend their effort in one or more groups. Each work group investigates one or more capabilities that are required by a federation of clouds. The work done is recorded in the group workbench and, eventually, translated into the Task Force blueprint.

With the development of the testbed and of the blueprint, new capabilities will be investigated and addressed. As a consequence, new work groups are added to the Task Force when required.

Running

Closed

Join the EGI FedCloud Task Force

If you are interested in joining the EGI FedCloud Task Force, please send a mail to fedcloud Mailing list introducing yourself.

Resources

  1. Mailing list (incl. Mailing list archive)
  2. Meeting planner

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