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.

HOWTO17 How to use the Catania Science Gateway Framework as Infrastructure Broker

From EGIWiki
Revision as of 15:14, 27 May 2014 by Scardaci (talk | contribs)
Jump to navigation Jump to search
Main Roadmap and Innovation Technology For Users For Resource Providers Media



The Catania Science Gateway Framework (CSGF) has been developed by INFN, Division of Catania (Italy), to provide application developers with a tool to create Science Gateways (SGs) in short time and in a very easy way. CSGF is made of a set of libraries to manage Authentication & Authorization mechanisms and to interact with several different kinds of DCIs (grid, cloud, HPC, local, etc.). The CSGF is fully compliant to the EGI.eu VO portal policy. The CSGF allows users to instanciate virtual services on the EGI Federated Cl oud through web portals/SGs. The Science Gateways based on CSGF provide users with intuitive web interface to manage virtualised services such as instantiating, moving them around different physical resources; interact with and terminate them. A list of Science Gateways based on the CSGF is available here.

Use the Catania Science Gateway Framework as IAAS or PAAS

The CSGF foresees three distinct figures: the 'Requestor', the 'Cloud Tenant' and the 'Cloud Manager' interacting each other as expressed below:

  • Requestor: Any SG registered user can request a virtualised service by filling an online survey accessible by a dedicated section of the SG. The request form has three different set of questions: Requestor' generalities, Cloud resources and the Acceptable usage Policy (AUP). The most important part of the survey consists of the Cloud service description which is splitted in two different parts: The user request one of the available generic templates or a user requests to deploy its own virtual service. Depending on the kind of request the survey questions may differ. At the end of the survey the user must agree and sign to the AUP.
  • Cloud Tenant: The Cloud Tenant is a special SG user having the rights to manage the instances of the virtualised services. The Cloud Tenant SG rights are bounded within the scope offered by the SG and more in general bounded to the resources provided by its own VO. Only SG registered user can become a Cloud Tenant applying for the specific authorization flag during the portal registration phase. Once gained this particular role it will be possible to access a special portlet named MyCloud. This portlet is capable to manage one or many instances of the requested Cloud services over the Federated Cloud available resources.
  • Cloud Manager: This figure is not stricly related to the SG, it rather depends on the physical resources being shared by the VO. This kind of users are the responsible to phisically define the virtual machine templates that will be instantiable by the Cloud tenants through the MyCloud portlet. In small SGs/VOs the Cloud Tenant fully matches with the Cloud Manager and it could be or not a registered member of the SG.