diskimage-builder

Go to file

Ian Wienand e82e0097a9 Use picked nodes for later cmd_* calls Currently the later cmd_* calls -- umount, cleanup, delete -- all recreate the node graph by parsing the config file using create_graph() There is some need, however, to have a sense of global state when building the node list. The problem is, this is a one time operation -- we do not want to rebuild that state for these later calls (see the "loaded" checks in proposed Ic3b805f9258128d5233b21ff25579c03487c7fcc). An insight here seems to be that these cmd_* calls do not actually want to re-parse the configuration file and rebuild the node list; they just want to walk the node list in reverse with the state as provided after cmd_create(). So, rather than re-creating the node list, we might as well just pickle it, save it to disk along side the state dictionary dump and reload it for cmd_*. After this, I think we can safely have PluginBase.__init__() be passed the state. We will now know that this will only be called once, during initial creation. Change-Id: I68840594a34af28d41d9522addcfd830bd203b97		2017-06-08 17:10:10 +10:00
bin	Allow ELEMENTS_DIR to be configurable	2017-03-14 09:57:10 -06:00
diskimage_builder	Use picked nodes for later cmd_* calls	2017-06-08 17:10:10 +10:00
doc	Remove ccache	2017-05-31 08:28:09 +10:00
releasenotes	Remove dracut-network element	2017-05-31 08:36:56 +10:00
tests	Add a keep-output flag for functional tests	2017-06-07 11:47:12 +10:00
.gitignore	Use sphinx warning-is-error	2017-03-14 14:49:49 +11:00
.gitreview	Update stackforge references to openstack	2013-08-17 22:58:26 -04:00
.testr.conf	Fix coverage report	2017-01-18 16:14:01 +11:00
babel.cfg	Make it possible for openstack-CI to run tests	2013-02-04 22:26:17 -08:00
bindep.txt	Use https in docs links	2017-06-05 22:54:23 +07:00
LICENSE	Fix copyrights for HP work.	2012-11-15 16:20:32 +13:00
pylint.cfg	Refactor: use lazy logging	2017-05-30 14:39:58 +10:00
README.rst	Use https in docs links	2017-06-05 22:54:23 +07:00
requirements.txt	Use networkx for digraph	2017-05-26 11:42:10 +10:00
setup.cfg	Use https in docs links	2017-06-05 22:54:23 +07:00
setup.py	Updated from global requirements	2017-03-13 19:30:19 +00:00
test-requirements.txt	Updated from global requirements	2017-06-06 12:13:28 +00:00
tox.ini	Add env var to dump config graph	2017-06-08 05:04:58 +00:00

README.rst

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
<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/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.