Chapter 3. Working with overcloud images

Procedure

1. To obtain these images, install the rhosp-director-images and rhosp-director-images-ipa packages:

   $ sudo yum install rhosp-director-images rhosp-director-images-ipa

2. Extract the archives to the images directory on the stack user home, /home/stack/images:

   $ cd ~/images
   $ for i in /usr/share/rhosp-director-images/overcloud-full-latest-13.0.tar /usr/share/rhosp-director-images/ironic-python-agent-latest-13.0.tar; do tar -xvf $i; done

Procedure

1. Log in as the root user and create a temporary directory for the ramdisk:

   # mkdir ~/ipa-tmp
   # cd ~/ipa-tmp

2. Use the skipcpio and cpio commands to extract the ramdisk to the temporary directory:

   # /usr/lib/dracut/skipcpio ~/images/ironic-python-agent.initramfs | zcat | cpio -ivd | pax -r

3. Install an RPM package to the extracted contents:

   # rpm2cpio ~/RPMs/python-proliantutils-2.1.7-1.el7ost.noarch.rpm | pax -r

4. Recreate the new ramdisk:

   # find . 2>/dev/null | cpio --quiet -c -o | gzip -8  > /home/stack/images/ironic-python-agent.initramfs
   # chown stack: /home/stack/images/ironic-python-agent.initramfs

5. Verify that the new package now exists in the ramdisk:

   # lsinitrd /home/stack/images/ironic-python-agent.initramfs | grep proliant

Procedure

1. To create a virtual machine instance that uses the overcloud-full.qcow2 image, use the guestmount command:

   $ mkdir ~/overcloud-full
   $ guestmount -a overcloud-full.qcow2 -i --ro ~/overcloud-full

   You can review the contents of the QCOW2 image in ~/overcloud-full.

2. Alternatively, you can use virt-manager to create a virtual machine with the following boot options:

   • Kernel path: /overcloud-full.vmlinuz
   • initrd path: /overcloud-full.initrd
   • Kernel arguments: root=/dev/sda

Procedure

1. Register your image temporarily to enable Red Hat repositories relevant to your customizations:

   $ virt-customize --selinux-relabel -a overcloud-full.qcow2 --run-command 'subscription-manager register --username=[username] --password=[password]'
   [  0.0] Examining the guest ...
   [ 10.0] Setting a random seed
   [ 10.0] Running: subscription-manager register --username=[username] --password=[password]
   [ 24.0] Finishing off

2. Replace the [username] and [password] with your Red Hat customer account details. This runs the following command on the image:

   subscription-manager register --username=[username] --password=[password]

Procedure

1. Find a list of pool ID from your account subscriptions:

   $ sudo subscription-manager list

2. Choose a subscription pool ID and attach it to the image:

   $ virt-customize --selinux-relabel -a overcloud-full.qcow2 --run-command 'subscription-manager attach --pool [subscription-pool]'
   [  0.0] Examining the guest ...
   [ 12.0] Setting a random seed
   [ 12.0] Running: subscription-manager attach --pool [subscription-pool]
   [ 52.0] Finishing off

3. Replace the [subscription-pool] with your chosen subscription pool ID:

   subscription-manager attach --pool [subscription-pool]

   This adds the pool to the image so that you can enable the repositories.

4. Enable the Red Hat repositories:

   $ subscription-manager repos --enable=[repo-id]

Procedure

1. List the contents of the opendaylight.repo file:

   $ cat opendaylight.repo
   
   [opendaylight]
   name=OpenDaylight Repository
   baseurl=https://nexus.opendaylight.org/content/repositories/opendaylight-yum-epel-6-x86_64/
   gpgcheck=0

2. Copy the repository file on to the image:

   $ virt-customize --selinux-relabel -a overcloud-full.qcow2 --upload opendaylight.repo:/etc/yum.repos.d/
   [  0.0] Examining the guest ...
   [ 12.0] Setting a random seed
   [ 12.0] Copying: opendaylight.repo to /etc/yum.repos.d/
   [ 13.0] Finishing off

   The --upload option copies the repository file to /etc/yum.repos.d/ on the overcloud image.

Procedure

1. Source the stackrc file so that you can access director from the command line:

   $ source stackrc

2. Upload the default director images to use for deploying the overcloud:

   $ openstack overcloud image upload --image-path /home/stack/images/

   This uploads the following images into the director:

   • bm-deploy-kernel
   • bm-deploy-ramdisk
   • overcloud-full
   • overcloud-full-initrd

   • overcloud-full-vmlinuz

     The script also installs the introspection images on the directors PXE server.

3. View a list of the images in the CLI:

   $ openstack image list
   +--------------------------------------+------------------------+
   | ID                                   | Name                   |
   +--------------------------------------+------------------------+
   | 765a46af-4417-4592-91e5-a300ead3faf6 | bm-deploy-ramdisk      |
   | 09b40e3d-0382-4925-a356-3a4b4f36b514 | bm-deploy-kernel       |
   | ef793cd0-e65c-456a-a675-63cd57610bd5 | overcloud-full         |
   | 9a51a6cb-4670-40de-b64b-b70f4dd44152 | overcloud-full-initrd  |
   | 4f7e33f4-d617-47c1-b36f-cbe90f132e5d | overcloud-full-vmlinuz |
   +--------------------------------------+------------------------+

   This list does not show the introspection PXE images (agent.*). Director copies these files to /httpboot.

   [stack@host1 ~]$ ls /httpboot -l
   total 151636
   -rw-r--r--. 1 ironic ironic       269 Sep 19 02:43 boot.ipxe
   -rw-r--r--. 1 root   root         252 Sep 10 15:35 inspector.ipxe
   -rwxr-xr-x. 1 root   root     5027584 Sep 10 16:32 agent.kernel
   -rw-r--r--. 1 root   root   150230861 Sep 10 16:32 agent.ramdisk
   drwxr-xr-x. 2 ironic ironic      4096 Sep 19 02:45 pxelinux.cfg