|
|
| (28 intermediate revisions by 5 users not shown) |
| Line 2: |
Line 2: |
| [[Category:Federated_Cloud]] | | [[Category:Federated_Cloud]] |
|
| |
|
| == Overview == | | {| style="border:1px solid black; background-color:lightgrey; color: black; padding:5px; font-size:140%; width: 90%; margin: auto;" |
| | | |- |
| EGI Federated Cloud resource providers are institutions and companies that contribute to the FedCloud ''providing access to their cloud infrastructure via the Federation''.
| | | style="padding-right: 15px; padding-left: 15px;" | |
| | | | [[Image:Alert.png]] This page is '''obsoleted''' by the new providers documentation at https://egi-federated-cloud-integration.readthedocs.io/en/latest/ |
| Resource providers are free to use any '''Cloud Management Framework''' (OpenNebula, OpenStack, etc...) exposing interfaces compliant with the [[Federated_Cloud_Architecture|Federated Cloud Architecture]].
| | |} |
| | |
| At the moment this compliance is guaranteed by the following CMFs:
| |
| | |
| * OpenStack
| |
| * OpenNebula
| |
| * Synnefo
| |
| | |
| They all are able to exploit the following '''features''':
| |
| | |
| * Federated AAI
| |
| * Information Discovery
| |
| * Monitoring
| |
| * Accounting
| |
| * VM Image Management
| |
| * OCCI
| |
| | |
| If you have any comments on the content of these pages, please contact '''operations @ egi.eu'''.
| |
| | |
| == Join the EGI Federated Cloud as resource provider == | |
| | |
| Research institutions and companies are very welcome to join the EGI Federated Cloud as resource providers becoming '''Resource Centres (RC)''', and to get members of the Federated Cloud Task Force, contributing directly to the design, the creation and the implementation of the clouds federation.
| |
| | |
| The steps you will follow to join as RP are:
| |
| | |
| 1. first contact with EGI; you can '''contact the EGI operations team (operations at egi.eu)''', expressing interest in joining EGI as a RP, and providing few details about
| |
| | |
| * the ''projects'' you are involved in
| |
| * the ''user communities'' you want to support (a.k.a. ''Virtual Organisations'', VO)
| |
| * the ''technologies'' (Cloud Management Framework) you want to provide (see the [[Federated Cloud Architecture]] for more details)
| |
| * the ''services'' you would like to support (virtual machine management, storage...)
| |
| * details on the ''current status of your deployment'' (to be installed or already installed, already used or not, how it is used, who uses the services...)
| |
| | |
| '''EGI will reply to you providing proper guidance through all the following steps until the RP gets certified.''' | |
| | |
| 2. start the integration with the EGI infrastructure, with the help of the EGI operations team; to do this, the RP administrators will follow the two steps below, which can go in parallel.
| |
| | |
| * the [[MAN10|EGI Cloud RP Installation Manual]], installing and configuring the necessary connectors on top of the CMF, to get integrated into the EGI infrastructure
| |
| * the [[PROC09_Resource_Centre_Registration_and_Certification|Resource Centre Registration and Certification procedure]], providing the steps to register and certify the RP. In particular, the registration makes the EGI infrastructure aware of the new resources you offer, while the certification takes care of validating the registration itself and testing the behaviour of the services. In the context of the registration, you will become part of a Resource Infrastructure such as a National Grid Initiative (NGI), an EIRO, or a multi-country Resource Infrastructure.
| |
| | |
| == Questions and Answers ==
| |
| | |
| === Do I lose control on who can access my resources if I join federated cloud? ===
| |
| === How many components do I have to install? ===
| |
| === Which components of my private cloud will interact with the federated cloud components? ===
| |
| === How my daily operational activities will change? ===
| |
The wiki is deprecated and due to be decommissioned by the end of September 2022.