This commit does the following: - sets all shell prompts in code-blocks to the root prompt - uses shell-session code-block since the shell prompt was being treated as a comment - links configure-aodh.rst in configure.rst (running tox was complaining that this file wasn't being linked anywhere) - other minor cleanup Change-Id: I9e3ac8bb0cabd1cc17952cfd765dbb0d8f7b6fa2
3.0 KiB
Home OpenStack-Ansible Installation Guide
Configuring the Image service
In an all-in-one deployment with a single infrastructure node, the Image service uses the local file system on the target host to store images. When deploying production clouds we recommend backing Glance with a swift backend or some form or another of shared storage.
The following procedure describes how to modify the
/etc/openstack_deploy/user_variables.yml file to enable
Cloud Files usage.
Change the default store to use Object Storage (swift), the underlying architecture of Cloud Files:
glance_default_store: swiftSet the appropriate authentication URL:
glance_swift_store_auth_address: https://127.0.0.1/v2.0Set the swift account credentials:
# Replace this capitalized variables with actual data. glance_swift_store_user: GLANCE_SWIFT_TENANT:GLANCE_SWIFT_USER glance_swift_store_key: SWIFT_PASSWORD_OR_KEYChange the
glance_swift_store_endpoint_typefrom the defaultinternalURLsettings topublicURLif needed.glance_swift_store_endpoint_type: publicURLDefine the store name:
glance_swift_store_container: STORE_NAMEReplace
STORE_NAMEwith the container name in swift to be used for storing images. If the container doesn't exist, it will be automatically created.Define the store region:
glance_swift_store_region: STORE_REGIONReplace
STORE_REGIONif needed.(Optional) Set the paste deploy flavor:
glance_flavor: GLANCE_FLAVORBy default, the Image service uses caching and authenticates with the Identity service. The default maximum size of the image cache is 10 GB. The default Image service container size is 12 GB. In some configurations, the Image service might attempt to cache an image which exceeds the available disk space. If necessary, you can disable caching. For example, to use Identity without caching, replace
GLANCE_FLAVORwithkeystone:glance_flavor: keystoneOr, to disable both authentication and caching, set
GLANCE_FLAVORto no value:glance_flavor:This option is set by default to use authentication and cache management in the
playbooks/roles/os_glance/defaults/main.ymlfile. To override the default behavior, setglance_flavorto a different value in/etc/openstack_deploy/user_variables.yml.The possible values for
GLANCE_FLAVORare:- (Nothing)
cachingcachemanagementkeystonekeystone+cachingkeystone+cachemanagement(default)trusted-authtrusted-auth+cachemanagement