Comment 4 for bug 2000179

Hi Neil,
Below is an example of the script we're using to invoke disk-image-create. Yes, we're running OpenStack, but I'm not aware of anything special with the hypervisor. I have to admit that I'm not intimately familiar with the inner working of DIB (I basically co-opted this build job from another team and customized it for my purposes). I've customized some elements and occasionally have had to fix things if the job breaks (such as external dependency changes, etc).

The primary purpose for the customization is to bootstrap our config mgmt system (ansible-pull) on the new image, provision ops accounts, etc.

###

IMG_NAME=CDN-Rocky-8

ELEMENTS_PATH=./elements \
  DIB_DEBUG_TRACE=1 \
  DIB_BOOTLOADER_DEFAULT_CMDLINE="nofb nomodeset vga=normal consoleblank=0" \
  DIB_CLOUD_INIT_DATASOURCES="ConfigDrive, OpenStack" \
  disk-image-create -u -a amd64 -t raw \
  --mkfs-options '-i 16384 -E stride=32,stripe_width=128' \
  -p rng-tools,qemu-guest-agent \
  -o images/${IMG_NAME} \
  rocky base vm selinux-permissive cloud-init-datasources \
  dib-custom ansible-pull ansible-pull-cloud-config