No description
9cd35c36e4
Tucked away in systemd-udev-settle.service is the following comment # This service can dynamically be pulled-in by legacy services which # cannot reliably cope with dynamic device configurations, and # wrongfully expect a populated /dev during bootup. The info that the growroot script is querying is populated via udev, particularly the blkid bits of [1]. This creates a race-condition where sometimes udev has been triggered and the rules have applied and sometimes not. Obviously in the first case, the root disk is not grown correctly. systemd-udev-settle is mostly disabled on distros because it can cause an increase in boot-time for systems with lots of disks; this is not our situation so it makes basically no difference. That said, I will investigate if some systemd people know even better ways to do this (possibly the service should depend on block .device targets in systemd, and then filter out and only apply to the root disk?) [1] https://github.com/systemd/systemd/blob/master/rules/60-persistent-storage.rules#L66 Change-Id: I453e3afcd953dfc29ab6c42ddc81e940cfa70ee0 |
||
|---|---|---|
| bin | ||
| diskimage_builder | ||
| doc/source | ||
| elements | ||
| lib | ||
| tests | ||
| .gitignore | ||
| .gitreview | ||
| .testr.conf | ||
| babel.cfg | ||
| LICENSE | ||
| MANIFEST.in | ||
| 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=trusty disk-image-create -o ubuntu-trusty.qcow2 vm ubuntu
will create a bootable Ubuntu Trusty 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
<http://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:
* http://docs.openstack.org/developer/diskimage-builder/
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.