Building guest image¶

Overview¶

When Trove receives a command to create a database instance, it does so by launching a Nova instance based on the appropriate guest image that is stored in Glance. This document shows you the steps to build the guest images.

Note

For testing purpose, the Trove guest images of some specific databases are periodically built and published in http://tarballs.openstack.org/trove/images/ in Trove upstream CI.

Since Victoria release, Trove supports to run database service as docker container inside the guest instance, so that we don’t need to maintain multiple images for different database service. That’s the reason that you can see images for MySQL and MariaDB for Ussuri and Train releases in http://tarballs.openstack.org/trove/images/.

Additionally, if you install Trove in devstack environment, the guest image is created and registered in Glance automatically, unless it’s disabled by setting TROVE_ENABLE_IMAGE_BUILD=false in devstack local.conf file.

Since Yoga release, Trove sets default use_nova_server_config_drive to False. This change will break instance provisioning in some cases. To avoid that, make sure your DIB_CLOUD_INIT_DATASOURCES environment contains OpenStack to configure cloud-init to use metadata serivce. If cloud-init still doesn’t inject files after changing the environment, please ask your IaaS provider admin to enable OpenStack metadata service.

High Level Overview of a Trove Guest Instance¶

At the most basic level, a Trove Guest Instance is a Nova instance launched by Trove in response to a create command. This section describes the various components of a Trove Guest Instance.

Operating System¶

The officially supported operating system is Ubuntu, based on which the functional tests are running.

Docker¶

Since Vitoria, the database service is running as docker container inside the trove guest instance, so docker should be installed when building the guest image. This also means the trove guest instance should be able to pull docker images from the image registry(either from user port or trove management port), the related options for container images are:

[mysql]
docker_image
backup_docker_image

[postgresql]
docker_image
backup_docker_image

[mariadb]
docker_image
backup_docker_image

Trove Guest Agent¶

The guest agent runs inside the Nova instances that are used to run the database engines. The agent listens to the messaging bus for the topic and is responsible for actually translating and executing the commands that are sent to it by the task manager component for the particular datastore.

Trove guest agent is responsible for datastore docker container management.

Injected Configuration for the Guest Agent¶

When TaskManager launches the guest VM it injects config files into the VM, including:

/etc/trove/conf.d/guest_info.conf: Contains some information about the guest, e.g. the guest identifier, the tenant ID, etc.
/etc/trove/conf.d/trove-guestagent.conf: The config file for the guest agent service.

In addition to these config files, Trove supports to inject user data when launching the instance for customization on boot time, e.g. network configuration, hosts file settings, etc. The user data files are located inside the directory configured by cloudinit_location, for mysql, the file name is mysql.cloudinit

Persistent Storage, Networking¶

The database stores data on persistent storage on Cinder (if CONF.volume_support=True) or ephemeral storage on the Nova instance. The database service is accessible over the tenant network provided when creating the database instance.

The cloud administrator is able to config management networks(CONF.management_networks) that is invisible to the cloud tenants, but used for communication between database instance and the control plane services(e.g. the message queue).

Building Guest Images¶

Since Victoria release, a single trove guest image can be used for different datastores, it’s unnecessary to maintain different images for differnt datastores.

Build images using trovestack¶

trovestack is the recommended tooling provided by Trove community to build the guest images. Before running trovestack command:

git clone https://opendev.org/openstack/trove
cd trove/integration/scripts

The trove guest image could be created by running the following command:

$ ./trovestack build-image \
    ${guest_os} \
    ${guest_os_release} \
    ${dev_mode} \
    ${guest_username} \
    ${output_image_path}

Currently, only guest_os=ubuntu and guest_os_release=jammy are fully tested and supported.

Default input values:

guest_os=ubuntu
guest_os_release=jammy
dev_mode=true
guest_username=ubuntu
output_image_path=$HOME/images/trove-guest-${guest_os}-${guest_os_release}-dev.qcow2

