Check-in
Authentication and Authorization integration
This manual provides information on how to set up a Resource Centre providing cloud resources in the EGI infrastructure. Integration with FedCloud requires a working OpenStack installation as a pre-requirement. EGI supports any recent OpenStack version (tested from OpenStack Mitaka).
EGI expects the following OpenStack services to be available and accessible from outside your site:
FedCloud components are distributed through CMD (Cloud Middleware Distribution) These docker containers come pre-packaged and ready to use in the EGI FedCloud Appliance so you do not need to install any extra components on your site but just run a VM and configure it approprietely to interact with your services.
The integration is performed by a set of EGI components that interact with the OpenStack services APIs:
Not all EGI components need to share the same credentials. They are individually configured, you can use different credentials and permissions if desired.
EGI distributes the integration components as:
The EGI FedCloud Appliance is available at AppDB as an OVA file. You can easily extract the VMDK disk by untaring and optionally converting it to your preferred format with qemu-img:
# get image and extract VMDK
$ curl $(curl "https://appdb.egi.eu/store/vm/image/fc90d1aa-b0ae-46a0-b457-96f6f7a7d446:7875/json?strict" \
| jq -r .url) \
| tar x "*.vmdk"
# convert to qcow2
$ qemu-img convert -O qcow2 FedCloud-Appliance.Ubuntu.*.vmdk fedcloud-appliance.qcow2
The appliance running at your OpenStack must:
eu.egi.cloud.accounting
. The host certificate and key in PEM
format are expected in /etc/grid-security/hostcert.pem
and
/etc/grid-security/hostkey.pem
respectively.fedcloud.egi.eu
VO). By default these are stored at /image_data. You can
mount a volume at that location.Configuration changes:
Configuration changes:
voms.json
file to the respective caso
and
cloudkeeper-os
directories under /etc/
There are several major changes between these versions, namely:
The CMD-OS repository provides packages that have gone through a quality assurance process for the supported distributions. Packages are available via the EGI repository.
The following services must be accessible to allow access to an OpenStack-based FedCloud site (default ports listed below, can be adjusted to your installation)
Port | Application | Note |
---|---|---|
5000/TCP | OpenStack/Keystone | Authentication to your OpenStack. |
8776/TCP | OpenStack/cinder | Block Storage management. |
8774/TCP | OpenStack/nova | VM management. |
9696/TCP | OpenStack/neutron | Network management. |
9292/TCP | OpenStack/glance | VM Image management. |
The EGI Cloud components require the following outgoing connections open:
Port | Host | Note |
---|---|---|
443/TCP | msg.argo.grnet.gr | ARGO Messaging System (used to send accounting records by SSM). |
8443/TCP | msg.argo.grnet.gr | AMS authentication (used to send accounting records by SSM). |
443/TCP | vmcaster.appdb.egi.eu | AppDB image lists (used by cloudkeeper). |
8080/TCP | cephrgw01.ifca.es | Swift server hosting EGI images (used by cloudkeeper). |
Images listed in AppDB may be hosted in other servers besides
cephrgw01.ifca.es
. Check the specific VO-wide image lists for details.
This is an overview of the expected account permissions used in an OpenStack site, these accounts can be merged as needed for your deployment:
Component | Permission |
---|---|
cloud-info | Member of all projects supporting EGI VOs |
accounting | Member of all projects and able to list users (allowed to identity:list_users in keystone) |
cloud-keeper | Permission to manage the images for all the projects supporting EGI VOs |
Other users | Automatically created by Keystone and permission set as configured in the mappings |
Authentication and Authorization integration
Accounting integration
cloud info provider configuration
cloudkeeper and AppDB integration
Configuring GPU flavors
Summary of steps for configuring new VOs in OpenStack