Federated Cloud user support
|EGI Federated Cloud||Technology||For Users||For Resource Providers||Roadmap and Innovation||Task Force||Operation|
Technical support is available via the EGI.eu Support Team
Users of the EGI Federated Cloud are scientists working in many fields, who can benefit of a flexible environment for running their workloads. Also, the EGI cloud is suitable to projects aiming to provide services and platforms to the scientific community.
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 needs
- 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 at multiple, independent providers
After obtaining access to one or more sites of the EGI federated cloud, the prospective user can setup and operate custom services, applications and simulations within the virtualized hosting environments of these sites.
- Users select Virtual Appliances (a virtual machine image that encapsulates an operating system and optionally a set of applications) from the EGI Applications Database. Technical developers may also create their own images with any operating system of choice, the scientific software and any optional component needed for the software to function.
- Tip: Images from the EGI Applications Database may be reusable, customisable for your use case.
- Instantiate the Virtual Appliance(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 application will be compatible with any site that currently exists or will join the EGI Federated Cloud in the future.
- Users can use block storage (that can be attached as a disk to running Virtual Machines) or object-based storage that can be accessed from anywhere with the CDMI interface.
- Tip: Read the storage how-to for more information on the storage services of FedCloud (PREPRODUCTION)
- Sites support the Virtual Organizations (VOs) and automatically download the Virtual Appliance lists endorsed by the VO managers.
The EGI Federated Cloud considerably widens the usage models supported by EGI. Now, web services and interactive applications can be easily integrated in the infrastructure, the computing environments can be finely tuned to satisfy user’s needs in term of software (OSs and software packages) and hardware (number of cores, amount of RAM, etc.) and, many solutions are available to store, update and access big amount of data. These new opportunities offered by EGI hugely extended the potential user base of the infrastructure opening the doors to new research communities with minimal or none knowledge of the EGI ecosystem.
We classified the usage models enabled by the EGI Fededated Cloud as follows:
- Service hosting: the EGI Federated Cloud can be used to hosts any IT service as web servers, databases, etc. Cloud features, as elasticity, can help users to provide better performance and reliable services.
- Compute and data intensive: applications needing considerable amount of resources in term of computation and/or memory and/or intensive I/O. Ad-hoc computing environments can be created in the FedCloud sites also to satisfy very hard HW resource requirements.
- Datasets repository: the EGI Federated Cloud can be used to store and manage large datasets exploiting the big amount of disk storage available in the Federation.
- Disposable and testing environments: environments for training or testing new developments.
Current FedCloud Users and Communities
More details of the FedCloud User Communities and their use cases is in the 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 FAQ page and the Guides and Tutorials listed in this page.
The typical user workflow on the EGI Federated Cloud looks like:
- Obtain a grid certificate from a recognised CA (if you don't own one already)
- Join fedcloud.egi.eu Virtual Organisation. This VO provides resources for application prototyping and validation. It can be used for up to 6 month for any new user.
- Select existing images from the Application Database Cloud Marketplace and start them by:
Once the 6-month testing period of fedcloud.egi.eu membership expires, you will need to move into a production VO:
- Several other VOs of EGI make resources available from the Federated Cloud. Find a suitable VO in the Operations Portal. (Search for Cloud as a middleware type.)
- Existing grid production VOs can be extended by VO manager to cloud by declaring cloud resources in VO ID card (in Operations Portal) and requesting via GGUS (assign to Perun Support Unit) Perun support.
- If no existing VO suits your case, a new VO can be created. Please follow this procedure. You can invite sites from the infrastructure to support them.
Customized Virtual Appliances
You can prepare fully customised Virtual Appliances and deploy them to the sites:
- Prepare Virtual Machine Images (VMIs) that encapsulate your application. See the application porting tutorial for tips.
- Make the VMIs available online, for example in the EGI Appliance Repository
- Register the VMIs as Virtual Appliance in the EGI Applications Database (for howto please click here)
- Once your registered set of VMIs, bundled under a vAppliance version, have been published (see howto here),inform the Manager of your VO through Applications Database about the new Virtual Appliance (see howto here). 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.
Guides and tutorials
These guides and tutorials help you to implement the above described typical user workflow and describe alternative ways of accessing, using high level application broker and infrastructure broker solutions:
- FedCloud FAQ page
- How to get a certificate (to access Federated Cloud resources)
- Setup the rOCCI Command Line Interface environment
- Porting your application/web service to the EGI Federated Cloud
- PRE-PRODUCTION: EGI Federated Cloud Storage solutions
- High level user environments to interact with the EGI Federated Cloud
- How to use the Applications Database Cloud Marketplace
- List and details about certified cloud resource providers
- Current status of Federated Cloud resources (NAGIOS test results): https://cloudmon.egi.eu/nagios/cgi-bin/status.cgi?host=all&sorttype=2&sortoption=2
- Current status of OpenStack interfaces in the EGI federated cloud: https://cloudmon.egi.eu/nagios/cgi-bin/status.cgi?servicegroup=SERVICE_org.openstack.nova&style=overview
- Explanation of NAGIOS tests performed by EGI on cloud resources: https://wiki.egi.eu/wiki/Cloud_SAM_tests
- How to write a new NAGIOS test for the EGI monitor: http://argoeu.github.io/samdoc/confluence/display/SAMDOC/Developer%27s%20Guide.html
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 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.
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 here.
Interfaces and protocols
The EGI Federated Cloud is designed to satisfy scenarios defined by various scientific communities. 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 to connect resources into a federated infrastructure. The Federated Cloud currently integrates the following main standard-based technological components:
|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 (IaaS) 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 & Block Storage Management||http://occi-wg.org/|
|GLUE Schema||The GLUE Schema is a common way of publishing information about sites and services of grid or cloud resources. GLUE is a open specification developed by the Open Grid Forum with implementations for a range of systems; the EGI Federated Cloud uses the LDAP based BDII implementation.||Information system for cloud resources||https://forge.ogf.org/sf/projects/glue-wg|
|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|
|CDMI: Cloud Data Management Interface||The Cloud Data Management Interface defines the functional interface that applications use to create, retrieve, update and delete data elements from Object-base storage in the cloud. CDMI is a flexible protocol that allows clients to discover the capabilities of the cloud storage offering and to manage containers and the data that is placed in them.||Object Storage||http://www.snia.org/cdmi|
Users' technical support is provided via the EGI support contact.
Technical problems and questions relating to the use of the EGI Federated Cloud can be reported and dealt with through the 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 this page.