dev_mode=true is mainly for testing purpose for trove developers and it’s necessary to build the image on the trove controller host, because the host and the guest VM need to ssh into each other without password. In this mode, when the trove guest agent code is changed, the image doesn’t need to be rebuilt which is convenient for debugging. Trove guest agent will ssh into the controller node and download trove code during the service initialization.
If dev_mode=false, the trove code for guest agent is injected into the image at the building time.
Some other global variables:
- HOST_SCP_USERNAME: Only used in dev mode, this is the user name used by guest agent to connect to the controller host, e.g. in devstack environment, it should be the stack user.
The image type can be easily changed by specifying a different image file extension, e.g. to build a raw image, you can specify $your-image-name.raw as the output_image_path parameter.

For example, in order to build a guest image for Ubuntu jammy operating system in development mode:

$ ./trovestack build-image ubuntu jammy true ubuntu

Once the image build is finished, the cloud administrator needs to register the image in Glance and register a new datastore or version in Trove using trove-manage command, e.g. after building an image for MySQL 5.7.29:

$ openstack image create trove-guest-ubuntu-jammy \
  --private \
  --disk-format qcow2 \
  --container-format bare \
  --tag trove --tag mysql \
  --file ~/images/trove-guest-ubuntu-jammy-dev.qcow2
$ openstack datastore version create 5.7.29 mysql mysql "" \
  --image-tags trove,mysql \
  --active --default
$ trove-manage db_load_datastore_config_parameters mysql 5.7.29 ${trove_repo_dir}/trove/templates/mysql/validation-rules.json

Note

The command trove-manage needs to run on Trove controller node.

If you see anything error or need help for the image creation, please ask help either in #openstack-trove IRC channel or sending emails to openstack-discuss@lists.openstack.org mailing list.

Use your own Docker Images¶

A Docker registry is a locally-hosted registry that replaces the need to pull from a public registry to get images. You can pull and push your own images when you use a private Docker registry. For Docker registry, please see Docker Registry Overview

A very simple registry may be deployed on the current host as follows:

sudo docker run -d --net=host -e REGISTRY_HTTP_ADDR=0.0.0.0:4000 --restart=always -v /opt/trove_registry/:/var/lib/registry --name registry registry:2

Before you build your own images, clone Trove’s git repository and define some environments. Please note: your registry address should be reachable by guest agent.

$ git clone --branch |TROVE_BRANCH_NAME| https://opendev.org/openstack/trove
$ YOUR_TROVE_SRC_DIR=${PWD}/trove
$ YOUR_REGISTRY_IP=<10.x.y.z>
$ YOUR_REGISTRY_PORT=4000
$ YOUR_REGISTRY_HTTP_ADDR=${YOUR_REGISTRY_IP}:${YOUR_REGISTRY_PORT}
$ YOUR_REGISTRY_REPO_NAME=trove-datastores

For mysql users, you can pull and push your own images to your own registry as follows:

$ DATABASE_NAME=mysql
$ DATABASE_VERSION=5.7
$ TROVE_DATABASE_IMAGE=${YOUR_REGISTRY_REPO_NAME}/${DATABASE_NAME}:${DATABASE_VERSION}
$ docker pull ${DATABASE_NAME}:${DATABASE_VERSION}
$ docker tag ${DATABASE_NAME}:${DATABASE_VERSION} ${YOUR_REGISTRY_HTTP_ADDR}/${TROVE_DATABASE_IMAGE}
$ docker push ${YOUR_REGISTRY_HTTP_ADDR}/${TROVE_DATABASE_IMAGE}

You can build and push your backup image to your own registry as follows:

$ cd ${YOUR_TROVE_SRC_DIR}/backup
$ TROVE_DATABASE_BACKUP_IMAGE=${YOUR_REGISTRY_HTTP_ADDR}/${YOUR_REGISTRY_REPO_NAME}/db-backup-${DATABASE_NAME}:${DATABASE_VERSION}
$ docker build -t ${TROVE_DATABASE_BACKUP_IMAGE} --build-arg DATASTORE=${DATABASE_NAME} --build-arg DATASTORE_VERSION=${DATABASE_VERSION} .
$ docker push ${TROVE_DATABASE_BACKUP_IMAGE}

