Differences between revisions 1 and 93 (spanning 92 versions)
Revision 1 as of 2008-12-23 18:33:54
Size: 1430
Comment:
Revision 93 as of 2021-05-07 18:11:33
Size: 4498
Comment: minor wording fixes
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
This page summarises on what to expect from Debian when it comes to compute clouds. Please refer to Wikipedia or other sources for details about what clouds are about. 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. #language en
<<TableOfContents>>
= Cloud Computing with Debian and its descendants =
Line 3: Line 5:
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.
Line 5: Line 7:
Our fine distribution can play any role in here. It can We support a number of different cloud-oriented use cases:
 * run as a guest OS on a number of different services
 * run the infrastructure that hosts a private cloud
 * run as a client, interacting with cloud services via APIs or other network services
Line 7: Line 12:
 * run as a cloud OS
 * run the infrastructure that runs the clouds
 * run as the joe the plumber's regular desktop OS that conctacts the cloud infrastructure with requests to control the clouds
Where to get more information
 * Eucalyptus - a free cloud infrastructure with Debian packages pending
 * Amazon - the EC2 that got the craze going
 * The Net At Large - various howtos that linking Debian with clouds
  * LinuxConfig.org
Who in the Debian community is interested in clouds and why?
Firstly, the extension from providing packages together is to use them together. Thus, the clouds, just like computational grids, may become a way to extend our current way we think about our community.
 * Debian-Med
  * sharing of administrative burden also for data that needs to be regularly updated
  * its Bioinformatics wing sees lots of parallel computing to be performed on clouds
This page, admittedly, is a stub, still. Please help improving it.
== Debian cloud images in the cloud marketplaces ==

  * [[/GoogleComputeEngineImage|Google Compute Engine]]: https://console.cloud.google.com/marketplace/browse?q=debian
  * [[Amazon EC2|Amazon AWS]]: [[https://aws.amazon.com/marketplace/seller-profile?id=4d4d4e5f-c474-49f2-8b18-94de9d43e2c0|Current releases]] or [[https://aws.amazon.com/marketplace/seller-profile?id=890be55d-32d8-4bc8-9042-2b4fd83064d5|Debian 9 (stretch) and older releases]]
  * [[/MicrosoftAzure|Microsoft Azure]]: https://azuremarketplace.microsoft.com/en-us/marketplace/apps?search=debian&page=1
  * OpenStack: https://cdimage.debian.org/cdimage/openstack/current-10/

Cloud images have to deviate from the base Debian image due to nature of the environment in which they are running.<<BR>> On pages listed below we're trying to explain differences between them:
 * [[Cloud/SystemsComparison|Debian images comparison (standard Debian vs cloud images)]]
 * [[Cloud/GoogleComputeEngineImage|Specifics of Debian on Google Compute Engine]]



=== Cloud images requirements ===
 * [[Teams/DPL/OfficialImages]] - list of requirements to call a image '''Official Debian Image'''

=== Building cloud images ===

 * The [[Teams/Cloud|Cloud team]] uses [[FAI]] to generate images. The toolchain and configs are available at [[https://salsa.debian.org/cloud-team/debian-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:
 * [[https://developer.ibm.com/linuxone/|IBM LinuxONE Community Cloud]]
 * Oracle cloud

----

== Cloud software already available in Debian ==

 * OpenStack

----

== How to contribute ==

Start by joining the [[Teams/Cloud|Debian Cloud team]] and/or the [[https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/openstack-devel|Openstack maintainers 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 [[Teams/Cloud|Debian Cloud team]] uses the [[DebianBug: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 [[https://www.debian.org/Bugs/server-control#affects|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:
 * <<mid(20121123012638.GA17190@falafel.plessy.net)>>
 * <<mid(20121123015033.GA3022@falafel.plessy.net)>>
 * <<mid(20160727143418.GG3906@bashton004)>>

----


== 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
}}}

----
## permalink 2021-04 https://www.debian.org/releases/bullseye/amd64/release-notes/ch-installing.en.html#cloud
CategoryPermalink | CategoryVirtualization | CategorySystemAdministration

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.

We support a number of different cloud-oriented use cases:

  • run as a guest OS on a number of different services
  • run the infrastructure that hosts a private cloud
  • 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

Start by joining the Debian Cloud team and/or the Openstack maintainers 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


CategoryPermalink | CategoryVirtualization | CategorySystemAdministration