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.

MAN10

From EGIWiki
Revision as of 10:32, 10 September 2018 by Enolfc (talk | contribs)
Jump to navigation Jump to search
Main EGI.eu operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security


Documentation menu: Home Manuals Procedures Training Other Contact For: VO managers Administrators



Title Cloud Resource Centre Installation Manual
Document link https://wiki.egi.eu/wiki/MAN10
Last modified 19 May 2017
Policy Group Acronym OMB
Policy Group Name Operations Management Board
Contact Group operations-support@mailman.egi.eu
Document Status DRAFT
Approved Date
Procedure Statement This manual provides information on how to set up a Resource Centre providing cloud resources in the EGI infrastructure.
Owner Owner of procedure


Warning:
The installation manual is now available at https://egi-federated-cloud-integration.readthedocs.io/. Information below is not maintained and outdated!


Common prerequirements and documentation

General minimal requirements are:

  • Very minimal hardware is required to join. Hardware requirements depend on:
    • the cloud stack you use
    • the amount of resources you want to make available
    • the number of users/use cases you want to support
  • Servers need to authenticate each other in the EGI Federated Cloud context; this is fulfilled using X.509 certificates, so a Resource Centre should be able to obtain server certificates for some services.
  • User and research communities are called Virtual Organisations (VO). Resource Centres are expected to join:
    • ops and dteam VOs, used for operational purposes as per RC OLA
    • a community-VO that supports EGI users (e.g. fedcloud.egi.eu for piloting)
  • EGI provides packages for the following operating systems (others may work but we are not providing packages):
    • CentOS 7 (and in general RHEL-compatible)
    • Ubuntu 16.04(and in general Debian-based)


Integration

Dedicated integration guides for each cloud management framework are provided below:

See http://releases.openstack.org/ for more details on the OpenStack releases.

Registration of services in GOCDB

Site cloud services must be registered in EGI Configuration Management Database (GOCDB). If you are creating a new site for your cloud services, check the PROC09 Resource Centre Registration and Certification procedure. Services can also coexist within an existing (grid) site.

If offering OCCI interface, sites should register the following services:

  • eu.egi.cloud.vm-management.occi for the OCCI endpoint offered by the site. Please note the special endpoint URL syntax described at GOCDB usage in FedCloud
  • eu.egi.cloud.accounting (host should be your OCCI machine)
  • eu.egi.cloud.vm-metadata.vmcatcher (also host is your OCCI machine)
  • Site should also declare the following properties using the Site Extension Properties feature:
    1. Max number of virtual cores for VM with parameter name: cloud_max_cores4VM
    2. Max amount of RAM for VM with parameter name: cloud_max_RAM4VM using the format: value+unit, e.g. "16GB".
    3. Max amount of storage that could be mounted in a VM with parameter name: cloud_max_storage4VM using the format: value+unit, e.g. "16GB".

Installation Validation

You can check your installation following these steps:

  • Check in ARGO-Mon2 that your services are listed and are passing the tests. If all the tests are OK, your installation is already in good shape.
  • Check that you are publishing cloud information in your site BDII:
    ldapsearch -x -h <site bdii host> -p 2170 -b Glue2GroupID=cloud,Glue2DomainID=<your site name>,o=glue
  • Check that all the images listed in the AppDB page for fedlcoud.egi.eu VO  are listed in your BDII. This sample query will return all the template IDs registered in your BDII:
    ldapsearch -x -h <site bdii host> -p 2170 -b Glue2GroupID=cloud,Glue2DomainID=<your site name>,o=glue objectClass=GLUE2ApplicationEnvironment GLUE2ApplicationEnvironmentRepository
  • Try to start one of those images in your cloud. You can do it with `onetemplate instantiate` or OCCI commands, the result should be the same.
  • Execute the site certification manual tests against your endpoints.
  • Check in the accounting portal that your site is listed and the values reported look consistent with the usage of your site.