|
|
| (5 intermediate revisions by 2 users not shown) |
| Line 15: |
Line 15: |
| {{Template:Block-comment | | {{Template:Block-comment |
| | name=Warning | | | name=Warning |
| | text=The installation manual is now available at https://egi-federated-cloud-integration.readthedocs.io/. Information below is not maintained and outdated! | | | text=The installation manual is now available at https://docs.egi.eu/. Information below just points to the relevant sections of that manual |
| }} | | }} |
|
| |
|
| = 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:
| |
| ** <code>ops</code> and <code>dteam</code> VOs, used for operational purposes as per RC OLA
| |
| ** a community-VO that supports EGI users (e.g. <code>fedcloud.egi.eu</code> 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)
| |
|
| |
| <!-- TO BE CHECKED
| |
| In order to configure Virtual Organisations and private image lists, please consider the following guides to:
| |
| * [[HOWTO16|enable a Virtual Organisation on a EGI Federated Cloud site]]
| |
| * [https://wiki.appdb.egi.eu/main:faq:how_to_get_access_to_vo-wide_image_lists get access to VO wide image lists]
| |
| * [https://wiki.appdb.egi.eu/main:faq:how_to_subscribe_to_a_private_image_list_using_the_vmcatcher subscribe to a private image list]
| |
| -->
| |
|
| |
| = Integration =
| |
|
| |
| Dedicated integration guides for each cloud management framework are provided below:
| |
| * OpenNebula
| |
| ** [[Federated_Cloud_OpenNebula_guide | OpenNebula v5.2.x/v5.4.x]]
| |
| * OpenStack:
| |
| ** [[Federated_Cloud_Mitaka_guide | OpenStack Mitaka]] -- LTS under Ubuntu 16.04 (otherwise EOL)
| |
| ** [[Federated_Cloud_Ocata_guide | OpenStack Ocata]]
| |
| ** [[Federated_Cloud_Pike_guide | OpenStack Pike]]
| |
| ** [[Federated_Cloud_Queens_guide | OpenStack Queens]] -- ''Support for Keystone-VOMS is not available''
| |
| * OpenStack EOL'd versions ('''not recommended in production''')
| |
| ** [[Federated_Cloud_Newton_guide | OpenStack Newton]]
| |
|
| |
| See http://releases.openstack.org/ for more details on the OpenStack releases.
| |
|
| |
| = Registration of services in GOCDB =
| |
|
| |
| Site cloud services must be registered in [https://goc.egi.eu EGI Configuration Management Database (GOCDB)]. If you are creating a new site for your cloud services, check the [[PROC09|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 [[Federated_Cloud_Technology#eu.egi.cloud.vm-management.occi|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:
| |
| *# Max number of virtual cores for VM with parameter name: <code>cloud_max_cores4VM</code>
| |
| *# Max amount of RAM for VM with parameter name: <code>cloud_max_RAM4VM</code> using the format: value+unit, e.g. "16GB".
| |
| *# Max amount of storage that could be mounted in a VM with parameter name: <code>cloud_max_storage4VM</code> using the format: value+unit, e.g. "16GB".
| |
|
| |
| = Installation Validation =
| |
|
| |
| You can check your installation following these steps:
| |
|
| |
| *Check in [https://argo-mon2.egi.eu/nagios 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:<br><code>ldapsearch -x -h <site bdii host> -p 2170 -b Glue2GroupID=cloud,Glue2DomainID=<your site name>,o=glue</code>
| |
| *Check that all the images listed in the [https://appdb.egi.eu/store/vo/fedcloud.egi.eu 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:<br><code>ldapsearch -x -h <site bdii host> -p 2170 -b Glue2GroupID=cloud,Glue2DomainID=<your site name>,o=glue objectClass=GLUE2ApplicationEnvironment GLUE2ApplicationEnvironmentRepository</code>
| |
| *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 [[HOWTO04_Site_Certification_Manual_tests#Check_the_functionality_of_the_cloud_elements|site certification manual tests]] against your endpoints.
| |
| *Check in the [http://accounting-devel.egi.eu/cloud.php accounting portal] that your site is listed and the values reported look consistent with the usage of your site.
| |
|
| |
|
| [[Category:Operations_Manuals]] | | [[Category:Operations_Manuals]] |
The wiki is deprecated and due to be decommissioned by the end of September 2022.