Difference between revisions of "Federated Cloud Discovery"
(→BDII) |
|||
Line 51: | Line 51: | ||
== GlueSchema 2.1 == | == GlueSchema 2.1 == | ||
We are currently under transition to a the GlueSchema 2.1 format for publishing information on the BDII. This change will provide more information about the endpoints, the supported VOs and the available images at each resource provider. | We are currently under transition to a the GlueSchema 2.1 format for publishing information on the BDII. This change will provide more information about the endpoints, the supported VOs and the available images at each resource provider. | ||
GlueSchema 2.1 draft is available as a [https://docs.google.com/document/d/1BpeTBQfCn8xRo4Ff38esRhBwzoUHE4bVxba2rEAzI-U/edit Google document] | |||
The implementation at the cloud-info-provider following the schema is being implemented at [https://github.com/gwarf/cloud-info-provider cloud-info-provider repo at github] | |||
First tests with providers are being carried out during Q4 2017. |
Revision as of 12:14, 13 November 2017
GOCDB
EGI Federated Cloud services are provided by a set of EGI Resource Centres registered in GOCDB with a specific FedCloud scope. These can be easily discovered via the web based view . API access is also available.
Service Endpoints
GOCDB maintains the different service endpoints that compose the EGI cloud services. Relevant service types for EGI Cloud are (links will bring you directly to the GOCDB XML results for querying that specific service type):
- eu.egi.cloud.vm-management.occi EGI cloud virtual machine management based on OCCI 1.1 specification http://occi-wg.org
- eu.egi.cloud.storage-management.cdmi EGI cloud data management interface based on CDMI 1.0.2 specification http://www.snia.org/cdmi
- org.openstack.nova OpenStack Nova provides VM management services.
You may also check higher-level service types from brokers:
- eu.egi.cloud.broker.compss A super-scalar broker service and programming model for Grids and Clouds. From Barcelona Supercomputing Centre (BSC).
- eu.egi.cloud.broker.proprietary.slipstream A broker supporting autoscaling and elasticity of virtualised applications in federated Clouds. From SixSq AG.
- eu.egi.cloud.broker.vmdirac A IaaS cloud broker extending Dirac to automated VM based application deployment. From Universitat Autònoma de Barcelona (UAB).
AppDB
AppDB cloud marketplace provides information about the cloud services. Within the cloud marketplace, users can browse:
AppDB has a query API to retrieve this information.
BDII
The common information system deployed at EGI is based on the Berkeley Database Information Index (BDII) with a hierarchical structure distributed over the whole infrastructure. Information on OCCI resources are published through the cloud BDII information provider including the available endpoints and their characteristics. AppDB relies on the EGI Information service to display the resource centres. This information is also used for operational purposes (e.g. the monitoring depends on certain data to be present in order to properly operate).
Information can be gathered from any of the available Top BDIIs.
You can use a ldap client to query the BDII. Here are some example queries.
List of sites providing IaaS:
ldapsearch -x -H ldap://lcg-bdii.cern.ch:2170 \ -b GLUE2GroupID=grid,o=glue "GLUE2ServiceType=IaaS" \ GLUE2ServiceAdminDomainForeignKey
OCCI endpoints for a given site SITE
:
ldapsearch -x -H ldap://lcg-bdii.cern.ch:2170 \ -b GLUE2DomainID=<site name>,GLUE2GroupID=grid,o=glue \ GLUE2EndpointInterfaceName=OCCI GLUE2EndpointUR
Get all OCCI resource templates for a given site:
ldapsearch -x -H ldap://lcg-bdii.cern.ch:2170 \ -b GLUE2DomainID=<site-name>,GLUE2GroupID=grid,o=glue \ objectClass=GLUE2ExecutionEnvironment GLUE2ResourceID
GlueSchema 2.1
We are currently under transition to a the GlueSchema 2.1 format for publishing information on the BDII. This change will provide more information about the endpoints, the supported VOs and the available images at each resource provider.
GlueSchema 2.1 draft is available as a Google document
The implementation at the cloud-info-provider following the schema is being implemented at cloud-info-provider repo at github
First tests with providers are being carried out during Q4 2017.