Differences between revisions 8 and 10 (spanning 2 versions)
Revision 8 as of 2016-04-06 15:52:27
Size: 3441
Editor: ?DarrellFixler
Comment: typo/translation fixes
Revision 10 as of 2016-07-22 20:07:48
Size: 2797
Editor: ?kuLa
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:

The goal of this page is to list the differences, and organize which and how to resolve them. Here, ''standard'' refers to Debian systems installed with DebianInstaller with the default settings, following the instructions in http://www.debian.org/releases/stable/installmanual.
The goal of this page is to list the differences, and organize which and how to
resolve them. Here, ''standard'' refers to Debian systems installed with
DebianInstaller with the default settings, following the instructions in
http://www.debian.org/releases/stable/installmanual.
Line 6: Line 8:
if any, do not prevent us to claim that the cloud images are genuine Debian systems (DebianBug:706052).

== Availability of installer source code ==

 * Standard systems are prepared with DebianInstaller, which is packaged in the Debian archive. TODO: check if the source code of all scripts used to prepare the binary images of DebianInstaller (install CDs, etc.) is also packaged.
 * AWS and GCE images are prepared with {{{build-debian-cloud}}}, to be packaged (DebianBug:693198). TODO: How about Azure images ?
if any, do not prevent us to claim that the cloud images are genuine Debian
systems (DebianBug:706052).
Line 14: Line 12:
 * Debian does not distribute binary images of standard systems, but distributes
installation media with a binary image of DebianInstaller.
 * AWS, Azure and GCE images are available on the respective public clouds.
 * Distribution of a generic cloud image in the debian archive is under
discussion.
Line 15: Line 18:
 * Debian does not distribute binary images of standard systems, but distributes installation media with a binary image of DebianInstaller.
 * AWS, Azure and GCE images are available on the respective public clouds.
 * Distribution of a generic cloud image in the debian archive is under discussion.
 * TODO: How about the Debian live images ?

== Contents (Stable systems) ==

=== Area ===

 * All: only the ''main'' area is enabled by default (not ''contrib'' or ''non-free'').

=== Distribution ===

 * All: only the ''stable'' distribution is used. Discussions are under way (independently for DebianInstaller and cloud images) to list stable backports by default (installation of backport packages will still be manual, but updates become automatic).

=== Kernel ===

 * Default for standard and AWS.
 * Custom for Azure, GCE and Oracle Compute.
 * TODO: what is the kernel on Azure and in Debian live systems ?

=== Packages ===

 * Standard systems contain all packages installed by {{{debootstrap}}}, plus the ones installed by {{{tasksel}}}.
 * Cloud systems contain all the packages installed by {{{debootstrap}}}. Addition of extra packages such as {{{less}}} and {{{psmisc}}} are discussed in (DebianBug:696154). Addition of {{{cloud-init}}} from {{{wheezy-backports}}} is discussed on the mailing list.
 * GCE images have third-party packages installed google-startup-scripts, google-compute-daemon, image-bundle (Free software).
 * TODO: How about the Debian live images ?

=== Non-packaged programs ===

 * Standard installations: none.
 * {{{build-debian-cloud}}} adds some startup scripts to the images it produces.
 * GCE images: Two unpackaged command-line utilities, see [[Cloud/GoogleComputeEngineImage]].
 * TODO: Azure and Live ?

