|
|
| (293 intermediate revisions by 11 users not shown) |
| Line 1: |
Line 1: |
| {{Fedcloud-tf:Menu}} {{TOC_right}} | | {{Fedcloud_Menu}} {{TOC_right}} |
|
| |
|
| Users of the EGI Federated Cloud are scientists working in many fields, who can benefit of a flexible environment for running their experiment. Also, the EGI cloud is suitable to projects aiming to provide services platforms to the scientific community.
| | {{DeprecatedAndMovedTo|new_location=https://docs.egi.eu/users/cloud-compute/}} |
| <!--
| |
| == How to get access to the FedCloud? ==
| |
| | |
| Access to EGI FedCloud resources can be requested in email through the [mailto:ucst@EGI.eu EGI.eu User Community Support Team]. The team will work with you to develop a technical plan for your envisaged use case, identifying the sites, the number and type of resources that your use case requires from EGI. The team will then arrange access for you to these resources and with the site operators provides you further assistance during their use.
| |
| | |
| To join the EGI FedCloud, please send an email to [mailto:ucst@EGI.eu?subject=Get%20access%20to%20the%20EGI%20FedCloud ucst@EGI.eu] with the following information:
| |
| | |
| *Name
| |
| *Institute
| |
| *Email address
| |
| *One paragraph long description of the use case
| |
| *Envisaged timeline (is there a deadline to finish the setup?; for how long do you think you will need the setup to exist?)
| |
| *Estimated number and size of machines that you need from EGI
| |
| *Link to webpage, document or other online resource for further information
| |
| -->
| |
| | |
| === Concept ===
| |
| | |
| The EGI Federated Cloud is a seamless grid of academic private clouds and virtualised resources, built around open standards and focusing on the requirements of the scientific community. The result is a new type of research e-infrastructure, based on the mature federated operations services that make EGI a reliable resource for science. When using EGI Federated Cloud resources, researchers and research communities can count on:
| |
| * Total control over deployed applications
| |
| * Elastic resource consumption based on real need
| |
| * Immediately processed workloads – no more waiting time
| |
| * An extended e-Infrastructure across resource providers in Europe
| |
| * Service performance scaled with elastic resource consumption
| |
| * Single sign-on to cloud resources at multiple, independent sites
| |
| | |
| | |
| After [[Fedcloud-tf:Users#How_to_get_access_to_the_FedCloud.3F|obtaining access]] to one or more sites of the EGI federated cloud, the prospective user can setup and operate custom services, applications, simulations within the virtualized hosting environments of these sites. To do so the user will needs to:
| |
| | |
| #Look for operating system images already available into the [http://appdb.egi.eu EGI Applications Database] or create a virtual machine image that encapsulates an operating system, the scientific software and any optional component needed for this software to function.
| |
| #*Tip: Images from the [http://appdb.egi.eu EGI Applications Database] may be reusable, customisable for your use case.
| |
| #Instantiate the virtual machine image(s) on the EGI cloud. This is possible using a command-line client (rOCCI), high-level tools or directly implementing the ‘Open Cloud Computing Interface’ (OCCI) into your environment. Using the OCCI interface guarantees that your work will be compatible with any site that currently exists or will join the EGI Federated Cloud in the future.
| |
| #*Tip: Follow [[Fedcloud-tf:CLI_Environment|this guide]] to setup the rOCCI command line client.
| |
| #*Tip: Read in [[Fedcloud-tf:Users:ApplicationPortingHowTo|this guidance]] about various options of porting applications to the EGI Federated Cloud.
| |
| #*Tip: Use one of these [[Fedcloud-tf:Users:ApplicationPortingHowTo#High_level_brokering_tools_for_Federated_Cloud_users|high-level tools]] to instantiate VMs on cloud sites.
| |
| == Current FedCloud Users and Communities ==
| |
| | |
| <!-- [[File:fedclouduclogos.png|800px|thumb]] -->
| |
| [[File:fedclouduclogos.png|550px|center]]
| |
| | |
| <br>
| |
| More details of the FedCloud User Communities and their use cases is in the [[Fedcloud-tf:Users:Communities|FedCloud Users Communities]] page.
| |
| | |
| == How to use the FedCloud? ==
| |
| | |
| A brief description on how to use the FedCloud resources is described in the text below. More information can be found on the '''[[Fedcloud-tf:Users:FAQ|FedCloud FAQ page]]''' and the Guides and Tutorials listed in this page. Technical support is available via the [mailto:ucst@egi.eu EGI.eu UCST Team]
| |
| | |
| === Getting access === | |
| | |
| The typical user workflow on the EGI Federated Cloud looks like:
| |
| # [http://www.egi.eu/how-to/get_a_certificate.html Obtain a grid certificate] from a recognised CA
| |
| # Join a Virtual Organisation:
| |
| ## The [http://operations-portal.egi.eu/vo/search fedcloud.egi.eu Virtual Organisation] (VO) provides resources for application prototyping and validation. The VO can be used for up to 6 month for any new user. You can apply for membership [https://perun.metacentrum.cz/perun-registrar-cert/?vo=fedcloud.egi.eu here]
| |
| ## Several other VOs of EGI make resources available from the Federated Cloud. Find a suitable VO in the [http://operations-portal.egi.eu/vo/search Operations Portal]. (Search for Cloud as a middleware type.)
| |
| ## New VOs can be [http://operations-portal.egi.eu/vo/registrationWelcome setup in the Operations Portal], and invite sites from the infrastructure to support them.
| |
| # Reuse existing images from the Application Database Cloud Marketplace, or other repositories
| |
| ## Using the [[Fedcloud-tf:rOCCI-Client_Usage | command line client]] OR
| |
| ## Using one of the [[Fedcloud-tf:Users:ApplicationPortingHowTo#High_level_brokering_tools_for_Federated_Cloud_users|high level brokering tools]] that are interoperable with the Federated Cloud OR
| |
| # Prepare fully customised Virtual Appliances and deploy these to the sites:
| |
| ## Prepare Virtual Machine Images (VMIs) that encapsulate your application. See the [[Fedcloud-tf:Users:ApplicationPortingHowTo|application porting tutorial]] for tips.
| |
| ## Make the VMIs available online, for example in the [http://marketplace.egi.eu/metadata Stratuslab Marketplace]
| |
| ## Register the VMIs as Virtual Appliance in the [http://appdb.egi.eu EGI Applications Database]
| |
| ## Inform the Manager of your VO through Applications Database about the new Virtual Appliance. He/she will include your images in the VO-wide image list, so these will be deployed on the Federated Cloud sites of your VO.
| |
| ## Use the [[Fedcloud-tf:rOCCI-Client_Usage | command line client]], or some [[Fedcloud-tf:Users:ApplicationPortingHowTo#High_level_brokering_tools_for_Federated_Cloud_users | high level environment]], for example an [[Fedcloud-tf:Users:ApplicationPortingHowTo#4._Infrastructure_broker | Infrastructure broker]] or an [[Fedcloud-tf:Users:ApplicationPortingHowTo#5._Application_broker | Application Broker]] to instantiate and manage your Virtual Machine Images on cloud resources.
| |
| | |
| === Guides and tutorials ===
| |
| | |
| These guides and tutorials help you implement the above described typical user workflow and describe alternative ways of access, using high level appliaction broker and infrastructure broker solutions:
| |
| | |
| *[[Fedcloud-tf:Users:FAQ|FedCloud FAQ page]]
| |
| *[http://www.egi.eu/how-to/get_a_certificate.html How to get a grid certificate]
| |
| *[[Fedcloud-tf:CLI Environment|Setup the rOCCI Command Line Interface environment]]
| |
| *[[Fedcloud-tf:Users:ApplicationPortingHowTo|Porting your application/web service to the EGI Federated Cloud]]
| |
| *[[Fedcloud-tf:Users:StorageHowTo|EGI Federated Cloud Storage solutions]]
| |
| *[[Fedcloud-tf:Users:ApplicationPortingHowTo#High_level_brokering_tools_for_Federated_Cloud_users|High level user environments to interact with the EGI Federated Cloud]]
| |
| *[https://wiki.appdb.egi.eu/ How to use the Applications Database Cloud Marketplace]
| |
| *[[Fedcloud-tf:ResourceProviders#Fully_integrated_Resource_Providers|List and details about certified cloud resource providers]]
| |
| <!--
| |
| === Tools ===
| |
| | |
| This list provides pointers to client/management tools who may be useful for the . Some of this tools are referred also into the [[#Guides_and_tutorials]] and the [[Fedcloud-tf:Users:FAQ|FedCloud FAQ page]]:
| |
| | |
| *rOCCI (OCCI client/server, used to manage computing resources): [http://github.com/EGI-FCTF/rOCCI-cli/ http://github.com/EGI-FCTF/rOCCI-cli/]
| |
| -->
| |
| | |
| == Technical background ==
| |
| | |
| Cloud providers in the EGI Federated Cloud use hardware virtualization technologies to host software on their resources. The cloud management platforms that make this possible can [[Fedcloud-tf:Testbed#Resource_Providers_inventory|vary from site to site]], but they all enable the provisioning of virtualized computing, storage and networking resources, thus they empower scientific groups to setup and operate domain specific services, applications and simulations on these resources.
| |
| | |
| To deploy a custom application in the cloud one needs to first create one or more virtual machine (VM) image(s) encapsulating both a operating system and the specific scientific software that implements the domain specific calculation. The images then need to be instantiated on machines of the Federated Cloud. Every site of the EGI federated cloud exposes the same programming interfaces towards the user to setup virtual machines, therefore applications that are built for one site of the EGI Federated Cloud can run at any of the EGI Federated Cloud sites. The use of the cloud services are further simplified for scientific groups by a set of reusable, extendable virtual machine images from the [http://appdb.egi.eu EGI Applications Database], and by technical assistance and support provided by the [email:ucst@egi.eu User Community Support Team] of EGI.eu and the [http://go.egi.eu/dcc EGI Distributed Competence Centre].
| |
| | |
| === EGI Federated Cloud Sites ===
| |
| | |
| The EGI Federated Cloud sites are the resource providers. An overview of the resource providers, and their certification status (production status) is available [[Fedcloud-tf:ResourceProviders#Fully_integrated_Resource_Providers | here]]<br>.
| |
| | |
| === Interfaces and protocols ===
| |
| | |
| The EGI Federated Cloud is designed to satisfy scenarios defined by various scientific communities who expressed interest in using the system. The initial set of scenarios that the community collected has been distilled down to capabilities that the EGI Federated Cloud must provide to enable these community use cases. The capabilities were compared to state-of-the-art cloud computing technologies, standards, protocols and APIs to identify a technology stack which can help the National Grid Initiatives and research communities connect resources into a federated cloud. The Federated Cloud currently integrates the following main standard-based technological components:
| |
| | |
| {| cellspacing="5" cellpadding="5" border="0" class="wikitable"
| |
| |-
| |
| | '''Name of the technology'''
| |
| | '''Description'''
| |
| | '''What it’s used for in EGI?'''
| |
| | '''Technology homepage'''
| |
| |-
| |
| | OCCI: Open Cloud Computing Interface
| |
| | The Open Cloud Computing Interface comprises a set of open community-lead specifications delivered through the Open Grid Forum. OCCI is a Protocol and API for all kinds of management tasks. OCCI was originally initiated to create a remote management API for Infrastructure as a Service model based Services, allowing for the development of interoperable tools for common tasks including deployment, autonomic scaling and monitoring. It has since evolved into a flexible API with a strong focus on integration, portability, interoperability and innovation while still offering a high degree of extensibility.
| |
| | Virtual Machine management
| |
| | [http://occi-wg.org/ http://occi-wg.org/]
| |
| |-
| |
| <!--| CDMI: Cloud Data Management Interface
| |
| | The Cloud Data Management Interface defines the functional interface that applications will use to create, retrieve, update and delete data elements from the cloud. As part of this interface the client will be able to discover the capabilities of the cloud storage offering and use this interface to manage containers and the data that is placed in them.
| |
| | Data and meta-data management
| |
| | [http://www.snia.org/cdmi http://www.snia.org/cdmi]
| |
| |- -->
| |
| | GLUE Schema
| |
| | The GLUE Schema is a common way of publishing information about grid or cloud resources. GLUE is developed by consortium of grid projects, including the two largest projects of the EGI collaboration: EGI-InSPIRE and EMI. GLUE describes attributes of sites and services, computing elements and storage elements. Implementations of the Schema exist for a range of systems, the EGI Federated Cloud uses the LDAP based BDII implementation.
| |
| | Information system for cloud resources
| |
| | [http://www.ggf.org/gf/group_info/view.php?group=glue http://www.ggf.org/gf/group_info/view.php?group=glue</span>]
| |
| |-
| |
| | X509
| |
| | User authentication is a means of identifying the user and verifying that the user is allowed to access some restricted service, particularly the sites of the EGI Federated Cloud. Public-key cryptography is a cryptographic technique that enables users to securely communicate on an insecure public network, and reliably verify the identity of a user via digital signatures. The X.509 specification defines a standard for managing digital signatures on the Internet. X.509 specifies, amongst other things, standard formats for public key certificates, certificate revocation lists, attribute certificates, and a certification path validation algorithm.
| |
| | User authentication
| |
| | [http://en.wikipedia.org/wiki/X.509 http://en.wikipedia.org/wiki/X.509]
| |
| |}
| |
| | |
| <!--| CDMI: Cloud Data Management Interface
| |
| | The Cloud Data Management Interface defines the functional interface that applications will use to create, retrieve, update and delete data elements from the cloud. As part of this interface the client will be able to discover the capabilities of the cloud storage offering and use this interface to manage containers and the data that is placed in them.
| |
| | Data and meta-data management
| |
| | [http://www.snia.org/cdmi http://www.snia.org/cdmi]
| |
| |- -->
| |
| | |
| == User support ==
| |
| | |
| === Technical support ===
| |
| | |
| Users' technical support is provided via the [mailto:ucst@egi.eu EGI.eu UCST Team] email.
| |
| | |
| === Helpdesk ===
| |
| | |
| Technical problems and questions relating to the use of the EGI Federated Cloud can be reported and dealt with through the [https://ggus.eu/ EGI Helpdesk ticketing system]. '''Note: '''Please choose 'Federated cloud' in the 'Type of problem' field of the ticket submission form!
| |
| | |
| === Feedback and open issues ===
| |
| | |
| A list of open-issue and feedbacks reported by the FedCloud users is available at [[Fedcloud-tf:Users:Feedback and open issues|this page]].
| |
| | |
| <!--
| |
| == High Level Services ==
| |
| | |
| The EGI FedCloud, tough the FedCloud User Communities, provides a set of High Level Services to the community users. A non-exaustive list of this services is provided below:
| |
| | |
| *TBD
| |
| -->
| |
The wiki is deprecated and due to be decommissioned by the end of September 2022.