tripleo-docs/doc/source/advanced_deployment/build_single_image.rst
Ben Nemec 6c31de6bc2 Streamline the basic deployment flow
There were a couple of non-basic steps that got included in the
mainline deployment docs.  Let's move those to the advanced
section and leave links in the basic flow so they're easy to find
for people who want them.

Co-Authored-By: Swapnil Kulkarni <me@coolsvap.net>
Change-Id: Id8c9a689060df85b5ee87390a5510a569236b553
2016-04-04 14:54:33 +05:30

1.3 KiB

Building a Single Image

The openstack overcloud image build --all command builds all the images needed for an overcloud deploy. However, you may need to rebuild a single one of them. Use the following commands if you want to do it:

openstack overcloud image build --type {agent-ramdisk|deploy-ramdisk|fedora-user|overcloud-full}

If the target image exist, this commands ends silently. Make sure to delete a previous version of the image to run the command as you expect.

Moreover, you can build the image with an extra element of your choice using the --builder-extra-args argument:

openstack overcloud image build --type overcloud-full \
    --builder-extra-args overcloud-network-midonet

Note

Make sure the element is available in the $ELEMENTS_PATH environment variable

Uploading the New Single Image

After the new image is built, it can be uploaded using the same command as before, with the --update-existing flag added:

openstack overcloud image upload --update-existing

Note that if the new image is a ramdisk, the Ironic nodes need to be re-configured to use it. This can be done by re-running:

openstack overcloud configure boot

Now the new image should be fully ready for use by new deployments.