Go to file
Steve Baker 147641fc3e Set machine-id to uninitialized to trigger first boot
According to the systemd documentation[1], if /etc/machine-id is empty
it will be populated with a unique value, but not in a way which
triggers an actual first boot event (running units with
ConditionFirstBoot=yes set)

This change writes "uninitialized" to /etc/machine-id to ensure that
systemd-firstboot.service actually runs, and other units can use
first-boot-complete.target as a dependency to trigger on first boot.

Since /var/lib/dbus/machine-id is sometimes a symlink to
/etc/machine-id, it is truncated before writing to /etc/machine-id.

On older versions of systemd before first boot semantics were
formalised, any non-uuid value will trigger a new machine-id to be
generated, so "uninitialized" also works.

[1] https://www.freedesktop.org/software/systemd/man/machine-id.html#First%20Boot%20Semantics

Change-Id: I77c35e51a3da2e8a6b5a2c80d033a159b303c9af
2022-04-21 09:39:42 +12:00
.zuul.d Merge "Don't run functional tests on doc changes" 2022-02-09 09:21:06 +00:00
bin dib-lint: match text/x-script.python 2021-05-10 14:29:51 +10:00
diskimage_builder Set machine-id to uninitialized to trigger first boot 2022-04-21 09:39:42 +12:00
doc Update platform support to describe stable testing 2022-02-16 10:40:09 +11:00
playbooks tests: remove debootstrap install 2021-10-27 11:01:55 +11:00
releasenotes Merge "dhcp-all-interfaces: opt let NetworkManager doit." 2022-02-21 18:55:51 +00:00
roles containerfile: add support for Docker 2022-03-11 14:04:52 +11:00
tests Fix openSUSE images and bump them to 15.3 2022-01-28 02:18:47 -03:00
.gitignore Migrate from testr to stestr 2021-06-30 18:58:35 +05:30
.gitreview OpenDev Migration Patch 2019-04-19 19:26:30 +00:00
.stestr.conf Migrate from testr to stestr 2021-06-30 18:58:35 +05:30
bindep.txt yum-minimal: use DNF tools on host 2021-08-30 14:14:32 +10:00
LICENSE Fix copyrights for HP work. 2012-11-15 16:20:32 +13:00
lower-constraints.txt Drop lower version requirement for networkx 2021-10-05 12:55:43 +05:30
pylint.cfg Refactor: use lazy logging 2017-05-30 14:39:58 +10:00
README.rst Update readme to clarify an ubuntu bionic image is built 2020-06-07 19:53:46 +02:00
requirements.txt Drop lower version requirement for networkx 2021-10-05 12:55:43 +05:30
setup.cfg Remove py35 tox jobs 2021-10-20 09:38:47 +11:00
setup.py Cleanup py27 and docs support 2020-06-05 12:04:30 +02:00
test-requirements.txt Migrate from testr to stestr 2021-06-30 18:58:35 +05:30
tox.ini Migrate from testr to stestr 2021-06-30 18:58:35 +05:30

Image building tools for OpenStack
==================================

``diskimage-builder`` is a flexible suite of components for building a
wide-range of disk images, filesystem images and ramdisk images for
use with OpenStack.

This repository has the core functionality for building such images,
both virtual and bare metal. Images are composed using `elements`;
while fundamental elements are provided here, individual projects have
the flexibility to customise the image build with their own elements.

For example::

  $ DIB_RELEASE=bionic disk-image-create -o ubuntu-bionic.qcow2 vm ubuntu

will create a bootable Ubuntu Bionic based ``qcow2`` image.

``diskimage-builder`` is useful to anyone looking to produce
customised images for deployment into clouds. These tools are the
components of `TripleO <https://wiki.openstack.org/wiki/TripleO>`__
that are responsible for building disk images. They are also used
extensively to build images for testing OpenStack itself, particularly
with `nodepool
<https://docs.openstack.org/infra/system-config/nodepool.html>`__.
Platforms supported include Ubuntu, CentOS, RHEL and Fedora.

Full documentation, the source of which is in ``doc/source/``, is
published at:

* https://docs.openstack.org/diskimage-builder/latest/

Copyright
=========

Copyright 2012 Hewlett-Packard Development Company, L.P.
Copyright (c) 2012 NTT DOCOMO, INC.

All Rights Reserved.

Licensed under the Apache License, Version 2.0 (the "License"); you may
not use this file except in compliance with the License. You may obtain
a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
License for the specific language governing permissions and limitations
under the License.