4f9131e692
This makes the docs site a lot more manageable and begins moving us in the direction of separate user and developer docs. Change-Id: I1650ef9d5be1733b8bc118d99090143cb5b06102
30 lines
1.4 KiB
ReStructuredText
30 lines
1.4 KiB
ReStructuredText
Componenets
|
|
===========
|
|
|
|
* disk-image-create [-a i386|amd64|armhf] -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. For instance, to enable armhf on Ubuntu install the qemu-user-static
|
|
package. 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
|
|
|
|
To generate kernel+ramdisk pair for use with ironic, use
|
|
ramdisk-image-create -o deploy.ramdisk deploy-ironic
|
|
|
|
* disk-image-get-kernel filename : **DEPRECATED** Extract the appropriate
|
|
kernel and ramdisk to use when doing PXE boot using filename as the image
|
|
for a machine. Consider using the `baremetal` element, rather than this tool.
|
|
|
|
* elements can be found in the top level elements directory.
|
|
|
|
* element-info : Extract information about elements.
|