For mariadb users, you can pull and push your own images to your own registry as follows:

$ DATABASE_NAME=mariadb
$ DATABASE_VERSION=10.4
$ TROVE_DATABASE_IMAGE=${YOUR_REGISTRY_HTTP_ADDR}/${YOUR_REGISTRY_REPO_NAME}/${DATABASE_NAME}:${DATABASE_VERSION}
$ docker pull ${DATABASE_NAME}:${DATABASE_VERSION}
$ docker tag ${DATABASE_NAME}:${DATABASE_VERSION} ${TROVE_DATABASE_IMAGE}
$ docker push ${TROVE_DATABASE_IMAGE}

You can build and push your backup image to your own registry as follows:

$ cd ${YOUR_TROVE_SRC_DIR}/backup
$ TROVE_DATABASE_BACKUP_IMAGE=${YOUR_REGISTRY_HTTP_ADDR}/${YOUR_REGISTRY_REPO_NAME}/db-backup-${DATABASE_NAME}:${DATABASE_VERSION}
$ docker build -t ${TROVE_DATABASE_BACKUP_IMAGE} --build-arg DATASTORE=${DATABASE_NAME} --build-arg DATASTORE_VERSION=${DATABASE_VERSION} .
$ docker push ${TROVE_DATABASE_BACKUP_IMAGE}

For postgres users, you can pull and push your own images to your own registry as follows:

$ DATABASE_NAME=postgres
$ DATABASE_VERSION=12
$ TROVE_DATABASE_IMAGE=${YOUR_REGISTRY_HTTP_ADDR}/${YOUR_REGISTRY_REPO_NAME}/${DATABASE_NAME}:${DATABASE_VERSION}
$ docker pull ${DATABASE_NAME}:${DATABASE_VERSION}
$ docker tag ${DATABASE_NAME}:${DATABASE_VERSION} ${TROVE_DATABASE_IMAGE}
$ docker push ${TROVE_DATABASE_IMAGE}

You can build and push your backup image to your own registry as follows:

$ cd ${YOUR_TROVE_SRC_DIR}/backup
$ TROVE_DATABASE_BACKUP_IMAGE=${YOUR_REGISTRY_HTTP_ADDR}/${YOUR_REGISTRY_REPO_NAME}/db-backup-${DATABASE_NAME}:${DATABASE_VERSION}
$ docker build -t ${TROVE_DATABASE_BACKUP_IMAGE} --build-arg DATASTORE=${DATABASE_NAME} --build-arg DATASTORE_VERSION=${DATABASE_VERSION} .
$ docker push ${TROVE_DATABASE_BACKUP_IMAGE}

After adding your own docker images to your docker registry, you should modify the configuration files and restart Trove processes.

/etc/trove/trove.conf:

[DEFAULT]
docker_insecure_registries = 10.x.y.z:4000

/etc/trove/trove-agent.conf:

[mysql]
docker_image = 10.x.y.z:4000/trove-datastores/mysql
backup_docker_image = 10.x.y.z:4000/trove-datastores/db-backup-mysql

[mariadb]
docker_image = 10.x.y.z:4000/trove-datastores/mariadb
backup_docker_image = 10.x.y.z:4000/trove-datastores/db-backup-mariadb

[postgres]
docker_image = 10.x.y.z:4000/trove-datastores/postgres
backup_docker_image = 10.x.y.z:4000/trove-datastores/db-backup-postgres

[guest_agent]
container_registry = 10.x.y.z:4000
container_registry_username =
container_registry_password =

Building guest image

Building guest image¶

Overview¶

High Level Overview of a Trove Guest Instance¶

Operating System¶

Docker¶

Trove Guest Agent¶

Injected Configuration for the Guest Agent¶

Persistent Storage, Networking¶

Building Guest Images¶

Build images using trovestack¶

Use your own Docker Images¶

trove 22.1.0.dev35

Page Contents