diskimage-builder/diskimage_builder/elements/debian-upstart/README.rst

==============
debian-upstart
==============
By default Debian will use sysvinit for booting. If you want to experiment
with Upstart, or have need of it due to a need for upstart jobs, this
element will build the image with upstart as the init system.

Note that this works with the ``debian`` element, not the
``debian-minimal`` element.

.. element_deps::
Create docs site containing element READMEs We currently do not have the ability to create a docs site which outlines all the elements. Change-Id: I77ccf61e0c4b1509b3e7ce9b8f15ea5ccfd50d9b 2015-02-07 10:30:02 +00:00			`==============`
			`debian-upstart`
			`==============`
Add debian-upstart for experimenting with upstart Upstart support in Debian is somewhat experimental, but having it would be especially useful for TripleO which already generates upstart scripts which will work fairly well on Debian based systems. Change-Id: I267da5ae7bc4a484fac152a14963d96ca2ad2693 2014-01-13 20:54:42 +00:00			`By default Debian will use sysvinit for booting. If you want to experiment`
			`with Upstart, or have need of it due to a need for upstart jobs, this`
			`element will build the image with upstart as the init system.`
Semi-automatic doc generation of element dependency Currently there is no description of dependencies in the generated documentation of the elements: therefore a user of an element does not know which other elements are automatically included and e.g. which configuration options are available. In addition there are some copy&pastes of parts of the README.rst scattered thought different Ubuntu and Debian specific elements. This patch adds a semi-automatic generation of dependency information of all elements. Nevertheless these are not automatically included. The author of the element's README.rst can decide if and where the dependency information should appear and can use the descriptor .. element_deps:: for this. This patch adds the dependency information for some Debian and Ubuntu patches - and creates the base for later removing the duplicated parts. A call is added to element_dependencies._find_all_elements() to populate reverse dependencies for Element objects. (This is a reworking of I31d2b6050b6c46fefe37378698e9a330025db430 for the feature/v2 branch) Change-Id: Iebb83916fed71565071246baa550849eef40560b 2017-01-19 21:00:21 +00:00
Install systemd earlier for Stretch Debian Stretch released as stable recently, and the init system is less tightly specified in the base dependencies (for some info, see [1]). It seems, probably unintentionally, that in the previous release systemd-sysv was brought in by debootstrap, but that is no longer happening. Add systemd as an early dependency of debian-minimal. Remove the package-installs.yaml as that happens too late (other things need to know the init system to write out service files, etc and probe for systemd utils before package-installs). As mentioned, I do not believe the "only install systemd on testing" idea was actually working here, because it was being brought in during the initial debootstrap. Update some documentation to explain what's going on [1] https://lists.debian.org/debian-boot/2015/05/msg00156.html Change-Id: Id67c0cf08728407d234976f9807d3bd71d12f758 2017-06-19 01:35:14 +00:00			Note that this works with the ``debian`` element, not the
			``debian-minimal`` element.

Semi-automatic doc generation of element dependency Currently there is no description of dependencies in the generated documentation of the elements: therefore a user of an element does not know which other elements are automatically included and e.g. which configuration options are available. In addition there are some copy&pastes of parts of the README.rst scattered thought different Ubuntu and Debian specific elements. This patch adds a semi-automatic generation of dependency information of all elements. Nevertheless these are not automatically included. The author of the element's README.rst can decide if and where the dependency information should appear and can use the descriptor .. element_deps:: for this. This patch adds the dependency information for some Debian and Ubuntu patches - and creates the base for later removing the duplicated parts. A call is added to element_dependencies._find_all_elements() to populate reverse dependencies for Element objects. (This is a reworking of I31d2b6050b6c46fefe37378698e9a330025db430 for the feature/v2 branch) Change-Id: Iebb83916fed71565071246baa550849eef40560b 2017-01-19 21:00:21 +00:00			`.. element_deps::`