This is not really actively maintained and is duplicate of the one
available in openstack-manuals.
Change-Id: I6617397585e49501a20e758877c4071a1f3b9d84
The previous attempt[1] was incomplete and these was still one usage
left. The deprecated alias was removed from oslo.db[2] and no longer
works.
[1] b6b9f043ff
[2] bf90aed0f7b19441644de2be807ec680ad86b1b1
Change-Id: Ib3b0271057578a64ae556a11224e3b366ddf89bf
The run_sql_cmd method in functional tests is not used. The method uses
Engine.execute() method which was removed in 2.0.
Change-Id: I6f9ea1dfd852a2d311e17964da0ea56c052b3fda
This is confusing, because after xen you have a dot which can be read
as belonging to the hypervisor type string.
Change-Id: Ibe5da521d80a895b66084c55a993cceebfb68894
In case of Cinder store, when updating location of a legacy image,
we call cinder store to perform the update.
If the operation fails, we log a warning in glance which states:
"Not able to update location url <url> of legacy image due to unknown issues."
Since glance doesn't have knowledge about the actual issue occurred
during the location update, we log this ambiguous warning which is not
useful for operators to debug the actual issue.
The responsibility of logging the warning should be delegated to
glance store (like done here[1]) since it can point to the right
issue as it knows which operation failed exactly.
This patch removes the warning and further warnings should be added
to glance store only.
[1] https://review.opendev.org/c/openstack/glance_store/+/911005
Change-Id: I24b14812a2a15675beacee720d722c2f3a2b252b
These options were deprecated and then removed when the glance-registry
service was removed[2].
[1] 80fef06497
[2] 3068096199
Change-Id: I519c99afe8bcdfa953c14470670dee690e593ce4
Add file to the reno documentation build to show release notes for
stable/2024.1.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/2024.1.
Sem-Ver: feature
Change-Id: I4b22aeaae7c01c92d3d463bda4c157c6a415ea8b
- comments that did not match the parameter names have been corrected.
- parameter information included in parameters but remaining in comments has been deleted.
Change-Id: I6bbaaae697f1be560897c7d99234f1e23e710143
Signed-off-by: Youngjun <yj.yoo@okestro.com>
The stable/xena branch has been deleted, so reno can't find its
release notes. Use the xena-eom tag to indicate the end of the
Glance project's maintenance of the Xena series.
This strategy is consistent with the way we handled stable/yoga and
was agreed upon at the 8 Feb Glance meeting:
https://meetings.opendev.org/meetings/glance/2024/glance.2024-02-08-14.00.log.html#l-58
Change-Id: I57f167ee0d5a56a0ef2bbd12e4ea683b3b1d7079
The stable/wallaby branch has been deleted, so reno can't find its
release notes. Use the wallaby-eom tag to indicate the end of the
Glance project's maintenance of the Wallaby series.
This strategy is consistent with the way we handled stable/yoga and
was agreed upon at the 8 Feb Glance meeting:
https://meetings.opendev.org/meetings/glance/2024/glance.2024-02-08-14.00.log.html#l-58
Change-Id: Ib6ede82ce42168191eaa6a49c09178bf4ae8ec70
The stable/victoria branch has been deleted, so reno can't find its
release notes. Use the victoria-eom tag to indicate the end of the
Glance project's maintenance of the Victoria series.
This strategy is consistent with the way we handled stable/yoga and
was agreed upon at the 8 Feb Glance meeting:
https://meetings.opendev.org/meetings/glance/2024/glance.2024-02-08-14.00.log.html#l-58
Change-Id: I9d5d597e6debb1c71d72f0720c34714c516ad91b
This patch mentions the following details about the glance cinder
store:
Single store:
Importance of setting the service credentials with the cinder store
configuration options.
Multi store:
1. Mention warning that during store initialization, we require the
credentials in configuration file to validate volume types.
2. Upgrade scenario where the values of configuration parameters
should remain same in single and multi store before and after the
upgrade.
3. Upgrade scenario when single store doesn't contain credentials
in glance config file and we need to transfer Image-Volumes to
service project.
Change-Id: Iff1320f8a4cf0c614f1a71556957a11ccd010147
This job will verify that upgrading cache driver from sqlite to
centralized database will not have any impact.
Related blueprint centralized-cache-db
Change-Id: Iafed7342753da73efee2c50079505d88fe8ac4d5
This is follow-up of 1e683483e7 and
replaces the generic Exception asserted in a unit tests by the specific
castellan exception, according to the 4.4.0 release.
This change does not bump minimum required version of castellan because
the version requirement only affects unit tests.
Depends-on: https://review.opendev.org/c/openstack/requirements/+/911059
Change-Id: Id1ed909f179038713d9da2fd72cf39e7fb7c8dfe
Made `centralized_db` cache driver as default driver so that we
can test it using tempest jobs in gate.
Implements blueprint centralized-cache-db
Depends-On: https://review.opendev.org/c/openstack/devstack/+/907110
Change-Id: Id94e93e3ba3fc207b39c7dbff92495805aa0f6f9
oslo.concurrency 6.0.0 has relocated the lock_path that is required
for external locks from [DEFAULT] to the [oslo_concurrency] config
section. Instead of messing with configuration, we can use the
lockutils.set_defaults() method to set this for tests. So add this
to the BaseTestCase so that it's available for all tests.
Change-Id: I2878b4162dddaf935002c168bc544eb1eff71efd
In cache migration unit tests, I was using same cache.db file name
in the setup method which was used by all the tests, which was
causing a issue of deleting a file by other test and resulted
in random failure.
Using random filename to fix this issue permenantly.
Related blueprint centralized-cache-db
Change-Id: I321982013bdf571741a8ef2d0575f65288fff53f