Difference between revisions of "Fedcloud-tf:FederatedCloudsTaskForce"
|Line 155:||Line 155:|
== Quarterly report ==
== Quarterly report ==
Starting from Quarter 9, the Federated Cloud activities can be accounted under TSA2.6. Therefore there is the need to produce a contribution to the quarterly report QR9, please '''all workbench leaders''' and '''all resource providers who are willing to account effort on TSA2.6''' should fill the table in the following wiki page: [[
Starting from Quarter 9, the Federated Cloud activities can be accounted under TSA2.6. Therefore there is the need to produce a contribution to the quarterly report QR9, please '''all workbench leaders''' and '''all resource providers who are willing to account effort on TSA2.6''' should fill the table in the following wiki page: []
== References ==
== References ==
Revision as of 12:50, 1 August 2012
|Main||Roadmap and Innovation||Technology||For Users||For Resource Providers||Media|
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.
- 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).
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.
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 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: Sept 2011 - March 2012|
|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|
|Phase 2: April 2012 - Sept 2012|
|6||VM/Resource state change notification||Notification|
|7||AA across Resource Providers||Authentication and Authorisation|
|8||VM images across Resource Providers||VM sharing|
- Mailing list (incl. Mailing list archive)
- Meeting planner
- HiDef conferencing system
- Task Force Management & Actions tracker
Starting from Quarter 9, the Federated Cloud activities can be accounted under TSA2.6. Therefore there is the need to produce a contribution to the quarterly report QR9, please all workbench leaders and all resource providers who are willing to account effort on TSA2.6 should fill the table in the following wiki page: FedClouds QR9
- Task Force Mandate: https://documents.egi.eu/document/720
- Task Force Roadmap: https://documents.egi.eu/secure/RetrieveFile?docid=803&version=1&filename=lyon_20092011_v3.pdf
- Other EGI Virtualisation activities: https://wiki.egi.eu/wiki/EGI_Virtualisation_Activities