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.

Difference between revisions of "Federated Cloud Virtual Machine Image Preparation"

From EGIWiki
Jump to navigation Jump to search
Line 26: Line 26:


= Image size and layout =
= Image size and layout =
The bigger the VM image, the longer it will take to be distributed to the cloud providers and the longer it will take to be started on the infrastructure. As a general rule, always try to make images as smaller as possible following these guidelines:
* '''DO NOT''' include (big) data in your image. There are other mechanisms for accessing data from your VM: [[HOWTO09 block and object storage]], or solutions like [https://www.gridpp.ac.uk/wiki/RALnonLHCCVMFS CVMFS]
* '''DO NOT''' include (big) empty space or swap in your image. Extra space for your computation or swap can be added with block storage once the VM is booted or using VM flavors that have extra disk allocated for your VM.
* '''DO NOT''' install un-needed software. Tools like GUI are of no-use on most cases since you will have no access to the graphical console of the VM.
* '''DO''' adjust the size of the images as much as possible. As stated above, empty space can be allocated on runtime easily
* '''DO''' use compressed image formats, like qcow2 or vmdk (used in OVA) to minimize the size of the image
* '''DO''' fill with 0 the empty disk space of your image so it can be compressed, e.g. using <code>dd if=/dev/zero of=/bigemptyfile bs=4096k; rm -rf /bigemptyfile</code>
For the disk layout is recommended to use a single partition (no /boot, no swap) and to avoid LVM. This will allow the cloud provider to easily resize your partition when instantiated and to modify files in it if needed.


= Contextualization and credentials =
= Contextualization and credentials =

Revision as of 23:40, 25 May 2017

Overview For users For resource providers Infrastructure status Site-specific configuration Architecture




Overview

Packaging your application in a custom VM image is a suggested solution in one of the following cases:

  • your particular OS flavor is not available into the existing image catalogue
  • installation of your application is very complex and time-consuming for being performed during contextualization
  • you want to reduce the number of 'moving-parts' of your software stack and follow an immutable infrastructure approach for deploying your application.

Custom VM images can be crafted in different ways. The two main possibilities are:

* start from scratch, creating a virtual machine, installing an OS and the software on top of it, then taking the virtual machine OS disk as custom image, or 
  • dump an existing disk from a VM or physical server and modify it, if needed, to run on a virtualization platform.

In this guide we will focus on the first option, because it tends to produce cleaner images and reduces the risks of hardware conflicts. Snapshotting may be also restricted by the cloud providers or by security policies.

Advantages

  • Possibility to build the virtual disk directly from a legacy machine, dumping the contents of the disk.
  • Possibility to speed-up the deployment for applications with complex and big installation packages. This because you do not need to install the application at startup, but the application is already included in the machine.

Disadvantages

  • Build a virtual disk directly from a legacy machine poses a set of compatibility issues with hardware drivers, which usually differs from a virtual and physical environment and even between different virtual environments.
  • You need to keep updated your machine. Outdated VM disk images may take long time to startup due to the need to download and install the latest OS updates.
  • If you are using special drivers or you are not packaging correctly the disk, your custom VM image may not run (or run slowly) on different cloud providers based on different virtualization technologies.
  • VM images images on public clouds are sometimes public, thus be aware of installing proprietary software on custom S images, since other users may be able to run the image or download it.
  • In general, the effort to implement this solution is higher than the basic contextualization.

Image size and layout

The bigger the VM image, the longer it will take to be distributed to the cloud providers and the longer it will take to be started on the infrastructure. As a general rule, always try to make images as smaller as possible following these guidelines:

  • DO NOT include (big) data in your image. There are other mechanisms for accessing data from your VM: HOWTO09 block and object storage, or solutions like CVMFS
  • DO NOT include (big) empty space or swap in your image. Extra space for your computation or swap can be added with block storage once the VM is booted or using VM flavors that have extra disk allocated for your VM.
  • DO NOT install un-needed software. Tools like GUI are of no-use on most cases since you will have no access to the graphical console of the VM.
  • DO adjust the size of the images as much as possible. As stated above, empty space can be allocated on runtime easily
  • DO use compressed image formats, like qcow2 or vmdk (used in OVA) to minimize the size of the image
  • DO fill with 0 the empty disk space of your image so it can be compressed, e.g. using dd if=/dev/zero of=/bigemptyfile bs=4096k; rm -rf /bigemptyfile

For the disk layout is recommended to use a single partition (no /boot, no swap) and to avoid LVM. This will allow the cloud provider to easily resize your partition when instantiated and to modify files in it if needed.

Contextualization and credentials

You can prepare fully customised Virtual Appliances and make them available to the sites supporting your VO.

  1. First, prepare a Virtual Machine Image (VMI) that encapsulates your application.
  2. Make the VMI available online, for example in the EGI Appliance Repository
  3. Register the VMI as a new Virtual Appliance in the EGI Applications Database
  4. Once your VA is published, inform your VO through Applications Database about it.
  5. Once your appliance is in the VO-wide image list, it will be deployed on the Federated Cloud sites of your VO.

Security

Workflow

Add-context-disk.png