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 "User:Enolfc"

From EGIWiki
Jump to navigation Jump to search
Line 2: Line 2:
https://www.egi.eu/sso/userDetail/enolfc
https://www.egi.eu/sso/userDetail/enolfc


= FedCloud Users  =


{{Fedcloud_Menu}} {{TOC_right}}


<br> <big>Technical support is available via the [mailto:support@egi.eu EGI.eu Support Team]</big>
{{Fedcloud_Menu}}
{{TOC_right}}


<br> The EGI Cloud federation is an hybrid cloud composed by public, community and private clouds, all supported by the EGI Core Infrastructure Platform services 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:
= EGI Cloud Federation =


;Elastic computing infrastructure.  
The EGI Federated Cloud is a multi-national cloud system that integrates institutional clouds into a scalable computing platform for data and/or compute driven applications and services. The initial architecture of the EGI Federated Cloud was defined in 2011-2012 and was fully implemented by May 2014. Currently, the federation is a collaboration that enables various types of cloud federations to serve diverse demands of researchers from both academia and industry. The EGI Federated Cloud brings together scientific communities, R&D projects, technology and resource providers to form a community that integrates and maintains a flexible solution portfolio that enables various types of cloud federations with IaaS, PaaS and SaaS capabilities. The collaboration is committed to the use of open source tools and services that are reusable across scientific disciplines. These tools and services form a flexible portfolio from which a scientific community can mix and match items to establish its own, customised cloud federation.  
:Execute compute and data intensive workloads (both batch and interactive), host long-running services (e.g. web servers, databases or applications servers), or create disposable testing and development environments on VMs and scale your infrastructure needs over a federation of cloud providers. Select VM configurations (CPU, memory, disk) and application environments that better fit your requirements.


;VM image sharing and distribution
:Easily share and distribute VM images for your applications on a open library of Virtual Appliances. Community curated appliances are securely and automatically replicated accross the infrastructure. EGI provides a set of securely configured images with basic software ready to use on all providers that can be re-used and extended with contextualisation to execute your applications


;Unified view of federation
The EGI Federated Cloud provides the services and technologies to create federation of clouds (community, private or public clouds) that operate according to the preferences, choices and constraints set by its members and users. The EGI Cloud Federations are modelled around the concept of an abstract Cloud Management stack subsystem that is integrated with components of the EGI Core Infrastructure and that provides a set of agreed uniform interfaces within the community it provides services to.
:The EGI Cloud provides: Single sing-on (SSO) for authentication and authorisation across all resource providers; Federated accounting with an integrated view of the the resource and service usage; Distributed information system for delivering a real-time view of the capabilities; and Federated monitoring to compute metrics for availability and reliability of the services.


;Beyond VMs
[[Image:Federated_Cloud_Model.png|thumb|center|600px|Federated Cloud Model]]
:Run docker applications on the EGI resources or use any of the supported PaaS and SaaS solutions that extend the IaaS capabilities of the EGI cloud and abstract the infrastructure to let you focus on your application development.


== Current Users and Communities  ==
The EGI Cloud Federation (see Figure ) is a hybrid cloud composed by public, community and private clouds, all supported by the EGI Core Infrastructure Platform services. The EGI Federated Cloud is composed by multiple “realms”, each realm having homogeneous cloud management interfaces and capabilities. A cloud realm is a subset of cloud providers exposing homogeneous cloud management interfaces and capabilities. The Open Standards Cloud Realm supports the usage of open standards for its interfaces and is completely integrated with the EGI Core Infrastructure Platform. A Community Platform provides community-specific data, tools and applications, which can be supported by one or more realms.


EGI Federated Cloud already has a large use base, check the [[Federated Cloud Communities|FedCloud Users Communities]] page for more details.
== Services in cloud federations ==
Despite the large diversity in the type of cloud realms, a relatively small number of identical building blocks (or federator services) can be identified in almost all of them. These services turn individual clouds into a federation. The table collects these common services to help architects identify topics they should focus on when designing a cloud federation. Technical details fro these are also available at [Federated Cloud Technology]


