fd1848282f
Despite having several issues (like missing firmware), it is still used by people. It seems that the only way to stop that is to remove it. Change-Id: I4baed8e8ab663c624dcc8d06ff0293d57b082abb
37 lines
1.3 KiB
ReStructuredText
37 lines
1.3 KiB
ReStructuredText
Components
|
|
==========
|
|
|
|
`disk-image-create [-a i386|amd64|armhf|arm64] -o filename {element} [{element} ...]`
|
|
|
|
Create an image of element {element}, optionally mixing in other elements.
|
|
Element dependencies are automatically included. Support for other
|
|
architectures depends on your environment being able to run binaries of
|
|
that platform and/or packages being available for the architecture. For
|
|
instance, to enable armhf on Ubuntu install the qemu-user-static package,
|
|
or to enable arm64 on CentOS setup the RDO aarch64 package repositories.
|
|
The default output format from disk-image-create is qcow2. To instead
|
|
output a tarball pass in "-t tar". This tarball could then be used as an
|
|
image for a linux container(see docs/docker.md).
|
|
|
|
`ramdisk-image-create -o filename {element} [{element} ...]`
|
|
|
|
Create a kernel+ ramdisk pair for running maintenance on bare metal
|
|
machines (deployment, inventory, burnin etc).
|
|
|
|
To generate kernel+ramdisk pair for use with nova-baremetal, use::
|
|
|
|
ramdisk-image-create -o deploy.ramdisk deploy-baremetal
|
|
|
|
Ironic no longer supports images created like this.
|
|
|
|
|
|
`element-info`
|
|
|
|
Extract information about elements.
|
|
|
|
`tests/run_functests.sh`
|
|
|
|
This runs a set of functional tests for diskimage-builder.
|
|
|
|
elements can be found in the top level elements directory.
|