* Db list operation added for postgresql
* User list operation added for postgresql
* User create operation added for postgresql
* User delete operation added for postgresql
* Db create operation added for postgresql
* Db delete operation added for postgresql
* User grant access operation added for postgresql
* User revoke access and update attributes operations added for postgresql
* Common/db/models collate and character_set setter functions are updated.
Depends-On: https://review.opendev.org/c/openstack/trove-tempest-plugin/+/930276
Change-Id: I4c000363dd046fc82f099de0a30c16b1f01d6d2c
In order to avoid docker pull rate limit, this commit
replaces images in the dockerhub to quay.io/openstack.trove
Change-Id: I4fb7afd9f6a5d84578bb6226f8b2ff4b9908a526
As per 2025.1 testing runtime[1], we need to test on Ubuntu
Noble (which will be taken care by tempest and devstack [2]
patches to move base jobs to Noble) and at least single job to run on
Ubuntu Jammy (for smooth upgrade from previous releases).
This commit adds a new job to run on Jammy which can be removed
in future cycle when testing runtime test next version of Ubuntu
as default.
Also bump the hacking version to fix the pepe8 erorr:
-AttributeError: 'EntryPoints' object has no attribute 'get'
[1] https://governance.openstack.org/tc/reference/runtimes/2025.1.html
[2] https://review.opendev.org/c/openstack/tempest/+/932156
Change-Id: Ia29391d5535b16589d7cf259f958b3b6aac5776c
TypeError: tuple indices must be integers or slices, not str
this is caused by the new version of the sqlachemy library.
Change-Id: I76166f901f961a18ad4297d04e1a75a59b059e23
using apt to install diskimage-builder to avoid
'externally-managed-environment' error on ubuntu Noble
Change-Id: Ia461bb28c41e4fe64bee90e170c095137a2f110f
This target hasn't been validated in CI. Currently running the target
consistently fails likely because of the quite old version pinned to.
Because hacking/flake8/pep8 is already used, drop the unmaintained
target.
Change-Id: I414b24355a2b750f5ae0ff92613cfbfc1f39f3ff
Since lower constraints job was removed the bounds are not actually
tested. Add a note to explain the bounds are maintained on best effort
basis.
Change-Id: I8c9d2b029e08789bd11bb77ea2b0d577fc5f5257
olso.policy 4.5.0[1] changed the config options policy_file
default value to 'policy.yaml', which means it is changed
for all the OpenStack services and they do not need to
override the default anymore.
NOTE: There is no change in behaviour here, oslo.policy provides
the same configuration that services have overridden till now.
[1] https://review.opendev.org/c/openstack/releases/+/934012
[2] https://review.opendev.org/c/openstack/requirements/+/934295
Change-Id: Id8b6efa93a059adfaaa9bd4827eca957593bf171
When upgrading Trove, the trove-manage script fails
to upgrade the database when the DBDatastoreVersion
table is not empty.
This patch will help us fix above error
Change-Id: Ib615032747f89daf7f8500c7e2df4064fab05314
Python 3.8 was removed from the tested runtimes for 2024.2[1] and has
not been tested since then.
Also add Python 3.12 which is part of the tested runtimes for 2025.1.
Now unit tests job with Python 3.12 is voting.
[1] https://governance.openstack.org/tc/reference/runtimes/2024.2.html
Change-Id: I76df03331cc565ffd8638ad30660f52e22fc99ab
This code worked around a bug in eventlet[1] that has been fixed in
115103d5608cbe8f15df10e27eba1644f5364e95. The fix has been available in
every eventlet release since v0.27.0.
[1] https://github.com/eventlet/eventlet/issues/592
Co-Authored-By: Cyril Roelandt <cyril@redhat.com>
Change-Id: Idb0d7d46b149d600ac34442ad53e4d78713f7f2f
Add file to the reno documentation build to show release notes for
stable/2024.2.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/2024.2.
Sem-Ver: feature
Change-Id: I84d4fe645bf2f18fdbbcfbd0c9cd81b44f738152
When trove prepares a container, it grants permissions for folders with
the default user/group "database" (ID 1001). However, some Docker images
require a different user for provisioning the database. Therefore, we
need to make it flexible so that the database container can run with
the required user and group, regardless of the default settings.
Story: #2010827
Task: #48386
Change-Id: Ie0268951db7a9e711089714cecf7fbf311eecec8
Currently the logic to determine the admin context is controlled by
the [DEFAULT] admin_roles option but this requires that users set both
policy and the option properly.
This replaces the option by a new policy rule so that users can define
all policy related settings in the policy.yaml file. This also allows
users to create their is_admin rule with not only roles but also with
other elements.
Change-Id: Ib9d003065f943a5382e1079397bfde4292f5dabb
This PR introduces Alembic database migration tool. Trove currently
uses sqlalchemy-migrate with which SQLAlchemy-2.0 does not work. By
introducing the new migration tool, we can prepare for migrating
to SQLAlchemy-2.0.
This change will not affect the default trove-manage's usage while
the database schema versioning will be changed because alembic uses
non-linear, dependency-graph versioning while sqlalchemy-migrate
uses integer based versioning.
Depends-On: https://review.opendev.org/c/openstack/trove-tempest-plugin/+/921589
Co-Authored-By: wu.chunyang <wchy1001@gmail.com>
Story: 2010922
Task: 48782
Change-Id: Idd63f470a2b941720314b6356fe28cd8e394427e
Trove does not use extras and it was removed from the top-level
requirements by 2cc36175c8dec51824c716304a7dd16c3d1038ef .
Also enum34 is no longer required because now the minimum supported
python version is 3.8 .
Change-Id: I62c04ccc3c8157a86fa8b5a307983ba0796111b0