[[Image:Fedclouduclogos.png|center|550px|Fedclouduclogos.png]]
{| class="wikitable" style="margin: auto;"
|-
! Federation Service
! Role within the federation
! Existing technical solution in EGI
|-
! Service Registry
| A registry where all the federated sites and services are registered and state their capabilities. The registry provides the ‘big picture view’ about the federation for both human users and online services (such as service monitors).
|GOCDB
|-
!Information System
|A database that provides real-time view about the actual capabilities and load of federation participants. Can be used by both human users and online services.
|BDII
|-
! Virtual Machine Image Catalogue
| A catalogue of Virtual Machine Images (VMIs) that encapsulate those software configurations that is useful and relevant for the given community (typically pre-configured scientific models and algorithms).
|AppDB
|-
! Image replication mechanism
| A system that automatically replicates VMIs from the federation VMI catalogue to each of the member sites, as well as removes them when needed. Automated replication can ensure consistency of capabilities across sites and is very often coupled with a VMI vetting process to ensure that only properly working, and relevant VMIs are replicated to the cloud sites of the community.
| vmcatcher/vmcaster
|-
! Single sign-on for users
| Ensuring that users of the federation need to register for access only once before they can use the federated services. Single sign-on is increasingly implemented in the form of identity federations in both industry and academia.
| IGTF X509 proxies with VOMS extensions
|-
! Integrated view about resource/service usage
|A system that pulls together usage (accounting) information from the federated sites and services, integrates the data and presents them in such a way that both individual users and communities can monitor their own resource/service usage across the whole federation.
| Cloud Usage Record, APEL Accounting repository and portal
|-
! Integrated interfaces or user environments
|Having interfaces through which users and user applications can interact with the services offered by the various cloud providers. In case of an IaaS cloud federation these interfaces offer compute, storage and network management capabilities.
|OCCI API and OpenStack API
|-
!Availability Monitoring
| Use a shared system to monitor and collect availability and reliability statistics about the distributed cloud service providers and to retrieve this information programmatically.  
| ARGO monitoring system
|-
! Federated service management tools
| A set of processes, policies, activities and supporting tools customized to the federated cloud.
| EGI federated service management
|}
= EGI cloud realms =


== Usage Models  ==
The EGI Federated Cloud can support multiple cloud federations (community specific, private or public). Based on the EGI federation services and custom external solutions, any scientific community can create a federated cloud. Each community or e-infrastructure that wants to build a cloud federation decides the services required to support their computational needs. Because these cloud federations are largely built from tools and services of the same solution portfolio, they can maintain the portfolio together; they can share best practices, and can offer user support and training in a collaborative fashion.


'''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.  
EGI currently operates two realms: the '''Open Standards Realm''' and the '''OpenStack Realm'''. Both are completely integrated with the EGI federator services described above but use different interfaces to offer the IaaS capabilities to the users: the Open Standards Realm uses OCCI standard (supported by providers with OpenNebula, OpenStack or Synnefo cloud management frameworks), while the OpenStack Realm uses OpenStack native Nova API (support limited to OpenStack providers). This OpenStack Realm was introduced in the federation during November 2015 and most of the resource providers already in the Open Standards Realm using OpenStack have started to provide this API along with the existing OCCI interface.


We classified the usage models enabled by the EGI Fededated Cloud as follows:  
{| class="wikitable" style="margin: auto;"
 
|-
*'''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.
! Service
*'''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.
! Open Standards Realm
*'''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.
! OpenStack Realm
*'''Disposable and testing environments''': environments for training or testing new developments.
|-
 
! Service Registry
<br> [[Image:FedCloudUsageModels.png|center|550px|FedCloudUsageModels.png]] <br>
| colspan="2" style="text-align: center;" | GOCDB
 
|-
 
! Single sign-on
 
| colspan="2" style="text-align: center;" | X.509 proxies with VOMS extensions
== How to use the EGI Federated Cloud?  ==
|-
 
! Accounting
=== Access  ===
| colspan="2" style="text-align: center;" | Cloud Usage Record
 
|-
EGI provides users with a single sign-on mechanism to access the federated services with the use of X.509 certificates and Virtual Organisations (VOs). Before using the EGI Federated Cloud you will need to:  
! Information discovery
 
