openstack/glance
Code Issues Proposed changes

Imported Translations from Zanata

Browse Source 
For more information about this automatic import see:
https://docs.openstack.org/i18n/latest/reviewing-translation-import.html

Change-Id: I7bed209616a02f51d0a43d59d8b448b8bccdb168
This commit is contained in:
OpenStack Proposal Bot 2020-05-05 06:41:22 +00:00
parent 7a89d4c353
commit 3e2e51a5d0
1 changed files with 723 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

727
releasenotes/source/locale/en_GB/LC_MESSAGES/releasenotes.po
View File

@ -6,11 +6,11 @@ msgid ""
msgstr ""
"Project-Id-Version: Glance Release Notes\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-04-27 18:30+0000\n"
"POT-Creation-Date: 2020-05-04 21:58+0000\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"PO-Revision-Date: 2020-04-27 07:47+0000\n"
"PO-Revision-Date: 2020-05-04 09:10+0000\n"
"Last-Translator: Andi Chandler <andi@gowling.com>\n"
"Language-Team: English (United Kingdom)\n"
"Language: en_GB\n"
@ -140,8 +140,8 @@ msgstr "20.0.0.0b2"
msgid "20.0.0.0b3"
msgstr "20.0.0.0b3"
msgid "20.0.0.0rc1-6"
msgstr "20.0.0.0rc1-6"
msgid "20.0.0.0rc2"
msgstr "20.0.0.0rc2"
msgid ""
"A new common image property, 'description', has been added. This allows you "
@ -684,6 +684,17 @@ msgstr ""
"source image formats that users can upload. Any image that fails the "
"conversion when this plugin is enabled will fail the image creation."
msgid ""
"Be aware that if you define a policy rule for ``default`` or "
"``context_is_admin``, that policy rule will also be used by the policies "
"that govern permissions to perform actions using the Images API, even if "
"these actions are not specified in the policy file."
msgstr ""
"Be aware that if you define a policy rule for ``default`` or "
"``context_is_admin``, that policy rule will also be used by the policies "
"that govern permissions to perform actions using the Images API, even if "
"these actions are not specified in the policy file."
msgid "Bug 1229823_: Handle file delete races in image cache"
msgstr "Bug 1229823_: Handle file delete races in image cache"
@ -864,6 +875,41 @@ msgid "Bug 1836140_: Image deletion returns 500 if 'file' store is not enabled"
msgstr ""
"Bug 1836140_: Image deletion returns 500 if 'file' store is not enabled"
msgid ""
"Bug 1850412_: Useful image properties in glance - os_admin_user not "
"documented"
msgstr ""
"Bug 1850412_: Useful image properties in glance - os_admin_user not "
"documented"
msgid "Bug 1855708_: Reload tests broken in Py3"
msgstr "Bug 1855708_: Reload tests broken in Py3"
msgid ""
"Bug 1861334_: cors config defaults not used when Glance is run as WSGI app"
msgstr ""
"Bug 1861334_: cors config defaults not used when Glance is run as WSGI app"
msgid ""
"Bug 1861501_: Store ID fetched from URI is incorrectly encoded under py27"
msgstr ""
"Bug 1861501_: Store ID fetched from URI is incorrectly encoded under py27"
msgid ""
"Bug 1861723_: Glance is listening on TCP socket before store initialization"
msgstr ""
"Bug 1861723_: Glance is listening on TCP socket before store initialisation"
msgid ""
"Bug 1863021_: eventlet monkey patch results in assert len(_active) == 1 "
"AssertionError"
msgstr ""
"Bug 1863021_: eventlet monkey patch results in assert len(_active) == 1 "
"AssertionError"
msgid "Bug 1863879_: Multiple import fails if all-stores 'True' is passed"
msgstr "Bug 1863879_: Multiple import fails if all-stores 'True' is passed"
msgid "Bug Fixes"
msgstr "Bug Fixes"
@ -968,6 +1014,33 @@ msgstr ""
msgid "Deprecation Notes"
msgstr "Deprecation Notes"
msgid ""
"Documentation examples were changed from ``openstack`` commands back to "
"``glance``. This should help avoid the frustration of glance-community "
"maintaining different client than what is referred in examples. 'python-"
"glanceclient' is and will be the reference implementation of Images API and "
"the team will implement all API changes to the relevant client version of "
"the cycle as well."
msgstr ""
"Documentation examples were changed from ``openstack`` commands back to "
"``glance``. This should help avoid the frustration of Glance-community "
"maintaining different client than what is referred in examples. 'python-"
"glanceclient' is and will be the reference implementation of Images API and "
"the team will implement all API changes to the relevant client version of "
"the cycle as well."
msgid "Dropped support for python 2.7"
msgstr "Dropped support for Python 2.7"
msgid ""
"Due to some unresolved issues on consuming multiple backends work the "
"stabilization of the feature has been pushed to Train and will stay "
"EXPERIMENTAL on Stein."
msgstr ""
"Due to some unresolved issues on consuming multiple backends work the "
"stabilisation of the feature has been pushed to Train and will stay "
"EXPERIMENTAL on Stein."
msgid ""
"Due to the bug in the glance_store implementation of multihash feature the "
"first stable Rocky release (0.26.0) of glance_store does not work with "
@ -1177,6 +1250,9 @@ msgstr ""
"Glance now uses the `python 'cryptography' module`_ instead of the "
"'pycrypto' module."
msgid "Glance services can now run on Windows."
msgstr "Glance services can now run on Windows."
msgid ""
"Glance uses the ``cursive`` library's functionality to verify digital "
"signatures. To familiarize yourself with this new dependency and see the "
@ -1259,6 +1335,95 @@ msgstr ""
"the backend even though the image goes to 'killed' state. The data remains "
"even if a user deletes the killed image record."
msgid ""
"If the ``cinder_encryption_key_deletion_policy`` image property is missing "
"or has any value other than ``on_image_deletion``, Glance will **not** "
"attempt to delete the key whose identifier is the value of "
"``cinder_encryption_key_id``."
msgstr ""
"If the ``cinder_encryption_key_deletion_policy`` image property is missing "
"or has any value other than ``on_image_deletion``, Glance will **not** "
"attempt to delete the key whose identifier is the value of "
"``cinder_encryption_key_id``."
msgid ""
"If the existing ``policy.json`` file relies on the ``default`` rule for some "
"policies (i.e. not all policies are explicitly specified in the file) then "
"the ``default`` rule must be explicitly set (e.g. to ``\"role:admin\"``) in "
"the file. The new default value for the ``default`` rule is ``\"\"``, "
"whereas since the Queens release it has been ``\"role:admin\"`` (prior to "
"Queens it was ``\"@\"``, which allows everything). After upgrading to this "
"release, the policy file should be replaced by one that overrides only "
"policies that need to be different from the defaults, without relying on the "
"``default`` rule."
msgstr ""
"If the existing ``policy.json`` file relies on the ``default`` rule for some "
"policies (i.e. not all policies are explicitly specified in the file) then "
"the ``default`` rule must be explicitly set (e.g. to ``\"role:admin\"``) in "
"the file. The new default value for the ``default`` rule is ``\"\"``, "
"whereas since the Queens release it has been ``\"role:admin\"`` (prior to "
"Queens it was ``\"@\"``, which allows everything). After upgrading to this "
"release, the policy file should be replaced by one that overrides only "
"policies that need to be different from the defaults, without relying on the "
"``default`` rule."
msgid ""
"If upgrade is conducted from PY27 where ssl connections has been terminated "
"into glance-api, the termination needs to happen externally from now on."
msgstr ""
"If upgrade is conducted from PY27 where SSL connections has been terminated "
"into glance-api, the termination needs to happen externally from now on."
msgid ""
"If you are using the multistore feature, you must define configuration "
"options for ``os_glance_tasks_store`` and ``os_glance_staging_store`` in the "
"``glance-scrubber.conf`` file. See the \"Reserved Stores\" section of the "
"\"Multi Store Support\" chapter of the Glance Administration Guide for more "
"information."
msgstr ""
"If you are using the multistore feature, you must define configuration "
"options for ``os_glance_tasks_store`` and ``os_glance_staging_store`` in the "
"``glance-scrubber.conf`` file. See the \"Reserved Stores\" section of the "
"\"Multi Store Support\" chapter of the Glance Administration Guide for more "
"information."
msgid ""
"If you choose to use the Barbican secret identified by the value of "
"``cinder_encryption_key_id`` for any other purpose, you risk data loss."
msgstr ""
"If you choose to use the Barbican secret identified by the value of "
"``cinder_encryption_key_id`` for any other purpose, you risk data loss."
msgid ""
"If you use the Glance multiple stores feature, introduced on an experimental "
"basis in Rocky and now fully supported in the Train release, then you *must* "
"use backing stores instead of ``work_dir`` and ``node_staging_uri`` for "
"Glance's temporary storage **beginning right now with the current "
"release**. See the \"Reserved Stores\" section of the \"Multi Store Support"
"\" chapter of the Glance Administration Guide for more information."
msgstr ""
"If you use the Glance multiple stores feature, introduced on an experimental "
"basis in Rocky and now fully supported in the Train release, then you *must* "
"use backing stores instead of ``work_dir`` and ``node_staging_uri`` for "
"Glance's temporary storage **beginning right now with the current "
"release**. See the \"Reserved Stores\" section of the \"Multi Store Support"
"\" chapter of the Glance Administration Guide for more information."
msgid ""
"If you were previously aware of this option and were actually using it, we "
"apologize for the inconvenience its removal will cause, but overall it will "
"be better for everyone if policy configuration is confined to the policy "
"configuration file and this backdoor is eliminated. The migration path is "
"to explictly mention the role you configured for this option in appropriate "
"places in your policy configuration file."
msgstr ""
"If you were previously aware of this option and were actually using it, we "
"apologize for the inconvenience its removal will cause, but overall it will "
"be better for everyone if policy configuration is confined to the policy "
"configuration file and this backdoor is eliminated. The migration path is "
"to explicitly mention the role you configured for this option in appropriate "
"places in your policy configuration file."
msgid ""
"If you wish to enable the EXPERIMENTAL version 2.6 API that contains the new "
"interoperable image import functionality, set the configuration option "
@ -1270,6 +1435,15 @@ msgstr ""
"``enable_image_import`` to True in the glance-api.conf file. The default "
"value for this option is False."
msgid ""
"If you wish to use the backend store feature now, please see the \"Reserved "
"Stores\" section of the \"Multi Store Support\" chapter of the Glance "
"Administration Guide for configuration information."
msgstr ""
"If you wish to use the backend store feature now, please see the \"Reserved "
"Stores\" section of the \"Multi Store Support\" chapter of the Glance "
"Administration Guide for configuration information."
msgid "Image 'visibility' changes."
msgstr "Image 'visibility' changes."
@ -1440,6 +1614,49 @@ msgstr ""
"false are the equivalent of v2 'shared' images if they have members, or the "
"equivalent of v2 'private' images if they have no members."
msgid ""
"In this release, the default value of ``admin_role`` has been defined as "
"``__NOT_A_ROLE_07697c71e6174332989d3d5f2a7d2e7c_NOT_A_ROLE__``. This "
"effectively makes it inoperable (unless your Keystone administrator has "
"actually created such a role and assigned it to someone, which is unlikely "
"but possible, so you should check). If your local policy tests (you have "
"some, right?) indicate that your Glance policies no longer function as "
"expected, then you have been relying on the ``admin_role`` configuration "
"option and need to revise your policy file. (A short term fix would be to "
"set the ``admin_role`` option back to ``admin``, but keep in mind that it "
"*is* a short-term fix, because this configuration option is deprecated and "
"subject to removal.)"
msgstr ""
"In this release, the default value of ``admin_role`` has been defined as "
"``__NOT_A_ROLE_07697c71e6174332989d3d5f2a7d2e7c_NOT_A_ROLE__``. This "
"effectively makes it inoperable (unless your Keystone administrator has "
"actually created such a role and assigned it to someone, which is unlikely "
"but possible, so you should check). If your local policy tests (you have "
"some, right?) indicate that your Glance policies no longer function as "
"expected, then you have been relying on the ``admin_role`` configuration "
"option and need to revise your policy file. (A short term fix would be to "
"set the ``admin_role`` option back to ``admin``, but keep in mind that it "
"*is* a short-term fix, because this configuration option is deprecated and "
"subject to removal.)"
msgid ""
"In this release, the stores used *must* be the filesystem store type. Our "
"goal is that in a future release, operators will be able to configure a "
"store type from other selected drivers as well. In Train, however, each of "
"these *must* be a filesystem store."
msgstr ""
"In this release, the stores used *must* be the filesystem store type. Our "
"goal is that in a future release, operators will be able to configure a "
"store type from other selected drivers as well. In Train, however, each of "
"these *must* be a filesystem store."
msgid ""
"In this release, the use of stores (instead of configuring the path "
"directly) is optional, but it will become mandatory for the 'U' release."
msgstr ""
"In this release, the use of stores (instead of configuring the path "
"directly) is optional, but it will become mandatory for the 'U' release."
msgid ""
"Include a ``Content-Range`` header upon successful delivery of the requested "
"partial content."
@ -1447,6 +1664,15 @@ msgstr ""
"Include a ``Content-Range`` header upon successful delivery of the requested "
"partial content."
msgid ""
"It is now possible for Glance to use backends accessed via the glance_store "
"library for the temporary storage of data that previously required access to "
"the local filesystem. Please note the following:"
msgstr ""
"It is now possible for Glance to use backends accessed via the glance_store "
"library for the temporary storage of data that previously required access to "
"the local filesystem. Please note the following:"
msgid ""
"It must be noted that the configuration options that take integer values now "
"have a strict range defined with ``min`` and/or ``max`` boundaries where "
@ -1469,6 +1695,15 @@ msgstr ""
msgid "Liberty Series Release Notes"
msgstr "Liberty Series Release Notes"
msgid ""
"Location metadata key ``backend`` has been changed to ``store``. Any "
"environment that might be using the old ``backend`` key will have the key "
"name changed through lazy update upon access."
msgstr ""
"Location metadata key ``backend`` has been changed to ``store``. Any "
"environment that might be using the old ``backend`` key will have the key "
"name changed through lazy update upon access."
msgid ""
"Location updates for images are now restricted to images in ``active`` or "
"``queued`` status. Please refer to the \"Bug Fixes\" section for more "
@ -1487,6 +1722,13 @@ msgstr ""
"is painful for developers and operators, so the less granular means of "
"controlling this feature will be eliminated in the **Ocata** release."
msgid ""
"Manual use of the ``cinder_encryption_key_*`` properties is *not* "
"recommended."
msgstr ""
"Manual use of the ``cinder_encryption_key_*`` properties is *not* "
"recommended."
msgid ""
"Metadata definitions previously associated with OS::Nova::Instance have been "
"changed to be associated with OS::Nova::Server in order to align with Heat "
@ -1510,6 +1752,15 @@ msgstr ""
msgid "Mitaka Series Release Notes"
msgstr "Mitaka Series Release Notes"
msgid ""
"Multiple back-ends: No default back-end gets assigned when adding location "
"via the locations api and not defining back-end ID on the call. This might "
"affect specially Nova snapshots utilizing rdb back-end."
msgstr ""
"Multiple back-ends: No default back-end gets assigned when adding location "
"via the locations API and not defining back-end ID on the call. This might "
"affect specially Nova snapshots utilising RDB back-end."
msgid ""
"Negotiation of the 'Accept-Language' header now follows the \"Lookup\" "
"matching scheme described in `RFC 4647, section 3.4 <https://tools.ietf.org/"
@ -1530,6 +1781,15 @@ msgstr ""
msgid "New Features"
msgstr "New Features"
msgid ""
"New Interoperable Image Import plugin has been introduced to address the use "
"case of providing compressed images either through 'web-download' or to "
"optimize the network utilization between the client and Glance."
msgstr ""
"New Interoperable Image Import plugin has been introduced to address the use "
"case of providing compressed images either through 'web-download' or to "
"optimise the network utilisation between the client and Glance."
msgid "Newton Series Release Notes"
msgstr "Newton Series Release Notes"
@ -1636,6 +1896,21 @@ msgstr ""
"during the Newton and Ocata releases. With the Pike release, it is no "
"longer possible to consume Glare code from the Glance repository."
msgid ""
"Operators who use property protections with the "
"``property_protection_rule_format`` set to ``policies`` must still define "
"the policy rules used for property protections in a policy file. The "
"content of the file may be JSON or YAML. Additionally, we suggest that the "
"absolute pathname of this file be set as the value of ``policy_file`` in the "
"``[oslo_policy]`` section of the ``glance-api.conf`` file."
msgstr ""
"Operators who use property protections with the "
"``property_protection_rule_format`` set to ``policies`` must still define "
"the policy rules used for property protections in a policy file. The "
"content of the file may be JSON or YAML. Additionally, we suggest that the "
"absolute pathname of this file be set as the value of ``policy_file`` in the "
"``[oslo_policy]`` section of the ``glance-api.conf`` file."
msgid ""
"Options where a negative value was previously defined (for example, -1 to "
"mean unlimited) will remain unaffected by this change."
@ -1649,6 +1924,13 @@ msgstr "Other Notes"
msgid "Pike Series Release Notes"
msgstr "Pike Series Release Notes"
msgid ""
"Please keep a watch on the Glance release notes and the glance-specs "
"repository to stay informed about developments on this issue."
msgstr ""
"Please keep a watch on the Glance release notes and the glance-specs "
"repository to stay informed about developments on this issue."
msgid ""
"Please keep in mind that as version 2.8 of the Image Service API is "
"EXPERIMENTAL, we reserve the right to make modifications to these aspects of "
@ -1674,6 +1956,41 @@ msgstr ""
"A Range request to a Glance server with such a backend will result in the "
"entire image content being delivered despite the 206 response code."
msgid ""
"Please see the Upgrades section of this document and the \"Multi Store "
"Support\" chapter of the Glance Administration Guide for more information."
msgstr ""
"Please see the Upgrades section of this document and the \"Multi Store "
"Support\" chapter of the Glance Administration Guide for more information."
msgid ""
"Policy defaults are now defined in code, as they already were in other "
"OpenStack services. After upgrading there is no need to provide a ``policy."
"json`` file (and you should not do so) unless you want to override the "
"default policies, and only policies you want to override need be mentioned "
"in the file. You should no longer rely on the ``default`` rule, and "
"especially not the default value of the rule (which has been relaxed), to "
"assign a non-default policy to rules not explicitly specified in the policy "
"file."
msgstr ""
"Policy defaults are now defined in code, as they already were in other "
"OpenStack services. After upgrading there is no need to provide a ``policy."
"json`` file (and you should not do so) unless you want to override the "
"default policies, and only policies you want to override need be mentioned "
"in the file. You should no longer rely on the ``default`` rule, and "
"especially not the default value of the rule (which has been relaxed), to "
"assign a non-default policy to rules not explicitly specified in the policy "
"file."
msgid ""
"Policy enforcement for several Metadata Definition delete APIs are added in "
"this release. The following actions are enforced and added to the policy."
"json:"
msgstr ""
"Policy enforcement for several Metadata Definition delete APIs are added in "
"this release. The following actions are enforced and added to the policy."
"json:"
msgid "Prelude"
msgstr "Prelude"
@ -1701,9 +2018,29 @@ msgstr ""
"part of the upgrade to Ocata, a 'visibility' column is introduced into the "
"images table. It will be populated as follows"
msgid ""
"Python 2.7 support has been dropped. Last release of Glance to support py2.7 "
"is OpenStack Train (Glance 19.x). The minimum version of Python now "
"supported by Glance is Python 3.6."
msgstr ""
"Python 2.7 support has been dropped. Last release of Glance to support py2.7 "
"is OpenStack Train (Glance 19.x). The minimum version of Python now "
"supported by Glance is Python 3.6."
msgid "Queens Series Release Notes"
msgstr "Queens Series Release Notes"
msgid ""
"Re-introducing cache-manage utility. In Rocky the Images API v1 dependent "
"glance-cache-manage utility was removed while removing the v1 endpoints. "
"Stein release introduces the command refactored to utilize the Images API "
"version 2."
msgstr ""
"Re-introducing cache-manage utility. In Rocky the Images API v1 dependent "
"glance-cache-manage utility was removed while removing the v1 endpoints. "
"Stein release introduces the command refactored to utilize the Images API "
"version 2."
msgid ""
"Removed the deprecated 'enable_image_import' config option. Image import "
"will be always enabled from this release onwards as designed."
@ -1733,6 +2070,11 @@ msgstr ""
msgid "Security Issues"
msgstr "Security Issues"
msgid ""
"See the \"Deprecation Notes\" section of this document for more information."
msgstr ""
"See the \"Deprecation Notes\" section of this document for more information."
msgid ""
"See the documentation in the sample glance-api.conf file for more "
"information."
@ -1822,12 +2164,45 @@ msgstr ""
"mitigation lessens the risk of ID re-usability on those very rare cases when "
"a database purge is necessary."
msgid ""
"Some work has been done on Windows compatibility and Glance Stein release is "
"compatible running on Windows platform. Future development will be also "
"gated on Windows based on 3rd party CI model."
msgstr ""
"Some work has been done on Windows compatibility and Glance Stein release is "
"compatible running on Windows platform. Future development will be also "
"gated on Windows based on 3rd party CI model."
msgid ""
"Stabilization of multi-store feature; from Train onwards multi-store is "
"considered stable feature in glance, glance_store and python-glanceclient. "
"The community encourages everyone to adopt this new way of configuring "
"backend stores at earliest convenience as the old configuration options are "
"deprecated for removal to ease the burden of maintaining underlying code. "
"Users are able to select the store they want their images to be stored "
"during import process."
msgstr ""
"Stabilization of multi-store feature; from Train onwards multi-store is "
"considered stable feature in glance, glance_store and python-glanceclient. "
"The community encourages everyone to adopt this new way of configuring "
"backend stores at earliest convenience as the old configuration options are "
"deprecated for removal to ease the burden of maintaining underlying code. "
"Users are able to select the store they want their images to be stored "
"during import process."
msgid "Start using reno to manage release notes."
msgstr "Start using Reno to manage release notes."
msgid "Stein Series Release Notes"
msgstr "Stein Series Release Notes"
msgid ""
"Stein release cycle has been without major changes to the Images API, this "
"release does not introduce new Images API minor version."
msgstr ""
"Stein release cycle has been without major changes to the Images API, this "
"release does not introduce new Images API minor version."
msgid ""
"Such an image will require its visibility to be updated to 'shared' before "
"it will accept members."
@ -1921,6 +2296,28 @@ msgstr ""
"Liberty and Mitaka releases, Glare ran on code stored in the Glance code "
"repository and used its own tables in the Glance database."
msgid ""
"The Block Storage service *always* creates a new secret in Barbican when it "
"uploads a volume as an image, keeping a 1-1 relation between each secret "
"stored in the Key Management Service and each image of an encrypted volume "
"stored in Glance. Thus, deleting the Barbican secret *at the time when the "
"image is deleted* will not cause data loss *as long as the secret is not "
"being used for any other purpose*."
msgstr ""
"The Block Storage service *always* creates a new secret in Barbican when it "
"uploads a volume as an image, keeping a 1-1 relation between each secret "
"stored in the Key Management Service and each image of an encrypted volume "
"stored in Glance. Thus, deleting the Barbican secret *at the time when the "
"image is deleted* will not cause data loss *as long as the secret is not "
"being used for any other purpose*."
msgid ""
"The Block Storage service will not use the secret associated with an image "
"for any other purpose."
msgstr ""
"The Block Storage service will not use the secret associated with an image "
"for any other purpose."
msgid ""
"The CURRENT version of the Images API v2 is bumped to **2.6**. The 2.6 API "
"was available in the previous (Pike) release as an experimental API to "
@ -1954,6 +2351,32 @@ msgstr ""
"been revised and updated. This includes information about the current "
"experimental status of rolling upgrades and zero-downtime database upgrades."
msgid ""
"The Glance API configuration option ``admin_role`` is deprecated in this "
"release and is subject to removal at the beginning of the Victoria "
"development cycle, following the `OpenStack standard deprecation policy "
"<https://governance.openstack.org/reference/tags/assert_follows-standard-"
"deprecation.html>`_."
msgstr ""
"The Glance API configuration option ``admin_role`` is deprecated in this "
"release and is subject to removal at the beginning of the Victoria "
"development cycle, following the `OpenStack standard deprecation policy "
"<https://governance.openstack.org/reference/tags/assert_follows-standard-"
"deprecation.html>`_."
msgid ""
"The Glance API configuration option ``allow_additional_image_properties`` is "
"deprecated in this release and is subject to removal at the beginning of the "
"Victoria development cycle, following the `OpenStack standard deprecation "
"policy <https://governance.openstack.org/reference/tags/assert_follows-"
"standard-deprecation.html>`_."
msgstr ""
"The Glance API configuration option ``allow_additional_image_properties`` is "
"deprecated in this release and is subject to removal at the beginning of the "
"Victoria development cycle, following the `OpenStack standard deprecation "
"policy <https://governance.openstack.org/reference/tags/assert_follows-"
"standard-deprecation.html>`_."
msgid ""
"The Glance API configuration option ``owner_is_tenant`` is deprecated in "
"this release and is subject to removal at the beginning of the 'S' "
@ -2021,6 +2444,17 @@ msgstr ""
"refactored\") and the API calls that are exposed to implement it in the "
"EXPERIMENTAL v2.6 of the API."
msgid ""
"The Image ``checksum`` property contains an MD5 hash of the image data "
"associated with an image. MD5 has not been considered secure for some time, "
"and in order to comply with various security standards (for example, FIPS), "
"an implementation of the MD5 algorithm may not be available on glance nodes."
msgstr ""
"The Image ``checksum`` property contains an MD5 hash of the image data "
"associated with an image. MD5 has not been considered secure for some time, "
"and in order to comply with various security standards (for example, FIPS), "
"an implementation of the MD5 algorithm may not be available on Glance nodes."
msgid ""
"The Images (Glance) version 1 API has been DEPRECATED. Please see "
"deprecations section for more information."
@ -2068,6 +2502,27 @@ msgstr ""
"following policy targets to **role:admin**: **get_task**, **get_tasks**, "
"**add_task**, and **modify_task**."
msgid ""
"The ``compressed`` container format was added in support of the Cinder "
"(Block Storage Service) feature `Leverage compression accelerator <http://"
"specs.openstack.org/openstack/cinder-specs/specs/train/leverage-compression-"
"accelerator.html>`_. You may expect that Cinder will be able to consume any "
"image in ``compressed`` container format *that Cinder has created*. You "
"should not expect, however, for other services to be able to consume such an "
"image at the present time. Further, you should not expect Cinder to be able "
"to successfully use an image in ``compressed`` format that it has not "
"created itself."
msgstr ""
"The ``compressed`` container format was added in support of the Cinder "
"(Block Storage Service) feature `Leverage compression accelerator <http://"
"specs.openstack.org/openstack/cinder-specs/specs/train/leverage-compression-"
"accelerator.html>`_. You may expect that Cinder will be able to consume any "
"image in ``compressed`` container format *that Cinder has created*. You "
"should not expect, however, for other services to be able to consume such an "
"image at the present time. Further, you should not expect Cinder to be able "
"to successfully use an image in ``compressed`` format that it has not "
"created itself."
msgid ""
"The ``cursive`` library is an OpenStack project which implements OpenStack-"
"specific verification of digital signatures."
@ -2139,6 +2594,52 @@ msgstr ""
msgid "The ``s3`` store driver has been removed."
msgstr "The ``s3`` store driver has been removed."
msgid ""
"The ``sheepdog`` storage backend driver was deprecated in the Train release "
"and has now been removed. Any deployments still using Sheepdog storage will "
"need to migrate to a different backend storage prior to upgrading to this "
"release."
msgstr ""
"The ``sheepdog`` storage backend driver was deprecated in the Train release "
"and has now been removed. Any deployments still using Sheepdog storage will "
"need to migrate to a different backend storage prior to upgrading to this "
"release."
msgid ""
"The ``show_multiple_locations`` configuration option remains DEPRECATED but "
"not removed in the Train release. We continue to recommend that image "
"locations not be exposed to end users. See `OSSN-0065 <https://wiki."
"openstack.org/wiki/OSSN/OSSN-0065>`_ for more information."
msgstr ""
"The ``show_multiple_locations`` configuration option remains DEPRECATED but "
"not removed in the Train release. We continue to recommend that image "
"locations not be exposed to end users. See `OSSN-0065 <https://wiki."
"openstack.org/wiki/OSSN/OSSN-0065>`_ for more information."
msgid ""
"The ``show_multiple_locations`` configuration option remains DEPRECATED but "
"not removed in the Ussuri release. We continue to recommend that image "
"locations not be exposed to end users. See `OSSN-0065 <https://wiki."
"openstack.org/wiki/OSSN/OSSN-0065>`_ for more information."
msgstr ""
"The ``show_multiple_locations`` configuration option remains DEPRECATED but "
"not removed in the Ussuri release. We continue to recommend that image "
"locations not be exposed to end users. See `OSSN-0065 <https://wiki."
"openstack.org/wiki/OSSN/OSSN-0065>`_ for more information."
msgid ""
"The ``show_multiple_locations`` configuration option remains deprecated in "
"this release, but it has not been removed. (It had been scheduled for "
"removal in the Pike release.) Please keep a watch on the Glance release "
"notes and the glance-specs repository to stay informed about developments on "
"this issue."
msgstr ""
"The ``show_multiple_locations`` configuration option remains deprecated in "
"this release, but it has not been removed. (It had been scheduled for "
"removal in the Pike release.) Please keep a watch on the Glance release "
"notes and the glance-specs repository to stay informed about developments on "
"this issue."
msgid ""
"The ``web-download`` import-method, intended to be a replacement for the "
"popular Image Service API v1 \"copy-from\" functionality, is configurable so "
@ -2177,6 +2678,13 @@ msgstr ""
"downtime database upgrades, which are part of the effort to implement "
"rolling upgrades for Glance (scheduled for the Pike release)."
msgid ""
"The configuration options ``work_dir`` and ``node_staging_uri`` are "
"deprecated and will be removed early in the 'U' development cycle."
msgstr ""
"The configuration options ``work_dir`` and ``node_staging_uri`` are "
"deprecated and will be removed early in the 'U' development cycle."
msgid ""
"The database migration engine used by Glance for database upgrades has been "
"changed from *SQLAlchemy Migrate* to *Alembic* in this release."
@ -2215,6 +2723,17 @@ msgstr ""
"has no members is not accessible to other users, so it is functionally a "
"private image."
msgid ""
"The default value of the Glance API configuration option ``admin_role`` has "
"been changed in this release. If you were also using the default policy "
"configuration, this change will not affect you. If you were *not* using the "
"default policy configuration, please read on."
msgstr ""
"The default value of the Glance API configuration option ``admin_role`` has "
"been changed in this release. If you were also using the default policy "
"configuration, this change will not affect you. If you were *not* using the "
"default policy configuration, please read on."
msgid ""
"The deprecation path for the configuration option "
"``show_multiple_locations`` has been changed because the mitigation "
@ -2235,6 +2754,23 @@ msgstr ""
"The discovery calls defined in the `refactored image import spec`_ remain in "
"an abbreviated form in this release."
msgid ""
"The exact format of the compressed file is unspecified. It is the "
"responsibility of the consuming service to analyze the data payload and "
"determine the compression format. A particular OpenStack service may only "
"support specific formats. Thus, even if a service does support the "
"``compressed`` container format, this does not imply that the service can "
"handle arbitrary compression formats. Consult the documentation for the "
"service that will consume your image for details."
msgstr ""
"The exact format of the compressed file is unspecified. It is the "
"responsibility of the consuming service to analyse the data payload and "
"determine the compression format. A particular OpenStack service may only "
"support specific formats. Thus, even if a service does support the "
"``compressed`` container format, this does not imply that the service can "
"handle arbitrary compression formats. Consult the documentation for the "
"service that will consume your image for details."
msgid ""
"The following are some highlights of the bug fixes included in this release."
msgstr ""
@ -2255,6 +2791,11 @@ msgid ""
msgstr ""
"The following metadata definitions have been modified in the Rocky release:"
msgid ""
"The following metadata definitions have been modified in the Train release:"
msgstr ""
"The following metadata definitions have been modified in the Train release:"
msgid ""
"The glance configuration options have been improved with detailed help "
"texts, defaults for sample configuration files, explicit choices of values "
@ -2266,6 +2807,32 @@ msgstr ""
"for operators to choose from, and a strict range defined with ``min`` and "
"``max`` boundaries."
msgid ""
"The glance-scrubber utility is now multistore aware. If you are using the "
"multistore feature, you must define configuration options for "
"``os_glance_tasks_store`` and ``os_glance_staging_store`` in the ``glance-"
"scrubber.conf`` file. See the \"Reserved Stores\" section of the \"Multi "
"Store Support\" chapter of the Glance Administration Guide for more "
"information."
msgstr ""
"The glance-scrubber utility is now multistore aware. If you are using the "
"multistore feature, you must define configuration options for "
"``os_glance_tasks_store`` and ``os_glance_staging_store`` in the ``glance-"
"scrubber.conf`` file. See the \"Reserved Stores\" section of the \"Multi "
"Store Support\" chapter of the Glance Administration Guide for more "
"information."
msgid ""
"The identifier ``compressed`` has been added to the list of supported "
"container formats. The intent is that this format identifier will be used "
"for any compressed file archive format (for example, gzip or rar) that is "
"not otherwise covered by the existing container format identifiers."
msgstr ""
"The identifier ``compressed`` has been added to the list of supported "
"container formats. The intent is that this format identifier will be used "
"for any compressed file archive format (for example, gzip or rar) that is "
"not otherwise covered by the existing container format identifiers."
msgid ""
"The identifier ``ploop`` has been added to the list of supported disk "
"formats in Glance. The respective configuration option has been updated and "
@ -2336,6 +2903,17 @@ msgstr ""
"was deprecated in Mitaka, and has been removed in Newton. Related "
"CVE-2015-8234."
msgid ""
"The intent of the ``compressed`` container format identifier introduced in "
"this release is that it will be used for any compressed file archive format "
"(for example, gzip or rar) that is not otherwise covered by the existing "
"container format identifiers."
msgstr ""
"The intent of the ``compressed`` container format identifier introduced in "
"this release is that it will be used for any compressed file archive format "
"(for example, gzip or rar) that is not otherwise covered by the existing "
"container format identifiers."
msgid ""
"The internal store identifiers introduced in this release are "
"``os_glance_tasks_store`` and ``os_glance_staging_store``."
@ -2354,6 +2932,21 @@ msgstr ""
"interoperable image import workflow. The operator, however, must make sure "
"that the following configuration options are set correctly."
msgid ""
"The introduction of the ``compressed`` container format in this release "
"gives us the opportunity to remind you that Glance does not verify that the "
"``container_format`` image property is accurate for *any* container format. "
"It is the responsibility of the image consumer to verify the image data "
"payload format and take appropriate action in the case of a misdescribed "
"image."
msgstr ""
"The introduction of the ``compressed`` container format in this release "
"gives us the opportunity to remind you that Glance does not verify that the "
"``container_format`` image property is accurate for *any* container format. "
"It is the responsibility of the image consumer to verify the image data "
"payload format and take appropriate action in the case of a misdescribed "
"image."
msgid ""
"The latest release of glance_store library does not have the support for the "
"``s3`` driver. All code references of the same have been removed from the "
@ -2422,6 +3015,19 @@ msgstr ""
"directly. After the upgrade, the image will have to have its visibility "
"changed to 'shared' before a member can be assigned."
msgid ""
"The migration path for operators who were using this option in its "
"nondefault ``False`` setting is to set the ``image_property_quota`` option "
"to ``0``. Since many other OpenStack services depend upon the ability to "
"read/write custom image properties, however, we suspect that no one has been "
"using the option with a nondefault value."
msgstr ""
"The migration path for operators who were using this option in its "
"nondefault ``False`` setting is to set the ``image_property_quota`` option "
"to ``0``. Since many other OpenStack services depend upon the ability to "
"read/write custom image properties, however, we suspect that no one has been "
"using the option with a nondefault value."
msgid ""
"The new ``tasks_api_access`` policy target directly controls access to the "
"Tasks API, whereas targets just mentioned indirectly affect what can be "
@ -2439,6 +3045,43 @@ msgstr ""
"Tasks API admin-only, you can accomplish this by using the following "
"settings:"
msgid ""
"The plan continues to be to eliminate the option and use only policies to "
"control image locations access. This, however, requires some major "
"refactoring, as discussed in the `draft Policy Refactor spec <https://review."
"openstack.org/#/c/528021/>`_. Further, there is no projected timeline for "
"this change, as no one has been able to commit time to it. (The Glance team "
"would be happy to discuss this more with anyone interested in working on it.)"
msgstr ""
"The plan continues to be to eliminate the option and use only policies to "
"control image locations access. This, however, requires some major "
"refactoring, as discussed in the `draft Policy Refactor spec <https://review."
"openstack.org/#/c/528021/>`_. Further, there is no projected timeline for "
"this change, as no one has been able to commit time to it. (The Glance team "
"would be happy to discuss this more with anyone interested in working on it.)"
msgid ""
"The plan is to eliminate the option and use only policies to control image "
"locations access. This, however, requires some major refactoring. See the "
"`draft Policy Refactor spec <https://review.openstack.org/#/c/528021/>`_ for "
"more information."
msgstr ""
"The plan is to eliminate the option and use only policies to control image "
"locations access. This, however, requires some major refactoring. See the "
"`draft Policy Refactor spec <https://review.openstack.org/#/c/528021/>`_ for "
"more information."
msgid ""
"The properties ``cinder_encryption_key_id`` and "
"``cinder_encryption_key_deletion_policy`` have been added to the *common "
"image properties* and appear in the image schema. See the \"New Features\" "
"section of these notes for information about these image properties."
msgstr ""
"The properties ``cinder_encryption_key_id`` and "
"``cinder_encryption_key_deletion_policy`` have been added to the *common "
"image properties* and appear in the image schema. See the \"New Features\" "
"section of these notes for information about these image properties."
msgid ""
"The property ``img_hide_hypervisor_id`` has been added to the namespace "
"``OS::Compute::LibvirtImage``."
@ -2471,6 +3114,19 @@ msgstr ""
"information about the configuration required to make the import "
"functionality work correctly."
msgid ""
"The secure \"multihash\" image properties, ``os_hash_algo`` and "
"``os_hash_value`` have been available on images since glance version 17.0.0 "
"(Rocky). Until this point, the MD5 ``checksum`` property has been populated "
"solely for backward compatability. It is not, however, necessary for "
"validating downloaded image data."
msgstr ""
"The secure \"multihash\" image properties, ``os_hash_algo`` and "
"``os_hash_value`` have been available on images since glance version 17.0.0 "
"(Rocky). Until this point, the MD5 ``checksum`` property has been populated "
"solely for backward compatibility. It is not, however, necessary for "
"validating downloaded image data."
msgid ""
"The secure hash algorithm used is an operator-configurable setting. See the "
"help text for 'hashing_algorithm' in the sample Glance configuration file "
@ -2480,6 +3136,25 @@ msgstr ""
"help text for 'hashing_algorithm' in the sample Glance configuration file "
"for more information."
msgid ""
"The ssl support from Glance has been removed as it worked only under PY27 "
"which is not anymore supported environment. Termination of encrypted "
"connections needs to happen externally as soon as move to PY3 happens. Any "
"deployment needing end to end encryption would need to put either reverse "
"proxy (using fully blown http server like Apache or Nginx will cause "
"significant performance hit and we advice using something more simple that "
"does not break the http protocol) in front of the service or utilize ssl "
"tunneling (like stunnel) between loadbalancers and glance-api."
msgstr ""
"The SSL support from Glance has been removed as it worked only under PY27 "
"which is not any more supported environment. Termination of encrypted "
"connections needs to happen externally as soon as move to PY3 happens. Any "
"deployment needing end to end encryption would need to put either reverse "
"proxy (using fully blown http server like Apache or Nginx will cause "
"significant performance hit and we advice using something more simple that "
"does not break the http protocol) in front of the service or utilize SSL "
"tunnelling (like stunnel) between loadbalancers and glance-api."
msgid ""
"The store drivers configuration order in the sample or autogenerated files "
"should be expected to be alphabetical as - ``cinder``, ``filesystem``, "
@ -2489,6 +3164,15 @@ msgstr ""
"should be expected to be alphabetical as - ``cinder``, ``filesystem``, "
"``http``, ``rbd``, ``sheepdog``, ``swift``, ``vmware``."
msgid ""
"The store name prefix ``os_glance_*`` is reserved by Glance for internal "
"stores. Glance will refuse to start if a store with this prefix is included "
"in the ``enabled_backends`` option."
msgstr ""
"The store name prefix ``os_glance_*`` is reserved by Glance for internal "
"stores. Glance will refuse to start if a store with this prefix is included "
"in the ``enabled_backends`` option."
msgid ""
"The task API is being deprecated and it has been made admin only. If "
"deployers of Glance would like to have this API as a public one, it is "
@ -2543,6 +3227,19 @@ msgstr ""
"encourage operators to try out the new functionality, but keep in mind its "
"EXPERIMENTAL nature."
msgid ""
"The workaround is to continue to use the ``show_multiple_locations`` option "
"in a dedicated \"internal\" Glance node that is not accessible to end users. "
"We continue to recommend that image locations not be exposed to end users. "
"See `OSSN-0065 <https://wiki.openstack.org/wiki/OSSN/OSSN-0065>`_ for more "
"information."
msgstr ""
"The workaround is to continue to use the ``show_multiple_locations`` option "
"in a dedicated \"internal\" Glance node that is not accessible to end users. "
"We continue to recommend that image locations not be exposed to end users. "
"See `OSSN-0065 <https://wiki.openstack.org/wiki/OSSN/OSSN-0065>`_ for more "
"information."
msgid ""
"There are some limitations with this method of deploying Glance and we do "
"not recommend its use in production environments at this time. See the "
@ -2552,6 +3249,15 @@ msgstr ""
"not recommend its use in production environments at this time. See the "
"`Known Issues`_ section of this document for more information."
msgid ""
"There is no projected timeline for this change, as no one has been able to "
"commit time to it. The Glance team would be happy to discuss this more with "
"anyone interested in working on it."
msgstr ""
"There is no projected timeline for this change, as no one has been able to "
"commit time to it. The Glance team would be happy to discuss this more with "
"anyone interested in working on it."
msgid ""
"There was a bug in the **experimental** zero-downtime database upgrade path "
"introduced in the Ocata release that prevented the **experimental** upgrade "
@ -2577,6 +3283,19 @@ msgstr ""
msgid "These are read-only image properties and are not user-modifiable."
msgstr "These are read-only image properties and are not user-modifiable."
msgid ""
"These local directories are used by Glance for the temporary storage of data "
"during the interoperable image import process and by the tasks engine. This "
"release introduces the ability to instead use a backend filesystem store "
"accessed via the glance_store library for this temporary storage. Please "
"note the following:"
msgstr ""
"These local directories are used by Glance for the temporary storage of data "
"during the interoperable image import process and by the tasks engine. This "
"release introduces the ability to instead use a backend filesystem store "
"accessed via the glance_store library for this temporary storage. Please "
"note the following:"
msgid ""
"This change applies only to operators using the VMware datastore or "
"filesystem stores"