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.
Federated Cloud Virtual Machine Image Preparation
| Overview | For users | For resource providers | Infrastructure status | Site-specific configuration | Architecture |
Overview
Advantages
Disadvantages
Image size and layout
Contextualization and credentials
You can prepare fully customised Virtual Appliances and make them available to the sites supporting your VO.
- First, prepare a Virtual Machine Image (VMI) that encapsulates your application.
- There are several methods for preparing the image, check the VMI guide for tips
- We use packer with VirtualBox, which can run easily on your computer
- Beware images should not contain any credentials, use cloud-init and follow hardening guidelines.
- Make the VMI available online, for example in the EGI Appliance Repository
- See How can I upload a VM image to the EGI FedCloud repository entry in the FAQ
- If you don't use the EGI Appliance Repository, please ensure that the server used has enough bandwidth to allow sites download the image.
- Register the VMI as a new Virtual Appliance in the EGI Applications Database
- Once your VA is published, inform your VO through Applications Database about it.
- Check the guide for managing VA versions
- VO-wide image lists can be managed by users that have the VO Manager, VO Expert or VO deputy roles within the VO.
- Once your appliance is in the VO-wide image list, it will be deployed on the Federated Cloud sites of your VO.
Security
Workflow
