Cloud Computing with Debian and its descendants

This page summaries on what to expect from Debian when it comes to compute clouds. The idea is that you get virtual instances of some self-assembled or off-shelf booting disk image. You start them, pay for their lifetime (likely), pay for the data that goes in or out, and stop them again.

Our fine distribution can play any role in here. It can

Debian cloud images in the cloud marketplaces

Cloud images have to deviate from the base Debian image due to nature of the environment in which they are running.
On pages listed below we're trying to explain differences between them:

Cloud images requirements

Building cloud images


These clouds don't have Debian images yet:

Cloud software already available in Debian

How to contribute

Join the Debian Cloud team or for Openstack this mailing list:

Note that, especially OpenStack, is BIG. We already have more than 50 binary packages of it in SID. So of course, we'd be more than happy to have help for its packaging/testing.

Reporting bugs

The Debian Cloud team uses the pseudo-package to track issues not bound to a specific package maintained in the team (for example, for the Amazon AWS images).

After reporting a bug against a Debian package, which has an impact on Debian images provided on or for clouds, please mark that the bug affects

Bugs are divided in four categories, by usertagging with the address ?

Bugs related to the images distributed in public clouds (outdatedness, lack of availability in all zones, etc.) can be usertagged ( More names of public clouds can of course be added, please keep the list of control commands below up to date) with:

The user categories were set up with the following control emails:


What is the default login name on the Debian AMIs?

A. The default user name is: admin. Authentication is ssh key based, therefore there is no password. admin is a privileged account with passwordless sudo to become root run:

sudo -i

CategoryVirtualization | CategorySystemAdministration