openstack/ironic
Code Issues Proposed changes

Docs: specify what to do with the created images

Browse Source 
Also make the Glance image docs easier to navigate.

Change-Id: Ib7f891c2086c556cffca94eb0e37db87b6a68e7b
This commit is contained in:
Dmitry Tantsur 2022-06-22 10:51:15 +02:00 committed by Jay Faulkner
parent 39a7f58002
commit 19daab6bae
1 changed files with 52 additions and 40 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
doc/source/install/configure-glance-images.rst
View File

@ -1,16 +1,15 @@
.. _image-requirements: .. _image-requirements:
Add images to the Image service Add images to the Image service
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ===============================
#. Build or download the user images as described in Instance (end-user) images
:doc:`/user/creating-images`. ~~~~~~~~~~~~~~~~~~~~~~~~~~
#. Add the user images to the Image service Build or download the user images as described in :doc:`/user/creating-images`.
Load all the images created in the below steps into the Image service, Load all the created images into the Image service, and note the image UUIDs in
and note the image UUIDs in the Image service for each one as it is the Image service for each one as it is generated.
generated.
- For *whole disk images* just upload the image: - For *whole disk images* just upload the image:
@ -63,6 +62,9 @@ Add images to the Image service
kernel_id=$MY_VMLINUZ_UUID --property \ kernel_id=$MY_VMLINUZ_UUID --property \
ramdisk_id=$MY_INITRD_UUID --file my-image.qcow2 ramdisk_id=$MY_INITRD_UUID --file my-image.qcow2
Deploy ramdisk images
~~~~~~~~~~~~~~~~~~~~~
#. Build or download the deploy images #. Build or download the deploy images
The deploy images are used initially for preparing the server (creating disk The deploy images are used initially for preparing the server (creating disk
@ -90,3 +92,13 @@ Add images to the Image service
--file ironic-python-agent.initramfs --file ironic-python-agent.initramfs
Store the image UUID obtained from the above step as ``DEPLOY_INITRD_UUID``. Store the image UUID obtained from the above step as ``DEPLOY_INITRD_UUID``.
#. Configure the Bare Metal service to use the produced images. It can be done
per node as described in :doc:`enrollment` or globally in the configuration
file:
.. code-block:: ini
[conductor]
deploy_kernel = <insert DEPLOY_VMLINUZ_UUID>
deploy_ramdisk = <insert DEPLOY_INITRD_UUID>