openstack/trove
Code Issues Proposed changes

[Doc] Improve building Trove guest image instruction

Browse Source 
Change-Id: I96c9c70aee9363880c0ba9372a347a80fa930e14
This commit is contained in:
Lingxian Kong
2020-09-21 17:23:45 +12:00
parent 7537b3255e
commit d75151bbe4
1 changed files with 26 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

29
doc/source/admin/building_guest_images.rst
View File

@@ -54,9 +54,26 @@ functional tests are running.
Docker
------
Since Vitoria release, all the datastore services are installed by docker
container inside the Trove instance, so docker should be installed when
building the guest image.
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:
.. code-block:: ini
[mysql]
docker_image
backup_docker_image
[postgresql]
docker_image
backup_docker_image
[mariadb]
docker_image
backup_docker_image
-----------------
Trove Guest Agent
@@ -81,6 +98,12 @@ VM, including:
* ``/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
------------------------------