147641fc3e
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 |
||
---|---|---|
.zuul.d | ||
bin | ||
diskimage_builder | ||
doc | ||
playbooks | ||
releasenotes | ||
roles | ||
tests | ||
.gitignore | ||
.gitreview | ||
.stestr.conf | ||
bindep.txt | ||
LICENSE | ||
lower-constraints.txt | ||
pylint.cfg | ||
README.rst | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
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.