summaryrefslogtreecommitdiff
path: root/releasenotes
Commit message (Collapse)AuthorAgeFilesLines
* Add release note for base test class removalStephen Finucane2023-04-171-0/+24
| | | | | | | | | In change I1e71150ba6daeba464b6ed8d46163f1f34959db3 we removed the legacy base test classes, first deprecated in 2015. We forgot to include a release note, however. Address this now. Change-Id: I4d66f0308b89a187143ef6c8495383fe60043c14 Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
* Get test suite to full pass with SQLAlchemy 2.0Stephen Finucane2023-04-061-0/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | Remaining issues encountered when running with SQLAlchemy 2.0 for real: * Never call str() on a URL and expect it to be meaningful anymore. The password is aggressively obfuscated now (users absolultely wouldn't let us leave it as is) * More utilities and fixtures that were calling begin() within a block that would have already begun * isnot is now called is_not; mocking "isnot" leads into too many weird compat layers * ORM InstrumentedAttribute and internals use __slots__ now, mock seems to not be able to patch methods. Ideally these tests would use a comparator subclass or something * Connection.connection.connection is now called driver_connection, SQLAlchemy keeps the old name available however oslo.db test suite does not appear to tolerate the deprecation warning emitted, so add a compat layer * mapper() is fully removed from 2.0, not sure if there is another not-yet-committed gerrit that removes mapper() [1] https://docs.sqlalchemy.org/en/20/core/engines.html#sqlalchemy.create_engine.params.pool_pre_ping [2] https://docs.sqlalchemy.org/en/20/changelog/changelog_20.html#change-2fe37eaf2295cebd3bb4ee8e5b8c575c [3] https://github.com/sqlalchemy/sqlalchemy/issues/5648 Change-Id: Ifaca67c07f008d8bc0febeecd3e200cc7ee7a4b0
* Remove sqlalchemy-migrateMike Bayer2023-03-211-0/+8
| | | | | | | | | | | | | | | sqlalchemy-migrate does not support SQLAlchemy 2.x and we're not going to invest the time in changing this. Remove integration of sqlalchemy-migrate in oslo.db, allowing us to support SQLAlchemy 2.x fully. Note that we do not remove the 'migration_cli' module entirely yet. While this is deprecated, it is possible to use this with alembic. New users shouldn't be switching to it, but any existing users can continue to use this module for some time yet. Change-Id: Ic3d6bd318038d723b0d50d39e45f8e26289e9a57 Sem-Ver: api-break
* Update master for stable/2023.1OpenStack Release Bot2023-02-242-0/+7
| | | | | | | | | | | | Add file to the reno documentation build to show release notes for stable/2023.1. Use pbr instruction to increment the minor version number automatically so that master versions are higher than the versions on stable/2023.1. Sem-Ver: feature Change-Id: I564d0adb2b6bd7df059ebe40d34715ecd0e2197e
* Imported Translations from ZanataOpenStack Proposal Bot2023-01-271-4/+39
| | | | | | | For more information about this automatic import see: https://docs.openstack.org/i18n/latest/reviewing-translation-import.html Change-Id: Ib2362e15f0b610412ed992d63da63ad2d2b39883
* Fix default value for wsrep_sync_wait option12.3.1Ayumu Ueha2023-01-181-0/+9
| | | | | | | | | | The default value for wsrep_sync_wait option should be `None`. However, since 0 is set incorrectly, an unintended process is executed. This patch fixes default value for wsrep_sync_wait option to `None` instead of `0`. Change-Id: Ifb1dc7ddcb127a69ea01234922caa7ca5ab111ce
* Add option for wsrep_sync_waitMike Bayer2022-12-051-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When using Galera, the wsrep_sync_wait option [1] can change the behavior of a variety of Galera DQL/DML statements such that a particular operation will pause until outstanding write-sets are fully persisted to the local node. The setting supersedes the previous boolean parameter wsrep_causal_reads which only affected SELECT, with an updated approach that allows for fine-grained control of so-called "causality checks" on individual statement types. The legacy-compatible setting of '1' indicates that READ/SELECT/BEGIN operations should proceed only after any pending writesets are fully available. The use case for this setting is for an application that is running operations on multiple Galera nodes simultaenously. An application that commits data on one node, and then immediately uses a different connection (on a potentially different node) to SELECT that data, may fail to see those changes if "causality checks" for SELECT are not enabled. While a COMMIT operation in Galera will block locally until all other nodes approve of the writeset, the operation does not block for the subsequent period of time when other nodes are actually persisting that writeset. Setting up "causal reads" in this case indicates that a SELECT operation will wait until any writesets in progress are available, thus maintaining serialization between the COMMIT and subsequent SELECT. As the name implies, wsrep_sync_wait adds...waiting! to the operation, and thus directly impacts performance by adding latency to SELECT operations or to the operations that have been selected for causality checks, to the degree that concurrent writesets are expected to be present. Since it's not expected that most if any Openstack applications actually need this setting in order to be effective with Galera multi-master operation, and as the setting is available within client session scope and also impacts performance, making it available on a per-application basis means that specific applications which may see issues under load can choose to enable this setting, much in the way any other "transaction isolation" settings might be made, without having to add a cluster-wide performance penalty by setting it at the Galera server level. [1] https://mariadb.com/docs/ent/ref/mdb/system-variables/wsrep_sync_wait/ Change-Id: Iee7afcac8ba952a2d67a9ad9dd0e4eae3f42518e
* Imported Translations from ZanataOpenStack Proposal Bot2022-09-241-2/+15
| | | | | | | For more information about this automatic import see: https://docs.openstack.org/i18n/latest/reviewing-translation-import.html Change-Id: Iae58f095c34f7118a4a2683b6d283e8cf81836b8
* Merge "Deprecate MySQL NDB Cluster Support"Zuul2022-09-091-0/+5
|\
| * Deprecate MySQL NDB Cluster SupportStephen Finucane2022-07-271-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Traditionally, the MySQL support in oslo.db has assumed use of the InnoDB storage engine. However, this isn't the only storage engine available and a few years ago an effort was made to add support for another storage engine, MySQL Cluster (NDB). The oslo.db aspects of this effort were tracked via bug 1564110 [1] and from reading this bug and looking at other patches related to this effort [2], it becomes obvious that this was never seen through to the completion and the OpenStack-wide effort never took off [3]. As a result, much of what is here is in-effect dead code now. Given no one is using this engine, there's no reason to keep it around. Deprecate it with an eye on removing it sooner rather than later. [1] https://bugs.launchpad.net/oslo.db/+bug/1564110 [2] https://review.opendev.org/q/owner:octave.orgeron%2540oracle.com [3] https://review.opendev.org/c/openstack/openstack-specs/+/429940 Change-Id: Id5ddf1d6f47b8a572001f58ad8b9b8a7dbe4e8ac Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
* | Update master for stable/zedOpenStack Release Bot2022-09-092-0/+7
|/ | | | | | | | | | | | Add file to the reno documentation build to show release notes for stable/zed. Use pbr instruction to increment the minor version number automatically so that master versions are higher than the versions on stable/zed. Sem-Ver: feature Change-Id: Ic0f1c5a9e902f13b66bab62d32e452211fb277ef
* Imported Translations from Zanata12.0.0OpenStack Proposal Bot2022-06-211-2/+164
| | | | | | | For more information about this automatic import see: https://docs.openstack.org/i18n/latest/reviewing-translation-import.html Change-Id: I1e47d7a37c1d27b511b45c36a3d56597f2548076
* Update master for stable/yogaOpenStack Release Bot2022-03-042-0/+7
| | | | | | | | | | | | Add file to the reno documentation build to show release notes for stable/yoga. Use pbr instruction to increment the minor version number automatically so that master versions are higher than the versions on stable/yoga. Sem-Ver: feature Change-Id: I450ea045a8cb88f4c59ea84f1340e989126d6b4c
* utils: Remove troublesome utility methods11.2.0Stephen Finucane2022-02-081-0/+15
| | | | | | | | | | These are not compatible with SQLAlchemy 2.0 due to their reliance on nested transactions. We should deprecate them first but doing so would push the boat out further wrt how long we have to wait before achieving compatibility with this new version. Change-Id: If3db4e8c1b681c0c62d3f04a57f92802639b3b9b Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
* Update master for stable/xenaOpenStack Release Bot2021-09-102-0/+7
| | | | | | | | | | | | Add file to the reno documentation build to show release notes for stable/xena. Use pbr instruction to increment the minor version number automatically so that master versions are higher than the versions on stable/xena. Sem-Ver: feature Change-Id: I21f4a1416a8dc316817ebc081b73b76992fca867
* Merge "Drop checks for IBM DB2"Zuul2021-07-291-0/+5
|\
| * Drop checks for IBM DB2Stephen Finucane2021-07-281-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This hasn't been supported by any project for many years. Quoting from the nova patch that removed DB2 support [1] This removes db2 support from tree completely. This is an oddball non open database that made doing live data migrations difficult. It is used by 0% of users in the OpenStack User Survey. Supporting commercial software that doesn't have users at the cost of delivering features and fixes to our community is the wrong tradeoff. This corrects that. There's no need to keep this around. [1] Ifeb9929e4515e3483eb65d371126afd7672b92a4 Change-Id: I8c3f23083e09e5ac924e35d1b7b3248a0d074e1b Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
* | tests: Remove 'ModelsMigrationsSync.check_foreign_keys'Stephen Finucane2021-06-251-0/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The 'check_foreign_key' method was removed in oslo.db 1.4.0 [1] and re-added but marked as deprecated in 1.4.1 [2] to allow for a deprecation period. That was over 6 years ago so we can now remove it. Meanwhile, the private '_walk_versions', '_migrate_down' and '_migrate_up' methods have been marked as deprecated since oslo.db 0.5.0 (!!!) [3]. We can definitely remove these now. codesearch.o.o reveals no users of any of these methods. [1] I77a2bba2de08125b5a601de03c1d2d5c73fa33ee [2] Id892567bd60d6b4b88765bbfe3cd5c5e75910b25 [3] Ic9358445e60a0dd43a5900e8bda7b12f2bebf679 Change-Id: Idb9596284df3e5d038c939d27fe14fe2cc2f4318 Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
* | concurrency: Deprecate 'TpoolDbapiWrapper'Stephen Finucane2021-06-251-0/+9
|/ | | | | | | | | This has been marked as experimented since before oslo.db was split out of nova. We've no test coverage and no idea of whether it even works nowadays. It's time to plan for its eventual removal. Change-Id: Ib7a5a6e1124c44a742b003442f815022a866bcbb Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
* Merge "Remove the idle_timeout option."Zuul2021-06-231-0/+7
|\
| * Remove the idle_timeout option.Daniel Bengtsson2021-06-231-0/+7
| | | | | | | | | | | | | | | | | | | | The option was replaced 4 years ago[1] by connection_recycle_time. The option is not anymore present in sqlalchemy. It's the good time to remove it. [1] https://opendev.org/openstack/oslo.db/commit/6634218415906192fca891362b8fa0ac50b66284 Change-Id: I0c26c3e14ad9ad9a4f30af80757e369d6042441a
* | Followup of "Added handler for mysql 8.0.19 duplicate key error update"9.1.0Kamlesh Chauvhan2021-06-101-0/+8
|/ | | | | | Followup of change: Ic78059b625e73cece355541cb4d89e641abc1103 Change-Id: Idb0410a1946acbd7caf6a0bb1dad229bd5c2c346
* Merge "Remove the sql_max_pool_size option."9.0.0Zuul2021-05-031-0/+4
|\
| * Remove the sql_max_pool_size option.Daniel Bengtsson2021-04-261-0/+4
| | | | | | | | | | | | | | | | The option was replaced 6 years ago[1] by max_pool_size. [1] https://opendev.org/openstack/oslo.db/commit/1b7c295d522e26aa8bf09242dcc1355c3fb1ab3e Change-Id: Ice1a90edc32603c85449b80fe78fd437aa7e8081
* | Fix formatting of release listPierre Riteau2021-04-161-15/+15
| | | | | | | | Change-Id: I129194d096656b06fb0a94a29b4b3cf4e0f00f2f
* | Merge "remove unicode from code"Zuul2021-04-161-7/+7
|\ \
| * | remove unicode from codexuanyandong2021-01-031-7/+7
| |/ | | | | | | Change-Id: Ia782bc7127a1cb967e2f475065b1fb963b9c184f
* | Update master for stable/wallabyOpenStack Release Bot2021-03-182-0/+7
|/ | | | | | | | | | | | Add file to the reno documentation build to show release notes for stable/wallaby. Use pbr instruction to increment the minor version number automatically so that master versions are higher than the versions on stable/wallaby. Sem-Ver: feature Change-Id: I347faed9c8c0e721ab81706c5cd6bb105897df06
* Merge "Deprecate the 'oslo_db.sqlalchemy.migration_cli' module"8.5.0Zuul2020-10-301-0/+6
|\
| * Deprecate the 'oslo_db.sqlalchemy.migration_cli' moduleStephen Finucane2020-10-301-0/+6
| | | | | | | | | | | | | | | | | | | | | | This API allowed users to abstract the differences between sqlalchemy-migrate and alembic. However, no one is using it for that and its continued existence necessitates continued support for sqlalchemy-migrate. Deprecate it now and encourage the odd user to switch to alembic directly. Change-Id: Ia5979369f23b38a2c7307f4112651a8bedb45c01 Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
* | Merge "Deprecate 'oslo_db.sqlalchemy.migration' module"Zuul2020-10-301-0/+8
|\ \ | |/
| * Deprecate 'oslo_db.sqlalchemy.migration' moduleStephen Finucane2020-10-301-0/+8
| | | | | | | | | | | | | | | | | | This module hasn't been touched with years and 'sqlalchemy-migrate' is effectively abandoned. It's time to drop support for this an encourage the laggards to switch to alembic and use it directly. Change-Id: I59335b4f318bae2e29ab139cdea089a4d6e14305 Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
* | Imported Translations from ZanataOpenStack Proposal Bot2020-10-111-2/+5
| | | | | | | | | | | | | | For more information about this automatic import see: https://docs.openstack.org/i18n/latest/reviewing-translation-import.html Change-Id: If6de09e513ec778f9b5f8c34d985aeea640d6002
* | Update master for stable/victoriaOpenStack Release Bot2020-09-112-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | Add file to the reno documentation build to show release notes for stable/victoria. Use pbr instruction to increment the minor version number automatically so that master versions are higher than the versions on stable/victoria. Change-Id: Iefed09b57fffca3a62ec4467e1d18a5f4724c474 Sem-Ver: feature
* | Fix pygments stylemelissaml2020-06-041-1/+1
| | | | | | | | | | | | | | | | New theme of docs respects pygments_style. more info: http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014971.html Change-Id: I572495d50e0edc8bdfe22594dcde30a61b0750b8
* | Switch to newer openstackdocstheme and reno versionsAndreas Jaeger2020-05-181-3/+3
|/ | | | | | | | | | | | | | | | Switch to openstackdocstheme 2.2.0 and reno 3.1.0 versions. Using these versions will allow especially: * Linking from HTML to PDF document * Allow parallel building of documents * Fix some rendering problems Update Sphinx version as well. openstackdocstheme renames some variables, so follow the renames. A couple of variables are also not needed anymore, remove them. Depends-On: https://review.opendev.org/728938 Change-Id: I072cf215486d672eacd3a57483cb2b311483c844
* Imported Translations from ZanataOpenStack Proposal Bot2020-04-191-2/+16
| | | | | | | For more information about this automatic import see: https://docs.openstack.org/i18n/latest/reviewing-translation-import.html Change-Id: I92a2105bb57e96c32f203cf53534eacea524b597
* Update master for stable/ussuriOpenStack Release Bot2020-04-142-0/+7
| | | | | | | | | | | | Add file to the reno documentation build to show release notes for stable/ussuri. Use pbr instruction to increment the minor version number automatically so that master versions are higher than the versions on stable/ussuri. Change-Id: I66ca1c9807ffb434bbc9bb35d3904e61b8ec3750 Sem-Ver: feature
* reword releasenote for py27 support droppingHervé Beraud2020-02-071-1/+1
| | | | Change-Id: I7bbab4f96391828d0b0e095a152bdacca6585e3c
* [ussuri][goal] Drop python 2.7 support and testing7.0.0Hervé Beraud2020-02-031-0/+5
| | | | | | | | | | | | | | OpenStack is dropping the py2.7 support in Ussuri cycle. Complete discussion & schedule can be found in - http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010142.html - https://etherpad.openstack.org/p/drop-python2-support Ussuri Communtiy-wide goal: https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html Change-Id: I02e2d11d38d2aa4182e8d466519b99f05943701f
* Imported Translations from Zanata6.0.0OpenStack Proposal Bot2019-12-221-2/+44
| | | | | | | For more information about this automatic import see: https://docs.openstack.org/i18n/latest/reviewing-translation-import.html Change-Id: I68d368e2e1d3eb5f0fc608b79f242a6b680570e1
* Bump the openstackdocstheme extension to 1.20melissaml2019-11-131-22/+0
| | | | | | | | | | | | Some options are now automatically configured by the version 1.20: - project - html_last_updated_fmt - latex_engine - latex_elements - version - release. Change-Id: I2c3a36fbc020d41c5eaa09008a0586142a63d6ba
* Update master for stable/train5.1.0OpenStack Release Bot2019-09-202-0/+7
| | | | | | | | | | | | Add file to the reno documentation build to show release notes for stable/train. Use pbr instruction to increment the minor version number automatically so that master versions are higher than the versions on stable/train. Change-Id: I377ad03a73b88407d0e70315cbd0162bb9dc356b Sem-Ver: feature
* Removing deprecated min_pool_sizeErik Olof Gunnar Andersson2019-04-061-0/+7
| | | | | | | | | | The database option min_pool_size is not actually used in oslo.db. This is a folllow up to Ib07b7b4200b5cf3a34b8eed441e6754da7d446cf Change-Id: I89754e9e4b42c45259729b0b0bb0a4bf464a981c
* Update master for stable/steinOpenStack Release Bot2019-03-182-0/+7
| | | | | | | | | | | | Add file to the reno documentation build to show release notes for stable/stein. Use pbr instruction to increment the minor version number automatically so that master versions are higher than the versions on stable/stein. Change-Id: Idedd684db42cbda300e69e628e96e4f9475f7df4 Sem-Ver: feature
* Add "is_started" flag to enginefacadeMike Bayer2018-10-241-0/+8
| | | | | | | | | | | | | | | | Some module reloading scenarios such as that which occurs within mod_wsgi mean that an existing module-level enginefacade is already in the "started" state, however initialization routines from the calling application may still attempt to call the ``.configure`` method. Add a new flag is_started to both _TransactionContextManager and _TransactionFactory so that calling code can check for this state ahead of time; additionally, promote the TypeError raised to a specific subclass enginefacade.AlreadyStartedError to allow for better optimistic schemes. Change-Id: I2f5a9e35c2fae0c28b78beef3dcd2c4794362766 References: I704196711d30c1124e713ac31111a8ea6fa2f1ba
* Imported Translations from ZanataOpenStack Proposal Bot2018-08-141-3/+23
| | | | | | | For more information about this automatic import see: https://docs.openstack.org/i18n/latest/reviewing-translation-import.html Change-Id: I36180c774142f6f268756b373aacd1fd9f5b9d66
* Update reno for stable/rockyOpenStack Release Bot2018-07-262-0/+7
| | | | Change-Id: Ie63b9305295fea38d2e142c2fbbd3b94d9515829
* Imported Translations from ZanataOpenStack Proposal Bot2018-03-011-6/+3
| | | | | | | For more information about this automatic import see: https://docs.openstack.org/i18n/latest/reviewing-translation-import.html Change-Id: I8e745e279e295b1b9a42b661d4da2568ce981e7a
* Merge "Allow connection query string to be passed separately."Zuul2018-02-201-0/+7
|\
View Lorry Controller Status