Differences between revisions 89 and 90
Revision 89 as of 2020-04-20 21:42:03
Size: 4445
Comment: Update AWS Marketplace links
Revision 90 as of 2020-04-20 21:49:53
Size: 4463
Comment: minor language tweaks...
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
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. This page summaries on what to expect from Debian when it comes to compute clouds, in which virtual machines can be quickly provisioned via service calls, configured and manipulated through various manual or automated means, and terminated when no longer needed.
Line 10: Line 10:
 * run as the joe the plumber's regular desktop OS that contacts the cloud infrastructure with requests to control the clouds  * run as a client, interacting with cloud services via APIs or other network services
Line 36: Line 36:
These clouds don't have Debian images yet: These clouds don't have Debian images yet, but users of these services are invited to work with the cloud team to add support:

Cloud Computing with Debian and its descendants

This page summaries on what to expect from Debian when it comes to compute clouds, in which virtual machines can be quickly provisioned via service calls, configured and manipulated through various manual or automated means, and terminated when no longer needed.

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

  • run as a cloud OS
  • run the infrastructure that runs the clouds
  • run as a client, interacting with cloud services via APIs or other network services

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

Unsupported

These clouds don't have Debian images yet, but users of these services are invited to work with the cloud team to add support:


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 cloud.debian.org 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 cloud.debian.org.

Bugs are divided in four categories, by usertagging with the address ?cloud.debian.org@packages.debian.org:

  • image (Machine Images)

  • infrastructure

  • documentation

  • package

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:

  • aws (for Amazon Web Services)

  • azure (for Microsoft Azure)

  • gce (for Google Compute Engine)

  • openstack (for Openstack)

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


FAQ

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