Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "Federated Cloud user support"

From EGIWiki
Jump to navigation Jump to search
Line 1: Line 1:
{{Fedcloud-tf:Menu}} {{TOC_right}}  
{{Fedcloud-tf: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 workloads. Also, the EGI cloud is suitable to projects aiming to provide services and platforms to the scientific community.  
 
<!--
 
<big>Technical support is available via the [mailto:support@egi.eu EGI.eu Support Team]</big>
 
 
 
 
 
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. <!--
== How to get access to the FedCloud?  ==
== How to get access to the FedCloud?  ==


Line 16: Line 23:
*Estimated number and size of machines that you need from EGI  
*Estimated number and size of machines that you need from EGI  
*Link to webpage, document or other online resource for further information
*Link to webpage, document or other online resource for further information
-->
-->  


=== Concept  ===
=== 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:
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
*Total control over deployed applications  
* Immediately processed workloads – no more waiting time
*Elastic resource consumption based on real needs  
* An extended e-Infrastructure across resource providers in Europe
*Immediately processed workloads – no more waiting time  
* Service performance scaled with elastic resource consumption
*An extended e-Infrastructure across resource providers in Europe  
* Single sign-on at multiple, independent providers
*Service performance scaled with elastic resource consumption  
*Single sign-on at multiple, independent providers


After [[Federated_Cloud_user_support|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.  
After [[Federated_Cloud_user_support|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.  


[[File:fedcloud.png|550px|center]]
[[Image:Fedcloud.png|center|550px|Fedcloud.png]]  


#Users select Virtual Appliances (a virtual machine image that encapsulates an operating system and optionally a set of applications) from the [http://appdb.egi.eu 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.
#Users select Virtual Appliances (a virtual machine image that encapsulates an operating system and optionally a set of applications) from the [http://appdb.egi.eu 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 [http://appdb.egi.eu EGI Applications Database] may be reusable, customisable for your use case.  
#*Tip: Images from the [http://appdb.egi.eu 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.  
#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.  
#*Tip: Follow [[Fedcloud-tf:CLI_Environment|this guide]] to setup the rOCCI command line client.  
#*Tip: Follow [[Fedcloud-tf:CLI Environment|this guide]] to setup the rOCCI command line client.  
#*Tip: Read in [[HOWTO10|this guidance]] about various options of porting applications to the EGI Federated Cloud.
#*Tip: Read in [[HOWTO10|this guidance]] about various options of porting applications to the EGI Federated Cloud.  
#*Tip: Use one of these [[HOWTO10|high-level tools]] to instantiate VMs on cloud sites.
#*Tip: Use one of these [[HOWTO10|high-level tools]] to instantiate VMs on cloud sites.  
#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.
#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 [[HOWTO09|storage how-to]] for more information on the storage services of FedCloud ('''PREPRODUCTION''')
#*Tip: Read the [[HOWTO09|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.
#Sites support the Virtual Organizations (VOs) and automatically download the Virtual Appliance lists endorsed by the VO managers.


<br>


== Current FedCloud Users and Communities  ==
== Current FedCloud Users and Communities  ==


<!-- [[File:fedclouduclogos.png|800px|thumb]] -->
<!-- [[File:fedclouduclogos.png|800px|thumb]] --> [[Image:Fedclouduclogos.png|center|550px|Fedclouduclogos.png]]  
[[File:fedclouduclogos.png|550px|center]]


<br>
<br> More details of the FedCloud User Communities and their use cases is in the [[Federated Cloud Communities|FedCloud Users Communities]] page.  
More details of the FedCloud User Communities and their use cases is in the [[Federated_Cloud_Communities|FedCloud Users Communities]] page.


== How to use the FedCloud?  ==
== 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 '''[[FAQ10|FedCloud FAQ page]]''' and the Guides and Tutorials listed in this page. <br>
A brief description on how to use the FedCloud resources is described in the text below. More information can be found on the '''[[FAQ10|FedCloud FAQ page]]''' and the Guides and Tutorials listed in this page. <br>  


<br>
<br>  


Technical support is available via the [mailto:ucst@egi.eu EGI.eu UCST Team]  
Technical support is available via the [mailto:ucst@egi.eu EGI.eu UCST Team]  
Line 107: Line 114:


*rOCCI (OCCI client/server, used to manage computing resources): [http://github.com/EGI-FCTF/rOCCI-cli/ http://github.com/EGI-FCTF/rOCCI-cli/]
*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  ==
== Technical background  ==
Line 115: Line 122:
=== EGI Federated Cloud Sites  ===
=== 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]].
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]].  


=== Interfaces and protocols  ===
=== Interfaces and protocols  ===
Line 133: Line 140:
| [http://occi-wg.org/ http://occi-wg.org/]
| [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  
| GLUE Schema  
| The GLUE Schema is a common way of publishing information about sites and services of grid or cloud resources. GLUE is developed by a consortium of grid projects, including the two largest projects of the EGI collaboration: EGI-InSPIRE and EMI. Implementations of the Schema exist for a range of systems, the EGI Federated Cloud uses the LDAP based BDII implementation.  
| The GLUE Schema is a common way of publishing information about sites and services of grid or cloud resources. GLUE is developed by a consortium of grid projects, including the two largest projects of the EGI collaboration: EGI-InSPIRE and EMI. Implementations of the Schema exist for a range of systems, the EGI Federated Cloud uses the LDAP based BDII implementation.  
Line 153: Line 155:
| Data and meta-data management  
| Data and meta-data management  
| [http://www.snia.org/cdmi http://www.snia.org/cdmi]
| [http://www.snia.org/cdmi http://www.snia.org/cdmi]
|- -->
|- -->  


== User support  ==
== User support  ==
Line 159: Line 161:
=== Technical support  ===
=== Technical support  ===


Users' technical support is provided via the [mailto:ucst@egi.eu EGI.eu UCST Team] email.
Users' technical support is provided via the [mailto:ucst@egi.eu EGI.eu UCST Team] email.  


=== Helpdesk  ===
=== 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!
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  ===
=== Feedback and open issues  ===


A list of open-issue and feedbacks reported by the FedCloud users is available at [[Federated_Cloud_Users_Feedback_and_open_issues|this page]].  
A list of open-issue and feedbacks reported by the FedCloud users is available at [[Federated Cloud Users Feedback and open issues|this page]].  


<!--
<!--

Revision as of 16:40, 28 January 2015

Main Roadmap and Innovation Technology For Users For Resource Providers Media




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.

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 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.

Fedcloud.png
  1. 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.
  2. 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.
    • Tip: Follow this guide to setup the rOCCI command line client.
    • Tip: Read in this guidance about various options of porting applications to the EGI Federated Cloud.
    • Tip: Use one of these high-level tools to instantiate VMs on cloud sites.
  3. 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)
  4. Sites support the Virtual Organizations (VOs) and automatically download the Virtual Appliance lists endorsed by the VO managers.


Current FedCloud Users and Communities

Fedclouduclogos.png


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.


Technical support is available via the EGI.eu UCST Team

Quick Start

The typical user workflow on the EGI Federated Cloud looks like:

  1. Obtain a grid certificate from a recognised CA (if you don't own one already)
  2. 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.
  3. Select existing images from the Application Database Cloud Marketplace and start them by:
    1. Using the command line client OR
    2. Using one of the high level brokering tools that are interoperable with the Federated Cloud.

Advanced Usage

Virtual Organisation

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:

  1. Prepare Virtual Machine Images (VMIs) that encapsulate your application. See the application porting tutorial for tips.
  2. Make the VMIs available online, for example in the EGI Appliance Repository
  3. Register the VMIs as Virtual Appliance in the EGI Applications Database (for howto please click here)
  4. 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:


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 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 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 developed by a consortium of grid projects, including the two largest projects of the EGI collaboration: EGI-InSPIRE and EMI. 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</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


User support

Technical support

Users' technical support is provided via the 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 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.