|
|
| (50 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| {{Fedcloud_Menu}} {{TOC_right}}
| | #REDIRECT [[Federated_Cloud_Architecture]] |
| | |
| {{Under_construction}}
| |
| | |
| = Introduction =
| |
| | |
| The current high throughput model of grid computing has proven to be extremely powerful for a small number of different communities. These communities have thrived in the current grid environment but the uptake of e-infrastructure by other communities has been limited. EGI has therefore strategically decided to investigate how it could broaden the uptake of its infrastructure to support other research communities and application design models, that would not only be able to take advantage of the existing functionality and investment already made in EGI’s Core Infrastructure, but also support different research communities and their applications on the current production infrastructure than it was previously able to.
| |
| | |
| The utilization of Virtualization and Infrastructure as a Service (IaaS) cloud computing was a clear candidate to enable this transformation. It was also clear that with a number of different open source technologies already in use across a number of different resource providers, that it would not be possible to mandate a single software stack. Instead, following on from a number of different activities already on-going in Europe including SIENA1, an approach that required the utilization of open standards where available and, where not, methods that have broad acceptance in the e-infrastructure community were essential.
| |
| | |
| This led to the current EGI Cloud Federation model, a model based on the needs of each community using the IaaS cloud as described below.
| |
| | |
| = Federation Model =
| |
| | |
| The EGI Federated Cloud is a set of clusters targeting global or specific user communities: a public federated cloud open for any researchers and various community clouds accessible to one or more selected Virtual Organizations. Every cluster follows the model shown in the figure:
| |
| | |
| [[Image:Federated_Cloud_Model.png|thumb|center|400px|Federated Cloud Model]]
| |
| | |
| The federation of IaaS Cloud resources in EGI is built upon the extensive autonomy of Resource Providers in terms of ownership of exposed resources. The federation model for distributed IaaS Cloud resources allows a lightweight aggregation of local Cloud resources into the EGI Cloud Infrastructure Platform (CLIP). At the heart of the federation are the locally deployed Cloud Management stacks. In compliance with the Cloud computing model, the EGI CLIP does not mandate deploying any particular or specific Cloud Management stack; it is the responsibility of the Resource Providers to investigate, identify and deploy the solution that fits best their individual needs for as long as the offered services implement the required interfaces and domain languages. These interfaces and domain languages, and the interoperability of their implementation with other solutions are the focus of the federation.
| |
| | |
| Every cluster of the federation, defines the actual level of integration with the EGI Federated Operations Services, the EGI marketplace and their Federated AAI architecture and technologies. The IaaS services of the cluster must be offered with interfaces that assure the interoperability within the community and whenever possible open standards should be used.
| |
| | |
| '''describe what's inside each box of the figure!'''
| |
| | |
| | |
| == Public Federated Cloud ==
| |
| | |
| The following figure depicts the concrete model for the public federated cloud, open to any research community, which is completely integrated with all EGI Core Services and EGI Marketplace, uses open standards (if available) for all the public APIs and uses the current AAI schema of EGI based on X.509 proxies with VOMS extensions.
| |
| | |
| [[Image:Public_Federated_Cloud_Model.png|thumb|center|800px|Public Federated Cloud Architecture]]
| |
| | |
| Resource providers in the public Federated Cloud must offer one or both of the following IaaS cloud capabilities by implementing these interfaces:
| |
| *IaaS VM management capability:
| |
| **[[Federated Cloud Architecture#VM_management_interface:_OCCI|VM management interface: OCCI]]
| |
| **[[Federated Cloud Architecture#VM_Image_management|VM Image management]]
| |
| *IaaS Data Management capability:
| |
| **[[Federated Cloud Architecture#Data_management_interface:_CDMI|Data management interface: CDMI]]
| |
| | |
| Moreover, to federate a resource provider in the public EGI Federated Cloud, it must integrate with the EGI core services and interfaces listed below:
| |
| *[[Federated Cloud Architecture#Virtual_Organisation_Management_.26_AAI:_VOMS|Virtual Organisation Management & AAI: VOMS]]
| |
| *[[Federated Cloud Architecture#Information_discovery:_BDII|Information discovery: BDII]]
| |
| *[[Federated Cloud Architecture#Monitoring:_SAM|Monitoring: SAM]]
| |
| *[[Federated Cloud Architecture#Accounting|Accounting]]
| |
| *[[Federated Cloud Architecture#Central_service_registry:_GOCDB|Central service registry: GOCDB]]
| |
| | |
| The EGI Federated Clouds Task gives Resource Providers a platform to share their implementation solutions for a commonly deployed specific Cloud Management stack (e.g. OpenNebula and OpenStack). The [[Federated Cloud resource providers support]] page is dedicated to the documentation of the steps necessary to integrate a local deployment of a given Cloud Management stack into the EGI Cloud federation. The table below summarizes the current integration level of the participating Cloud Management stacks in the federation:
| |
| | |
| {| class="wikitable"
| |
| |-
| |
| ! Cloud Mgmt. Stack
| |
| ! Fed. AAI
| |
| ! Info. Discovery
| |
| ! Monitoring
| |
| ! Accounting
| |
| ! VM Img. Mgmt.
| |
| ! OCCI
| |
| ! CDMI
| |
| |-
| |
| ! OpenStack
| |
| | Yes
| |
| | Yes
| |
| | Yes
| |
| | Yes
| |
| | Yes
| |
| | Yes
| |
| | In progress
| |
| |-
| |
| ! OpenNebula
| |
| | Yes
| |
| | Yes
| |
| | Yes
| |
| | Yes
| |
| | Yes
| |
| | Yes
| |
| | N/A
| |
| |-
| |
| ! Synnefo
| |
| | Yes
| |
| | Yes
| |
| | Yes
| |
| | Yes
| |
| | Yes
| |
| | Yes
| |
| | Yes
| |
| |}
| |
| | |
| | |
| == Community Federated Cloud ==
| |
| | |
| A community cloud is accessible to a selected group of users or Virtual Organizations. These clouds have a looser federation model hence the level of integration with the EGI services depends on the needs of the community it serves. Community clouds may also choose the interfaces to access the IaaS capabilities as long as the selected interfaces assure the interoperability within the federated resources. The standards used in the Public Federated Cloud are recommended if there are no requirements that prevent their usage.
| |
| | |
| Community clouds may profit the existing developments for the integration of Cloud Management stacks into the public federated cloud.
| |
| | |
| | |
| = Extending the EGI Federated Cloud =
| |
| | |
| '''TO REMOVE'''
| |
| | |
| An efficient and easy to use federated cloud needs more than just the infrastructure services. Convenient, user friendly interfaces for users, operators and developers are also a must. The EGI community is open to new projects which aim to improve the use and access to the EGI Federated Cloud work groups. If you are interested in participating or have questions please [mailto:support@egi.eu email] the User Community Support Team. Below are some example projects:
| |
| | |
| {| cellspacing="5" cellpadding="5" border="0" class="wikitable"
| |
| |-
| |
| | '''Project name'''
| |
| | '''Description'''
| |
| |-
| |
| | OCCI Web interface
| |
| | The start-up and management of virtual machine images in the EGI Federated Cloud is possible through the ‘Open Cloud Computing Interface’ API. While the OCCI API enables flexible management of images, it is a low level tool an its use requires an experienced programmer/user. This project aims to create and provide a high level, graphical front end interface for OCCI that would empower non-IT communities managing virtual machines on the EGI federated cloud. The interface can be a web browser plug-in, for example an extension of [https://indico.egi.eu/indico/conferenceDisplay.py?confId=1102 Hybridfox]) or can be a portal that is dedicated for serving users of the EGI Federated Cloud.
| |
| |-
| |
| | Grid middleware images
| |
| | Those who wish to operate a distributed computing environment within the EGI cloud would benefit from having grid middleware components available in the [http://appdb.egi.eu EGI Virtual Machine Marketplace]. While some of the gLite middleware components have images, many components are missing, and other middleware services (e.g. UNICORE, ARC) are not covered at all. This project aims to create, publish and keep up to date virtual machine images about the complete [http://repository.egi.eu/ EGI Unified Middleware Distribution] stack in the EGI Virtual Machine Marketplace.
| |
| |-
| |
| | BDII web interface
| |
| | BDII web interface Static information about the sites of the EGI Federated Cloud is stored in a ‘BDII Information System’. BDII is an LDAP based database optimised for frequent queries. The standard query interface of BDII is a command line tool. This project aims to provide a graphical interface that could be used to browse up-to-date information about the EGI Federated Cloud from its BDII information system. The interface could be a web portal, a [http://go.egi.eu/gadgets web gadget] or a web browser plug-in.
| |
| |}
| |
| | |
| [[Category:Federated_Cloud]] | |
The wiki is deprecated and due to be decommissioned by the end of September 2022.