| colspan="2" style="text-align: center;"| BDII
*[http://www.egi.eu/how-to/get_a_certificate.html Obtain a grid certificate] from a recognised CA (if you don't own one already).
|-
*Join [https://perun.metacentrum.cz/perun-registrar-cert/?vo=fedcloud.egi.eu 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.
! VM Image catalogue
*If you are part of an [http://operations-portal.egi.eu/vo/search existing VO] that has access to cloud resources, you may use that VO.
| colspan="2" style="text-align: center;" | AppDB
<!-- TODO: how to know if a VO has cloud resources?, which are those resources? -->
|-
 
! VM Image distribution
=== Creating your first VM - Instantiate an exiting image ===
| colspan="2" style="text-align: center;" | vmcatcher/vmcaster
 
|-
The basic user workflow for starting a Virtual Machine (VM) looks like this:  
! IaaS interface
 
| OCCI
#Browse in the [https://appdb.egi.eu/browse/cloud Application Database Cloud Marketplace] the available Virtual Appliances. Virtual Appliances  are the templates for the root volume of the running instances (Operating System and applications). EGI offers a set of basic images with minimal configuration that can get you started easily, but you can also find complete application stacks. See for example these images:
| OpenStack Compute API
#*[https://appdb.egi.eu/store/vappliance/egi.ubuntu.14.04 EGI Ubuntu 14], a basic [http://www.ubuntu.com/ Ubuntu 14.04] image
|-
#*[https://appdb.egi.eu/store/vappliance/egi.centos.6 EGI Centos 6], a basic [https://www.centos.org/ CentOS 6] image
! Monitoring
#*[https://appdb.egi.eu/store/software/compss.framework COMPSs], a VM for using [[HOWTO14_How_to_use_COMPSs|COMPSs]] programming framework
| ARGO (OCCI specific probes)
#*[https://appdb.egi.eu/store/vappliance/biovel.portal BioVel Portal], for executing a http://www.biovel.eu/ biodiversity virtual e-Laboratory]
| ARGO (OpenStack specific probes)
#Read the description of the appliance for information on how to use it and connect to it once started.
|}
#*You may need to have a ssh key in order to login into the VM, check [[FAQ10#How_can_I_inject_my_public_SSH_key_into_the_machine.3F|the FAQ on how to create one]]
#Get the IDs for starting the appliance at one of the sites supporting it in the "Availability and Usage" tab.
#Get the [[HOWTO11|command line client]] to start the VM using the IDs from previous step
#*Check the [[FAQ10#How_can_I_start_a_VM.3F|How can I start a VM?]] FAQ entry and the [[HOWTO11|command line client how to]] for more information.
#Connect to VM and start using it
#*You may need to allocate a public IP for the VM, check [[FAQ10#How_can_I_assign_a_public_IP_to_a_VM.3F|How can I assign a public IP to a VM]] in the Federated Cloud FAQ
 
=== Advanced topics  ===
 
==== API and SDKs access to Federated Cloud resources ====
 
Besides the command line client, there are several [[Federated Cloud APIs and SDKs|APIs and SDK ready to be used with the EGI Federated Cloud]].Preferred API for EGI federated cloud is OCCI, which can be accesses using using a command-line client (rOCCI), high-level tools or directly implementing the ‘Open Cloud Computing Interface’ (OCCI) into your environment. OpenStack Nova API is also available for OpenStack sites belonging to the Federation.
 
==== Storage ====
 
Every instantiated VM has some disk space provided with it, if you need more storage or need to share data, you can use a cloud storage solution. There are two kind of services: Block Storage and Object Storage. Check the [[HOWTO09|EGI Federated Cloud Storage How To]] for more information.
 
==== Docker containers ====
 
You can [[Federated Cloud Containers|run your docker applications on EGI's Cloud]]. EGI also provides a [[Federated_Cloud_Containers#EGI_Federated_Cloud_clients_docker_image|docker image with the clients]] so you can test them easily.
 
==== PaaS/SaaS ====
 
Read in [[HOWTO10|this guidance]] about various options of porting applications to the EGI Federated Cloud that includes information on several [[HOWTO10#4._Infrastructure_broker_2|High level user environments to interact with the EGI Federated Cloud]] to manage your applications as VMs on cloud sites.
 
==== GPGPUs (pre-production!) ====
 
'''PRE-PRODUCTION''' GPGPUs-enabled cloud resources are available in selected sites of the EGI Federated Cloud. Check the [[GPGPU-FedCloud|GPGPU guide on FedCloud]] for details on how to access 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 [[HOWTO10|application porting tutorial]] for tips.
#Make the VMI available online, for example in the [http://appliance-repo.egi.eu/images/ EGI Appliance Repository]
#Register the VMIs as Virtual Appliances in the [http://appdb.egi.eu EGI Applications Database] (for howto please click [https://wiki.appdb.egi.eu/main:faq:how_to_register_a_virtual_appliance here])
#Once your VA is published (see howto [https://wiki.appdb.egi.eu/main:guides:guide_for_managing_virtual_appliance_versions_using_the_portal here]),inform the Manager of your VO through Applications Database about it (see howto [https://wiki.appdb.egi.eu/main:guides:notify_virtual_organization_representatives 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.
 
==== 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 [http://operations-portal.egi.eu/vo/search Operations Portal]. (Search for Cloud as a middleware type.)
*Existing grid production VOs can be extended by VO&nbsp;manager to cloud by declaring cloud resources in VO&nbsp;ID card (in Operations Portal) and requesting via [http://ggus.eu/ GGUS ](assign to Perun Support Unit) Perun support.
*If no existing VO suits your case, a new VO can be created. Please follow [[PROC14_VO_Registration|VO Registration procedure]]. You can invite sites from the infrastructure to support them.
 
== Useful resources  ==
 
*[[FAQ10|FedCloud FAQ page]]
*[http://www.egi.eu/how-to/get_a_certificate.html How to get a certificate (to access Federated Cloud resources)]
*[https://wiki.appdb.egi.eu/ How to use the Applications Database Cloud Marketplace]
*[[HOWTO10|Porting your application/web service to the EGI Federated Cloud]]
*[[Federated_Cloud_Operation#Current_Resource_Providers|List and details about certified cloud resource providers]]
*[[Cloud_SAM_tests|Explanation of NAGIOS tests performed by EGI on cloud resources]]
**[https://cloudmon.egi.eu/nagios/cgi-bin/status.cgi?host=all&amp;sorttype=2&amp;sortoption=2 Current status of Federated Cloud resources (NAGIOS test results)]
**[https://cloudmon.egi.eu/nagios/cgi-bin/status.cgi?servicegroup=SERVICE_org.openstack.nova&amp;style=overview Current status of OpenStack interfaces in the EGI federated cloud]
 
== User support  ==
 
=== Technical support  ===
 
Users' technical support is provided via the [mailto:usupport@egi.eu EGI support contact].
 
=== 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 [[Federated Cloud Users Feedback and open issues|this page]].
 
== 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 [[Federated_Cloud_Operation#Current_Resource_Providers|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. Read more about the [[Federated Cloud Technology|technology that drives the Federated Cloud]].

Revision as of 11:53, 2 March 2016

Enol Fernandez - CSIC https://www.egi.eu/sso/userDetail/enolfc


Overview For users For resource providers Infrastructure status Site-specific configuration Architecture




EGI Cloud Federation

The EGI Federated Cloud is a multi-national cloud system that integrates institutional clouds into a scalable computing platform for data and/or compute driven applications and services. The initial architecture of the EGI Federated Cloud was defined in 2011-2012 and was fully implemented by May 2014. Currently, the federation is a collaboration that enables various types of cloud federations to serve diverse demands of researchers from both academia and industry. The EGI Federated Cloud brings together scientific communities, R&D projects, technology and resource providers to form a community that integrates and maintains a flexible solution portfolio that enables various types of cloud federations with IaaS, PaaS and SaaS capabilities. The collaboration is committed to the use of open source tools and services that are reusable across scientific disciplines. These tools and services form a flexible portfolio from which a scientific community can mix and match items to establish its own, customised cloud federation.


The EGI Federated Cloud provides the services and technologies to create federation of clouds (community, private or public clouds) that operate according to the preferences, choices and constraints set by its members and users. The EGI Cloud Federations are modelled around the concept of an abstract Cloud Management stack subsystem that is integrated with components of the EGI Core Infrastructure and that provides a set of agreed uniform interfaces within the community it provides services to.

Federated Cloud Model

The EGI Cloud Federation (see Figure ) is a hybrid cloud composed by public, community and private clouds, all supported by the EGI Core Infrastructure Platform services. The EGI Federated Cloud is composed by multiple “realms”, each realm having homogeneous cloud management interfaces and capabilities. A cloud realm is a subset of cloud providers exposing homogeneous cloud management interfaces and capabilities. The Open Standards Cloud Realm supports the usage of open standards for its interfaces and is completely integrated with the EGI Core Infrastructure Platform. A Community Platform provides community-specific data, tools and applications, which can be supported by one or more realms.

Services in cloud federations

Despite the large diversity in the type of cloud realms, a relatively small number of identical building blocks (or federator services) can be identified in almost all of them. These services turn individual clouds into a federation. The table collects these common services to help architects identify topics they should focus on when designing a cloud federation. Technical details fro these are also available at [Federated Cloud Technology]

Federation Service Role within the federation Existing technical solution in EGI
Service Registry A registry where all the federated sites and services are registered and state their capabilities. The registry provides the ‘big picture view’ about the federation for both human users and online services (such as service monitors). GOCDB
Information System A database that provides real-time view about the actual capabilities and load of federation participants. Can be used by both human users and online services. BDII
Virtual Machine Image Catalogue A catalogue of Virtual Machine Images (VMIs) that encapsulate those software configurations that is useful and relevant for the given community (typically pre-configured scientific models and algorithms). AppDB
Image replication mechanism A system that automatically replicates VMIs from the federation VMI catalogue to each of the member sites, as well as removes them when needed. Automated replication can ensure consistency of capabilities across sites and is very often coupled with a VMI vetting process to ensure that only properly working, and relevant VMIs are replicated to the cloud sites of the community. vmcatcher/vmcaster
Single sign-on for users Ensuring that users of the federation need to register for access only once before they can use the federated services. Single sign-on is increasingly implemented in the form of identity federations in both industry and academia. IGTF X509 proxies with VOMS extensions
Integrated view about resource/service usage A system that pulls together usage (accounting) information from the federated sites and services, integrates the data and presents them in such a way that both individual users and communities can monitor their own resource/service usage across the whole federation. Cloud Usage Record, APEL Accounting repository and portal
Integrated interfaces or user environments Having interfaces through which users and user applications can interact with the services offered by the various cloud providers. In case of an IaaS cloud federation these interfaces offer compute, storage and network management capabilities. OCCI API and OpenStack API
Availability Monitoring Use a shared system to monitor and collect availability and reliability statistics about the distributed cloud service providers and to retrieve this information programmatically. ARGO monitoring system
Federated service management tools A set of processes, policies, activities and supporting tools customized to the federated cloud. EGI federated service management

EGI cloud realms

The EGI Federated Cloud can support multiple cloud federations (community specific, private or public). Based on the EGI federation services and custom external solutions, any scientific community can create a federated cloud. Each community or e-infrastructure that wants to build a cloud federation decides the services required to support their computational needs. Because these cloud federations are largely built from tools and services of the same solution portfolio, they can maintain the portfolio together; they can share best practices, and can offer user support and training in a collaborative fashion.

EGI currently operates two realms: the Open Standards Realm and the OpenStack Realm. Both are completely integrated with the EGI federator services described above but use different interfaces to offer the IaaS capabilities to the users: the Open Standards Realm uses OCCI standard (supported by providers with OpenNebula, OpenStack or Synnefo cloud management frameworks), while the OpenStack Realm uses OpenStack native Nova API (support limited to OpenStack providers). This OpenStack Realm was introduced in the federation during November 2015 and most of the resource providers already in the Open Standards Realm using OpenStack have started to provide this API along with the existing OCCI interface.

Service Open Standards Realm OpenStack Realm
Service Registry GOCDB
Single sign-on X.509 proxies with VOMS extensions
Accounting Cloud Usage Record
Information discovery BDII
VM Image catalogue AppDB
VM Image distribution vmcatcher/vmcaster
IaaS interface OCCI OpenStack Compute API
Monitoring ARGO (OCCI specific probes) ARGO (OpenStack specific probes)