For the OpenStack Pike TripleO undercloud download or create the overcloud Introspection and deploy images

Download or create the overcloud images at the OpenStack Tripleo Pike Undercloud for the overcloud introspection and deployment

Creation of the overcloud images and uploading the same to the undercloud.

Before import and introspection of the VirtualMachines for the overcloud, the overcloud images have to be there on the undercloud system 

To have the latest overcloud images you can download the same from the RDO delorean or the CBS (CentOS) repos

example is here 

wget https://images.rdoproject.org/master/delorean/current-tripleo-rdo/overcloud-full.tar

get the ironic-python-agent also from the same location 

wget https://images.rdoproject.org/master/delorean/current-tripleo-rdo/ironic-python-agent.tar

Extract all these using tar. 

Go to the folder on the undercloud system where these images have been downloaded. Then run 'tar -xvf <TARFILE>' for each of the tar files downloaded.


The alternative to downloading the images is to build the images on the undercloud system.

Please note that we will be using here the alternative way of creation of the overcloud images as mentioned in the next section.


ref: https://docs.openstack.org/tripleo-docs/latest/install/basic_deployment/basic_deployment_cli.html

Enable the repos as per the openstack release

export DIB_YUM_REPO_CONF="/etc/yum.repos.d/delorean*"
export STABLE_RELEASE="pike"
export DIB_YUM_REPO_CONF="$DIB_YUM_REPO_CONF /etc/yum.repos.d/tripleo-centos-ceph-jewel.repo"


Build the overcloud images using.


openstack overcloud image build


OUTPUT Truncated
.
.
.
.
2018-04-03 01:19:36.842 | dib-run-parts --------------------- END PROFILING ---------------------
2018-04-03 01:19:36.997 | Unmount /tmp/dib_build.rls9b9ZY/mnt/sys
2018-04-03 01:19:37.015 | Unmount /tmp/dib_build.rls9b9ZY/mnt/proc
2018-04-03 01:19:37.029 | Unmount /tmp/dib_build.rls9b9ZY/mnt/dev/pts
2018-04-03 01:19:37.042 | Unmount /tmp/dib_build.rls9b9ZY/mnt/dev
2018-04-03 01:19:38.327 | INFO diskimage_builder.block_device.blockdevice [-] Getting value for [image-path]
2018-04-03 01:19:39.627 | INFO diskimage_builder.block_device.level3.mount [-] Called for [mount_mkfs_root]
2018-04-03 01:19:39.627 | INFO diskimage_builder.block_device.utils [-] Calling [sudo sync]
2018-04-03 01:19:39.665 | INFO diskimage_builder.block_device.utils [-] Calling [sudo fstrim --verbose /tmp/dib_build.rls9b9ZY/mnt/]
2018-04-03 01:19:39.680 | INFO diskimage_builder.block_device.utils [-] Calling [sudo umount /tmp/dib_build.rls9b9ZY/mnt/]
2018-04-03 01:19:39.957 | INFO diskimage_builder.block_device.level0.localloop [-] loopdev detach
2018-04-03 01:19:39.970 | INFO diskimage_builder.block_device.level0.localloop [-] Successfully detached [/dev/loop0]
2018-04-03 01:19:41.288 | INFO diskimage_builder.block_device.blockdevice [-] Removing temporary state dir [/tmp/dib_build.rls9b9ZY/states/block-device]
(undercloud) [stack@pike ~]$


NOTE

This builds the overcloud images as per the default YAML. If you want to specify the YAML configuration to build the overcloud images your own way, you can have a look at the 

(see for Pike)

openstack help overcloud image build 

The default Config YAML files for the creation of the overcloud images are there are located at /usr/share/openstack-tripleo-common/

Go to the Main page of the OpenStack Tripleo on KVM : Openstack Pike TripleO undercloud deployment with overcloud controller HA on KVM (libvirt)