blob: d4bb78f7f653c1e67f5b9280672b3e0a1b214828 [file] [log] [blame]
Mohammed Nasera5467342024-04-30 00:34:16 -04001####################
2Glance Configuration
3####################
4
5Glance, the image service used by OpenStack, can be configured to use different
6storage backends depending on your deployment needs. This document provides
7guidance on setting up Glance with either the integrated Ceph cluster that
8comes with Atmosphere or using Cinder as a storage backend, with additional
9details for configurations that require special handling.
10
11****
12Ceph
13****
14
15The Atmosphere deployment includes a pre-configured Ceph cluster that is
16ready to use with Glance, requiring no additional configuration steps. This
17setup is recommended for most users as it provides a seamless and integrated
18storage solution.
19
20******
21Cinder
22******
23
24To configure Glance to use Cinder as its storage backend, which allows for
25managing images as block storage volumes, apply the following configuration:
26
27.. code-block:: yaml
28
29 glance_helm_values:
30 storage: cinder
31 conf:
32 glance:
33 glance_store:
34 stores: cinder
35 default_store: cinder
vexxhost-bot5049bc32024-05-11 23:28:47 +010036 image_format:
Mohammed Nasera5467342024-04-30 00:34:16 -040037 disk_formats: raw
38
39This configuration sets Cinder as the default and only storage backend for
40Glance, with images stored in the ``raw`` disk format. The configuration
41above will use the Cinder default volume type for image storage.
42
43If you want to use a specific volume type, you can merge the following with
44the above configuration:
45
46.. code-block:: yaml
47
48 glance_helm_values:
49 conf:
50 glance:
51 glance_store:
52 cinder_volume_type: slow
53
54Vendor-Specific Configurations
55==============================
56
57Depending on the vendor you use for your Cinder storage backend, you may need
58to make some additional changes to accommodate specific requirements or
59capabilities offered by that vendor. Below are the configuration details for
60common providers.
61
62StorPool
63--------
64
65For deployments utilizing StorPool as the storage backend, additional
66configuration settings are necessary to ensure proper integration and
67functionality. You can merge the following with the base Cinder configuration
68above:
69
70.. code-block:: yaml
71
72 glance_helm_values:
73 pod:
74 useHostNetwork:
75 api: true
76 mounts:
77 glance_api:
78 volumeMounts:
79 - name: etc-storpool-conf
80 mountPath: /etc/storpool.conf
81 readOnly: true
82 - name: etc-storpool-conf-d
83 mountPath: /etc/storpool.conf.d
84 readOnly: true
85 volumes:
86 - name: etc-storpool-conf
87 hostPath:
88 type: File
89 path: /etc/storpool.conf
90 - name: etc-storpool-conf-d
91 hostPath:
92 type: Directory
93 path: /etc/storpool.conf.d
94
95These adjustments include network settings and mounting necessary configuration
96files into the Glance API pod to interact efficiently with the StorPool backend.