== Default account ==

 * No default account name on standard images
 * {{{admin}}} on AWS
 * {{{opc}}} on Oracle Compute
 * No default account name on GCE images (see https://cloud.google.com/compute/docs/linux-quickstart)
 * TODO: how about Azure and Debian live images ?

== Identifiers ==

 * AWS:
  * 379101102735/debian-''codename''-''architecture''-''YYYYMMDD''
  * 379101102735 is the account ID from which the images are produced.
 * Azure: ?
 * GCE:
  * debian-''N''-''codename''-v''YYYYMMDD''
  * Debian GNU/Linux N.N (codename) built on YYYY-MM-DD
  * Project ID: debian-cloud
 * Oracle Compute:
  * ''Not released yet'' (Jan 2016).
|| || Debian CD (standard image)|| AWS || Azure || GCP || Openstack || Oracle ||
|| Tool for generating images || DebianInstaller || [[https://tracker.debian.org/pkg/bootstrap-vz|bootstrap-vz]] || [[https://tracker.debian.org/pkg/openstack-debian-images|openstack-debian-images]] || [[https://tracker.debian.org/pkg/bootstrap-vz|bootstrap-vz]] || [[https://tracker.debian.org/pkg/openstack-debian-images|openstack-debian-images]] || unknown ||
|| Archive components available by default || main || main || main || main || main || main ||
|| Images available for Debian releases (suites) ||<:-6> stable<<FootNote(Discussions are under way (independently for DebianInstaller and cloud images) to list stable backports by default (installation of backport packages will still be manual, but updates become automatic))>> ||
|| Kernel || default || default || custom || custom || unknown || custom ||
|| Installed packages (default image) || packages with priority '''important''' (''debootstrap'' and higher (plus user choice if any [''tasksel'']) || packages from '''debootstrap''' plus: <<BR>>'''cloud-init''' || unknown || packages from '''debootstrap''' plus:<<BR>>'''google-startup-scripts''', <<BR>>'''google-compute-daemon''', <<BR>>'''image-bundle''' || unknown || unknown ||
|| Packages installed from outside of Debian archive || none || none || none || see<<FootNote([[Cloud/GoogleComputeEngineImage]])>> || unknown || unknown ||
|| Default system account || none || admin || unknown || none<<FootNote(https://cloud.google.com/compute/docs/linux-quickstart)>> || unknown || opc ||
|| Images description schema || debian-<release version>-<architecture>-<ccd numbner|desktop configuration>.iso || 379101102735<<FootNote(AMI owner AWS account ID)>>/debian-<codename>-<architecture>-<YYYYMMDD> || unknown || debian-<<release version>>-<<codename>>-v<<YYYYMMDD>> || unknown || ''Not released yet'' (Jan 2016) ||

List of differences between standard and cloud systems

The goal of this page is to list the differences, and organize which and how to resolve them. Here, standard refers to Debian systems installed with DebianInstaller with the default settings, following the instructions in http://www.debian.org/releases/stable/installmanual.

Eventually, we should converge on a consensus that the remaining differences, if any, do not prevent us to claim that the cloud images are genuine Debian systems (706052).

Distribution Binary images

  • Debian does not distribute binary images of standard systems, but distributes

installation media with a binary image of DebianInstaller.

  • AWS, Azure and GCE images are available on the respective public clouds.
  • Distribution of a generic cloud image in the debian archive is under

discussion.

Debian CD (standard image)

AWS

Azure

GCP

Openstack

Oracle

Tool for generating images

DebianInstaller

bootstrap-vz

openstack-debian-images

bootstrap-vz

openstack-debian-images

unknown

Archive components available by default

main

main

main

main

main

main

Images available for Debian releases (suites)

stable1

Kernel

default

default

custom

custom

unknown

custom

Installed packages (default image)

packages with priority important (debootstrap and higher (plus user choice if any [tasksel])

packages from debootstrap plus:
cloud-init

unknown

packages from debootstrap plus:
google-startup-scripts,
google-compute-daemon,
image-bundle

unknown

unknown

Packages installed from outside of Debian archive

none

none

none

see2

unknown

unknown

Default system account

none

admin

unknown

none3

unknown

opc

Images description schema

debian-<release version>-<architecture>-<ccd numbner|desktop configuration>.iso

3791011027354/debian-<codename>-<architecture>-<YYYYMMDD>

unknown

debian-<<release version>>-<<codename>>-v<<YYYYMMDD>>

unknown

Not released yet (Jan 2016)

  1. Discussions are under way (independently for DebianInstaller and cloud images) to list stable backports by default (installation of backport packages will still be manual, but updates become automatic) (1)

  2. Cloud/GoogleComputeEngineImage (2)

  3. https://cloud.google.com/compute/docs/linux-quickstart (3)

  4. AMI owner AWS account ID (4)