summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Add local bindep.txtstable/steinElod Illes2019-07-012-0/+20
| | | | | | | | | | | | | | As it was announced [1] global bindep-fallback.txt was removed and now projects need to have a local bindep.txt to be able to install binary dependencies for testing. In test jobs the script tools/test-setup.sh is called which requires mysql and postgres servers and clients to be installed. [1] http://lists.openstack.org/pipermail/openstack-discuss/2019-June/007272.html Change-Id: I6b237ecf55ff440b5f5c956ee849a1927bb15441 (cherry picked from commit f34e53ebf7670f51f16d5d96412a42fa7f3a8232)
* OpenDev Migration PatchOpenDev Sysadmins2019-04-191-1/+1
| | | | | | | | | | | | | | | This commit was bulk generated and pushed by the OpenDev sysadmins as a part of the Git hosting and code review systems migration detailed in these mailing list posts: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html Attempts have been made to correct repository namespaces and hostnames based on simple pattern matching, but it's possible some were updated incorrectly or missed entirely. Please reach out to us via the contact information listed at https://opendev.org/ with any questions you may have.
* Merge "Update UPPER_CONSTRAINTS_FILE for stable/stein" into stable/steinZuul2019-03-251-1/+1
|\
| * Update UPPER_CONSTRAINTS_FILE for stable/steinOpenStack Release Bot2019-03-181-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | Update the URL to the upper-constraints file to point to the redirect rule on releases.openstack.org so that anyone working on this branch will switch to the correct upper-constraints list automatically when the requirements repository branches. Until the requirements repository has as stable/stein branch, tests will continue to use the upper-constraints list on master. Change-Id: I258601b7d6888299dca1aa238b4049252ee0c317
* | Merge "Update .gitreview for stable/stein" into stable/steinZuul2019-03-251-0/+1
|\ \ | |/
| * Update .gitreview for stable/steinOpenStack Release Bot2019-03-181-0/+1
| | | | | | | | Change-Id: I2aff0151f21f645e64ea82b0ab5b15a3f9b5d724
* | Bump psycopg lower-constraint to 2.7stein-em4.45.0Ben Nemec2019-03-223-3/+3
|/ | | | | | | | | Earlier versions don't work with postgresql 10, which is now showing up in distros. Change-Id: I56589eb4ac55bec426d16f355398720f2994edcb Closes-Bug: 1821400 (cherry picked from commit 57333e902a3747715b2f13ea63477cc4aedc2129)
* Merge "Resolve SAWarning in Query.soft_delete()"4.44.0Zuul2019-02-131-3/+3
|\
| * Resolve SAWarning in Query.soft_delete()Mike Bayer2019-02-011-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We currently see a lot of warnings like this from the soft_delete() method: sqlalchemy.exc.SAWarning: Evaluating non-mapped column expression 'updated_at' onto ORM instances; this is a deprecated use case. Please make use of the actual mapped columns in ORM-evaluated UPDATE / DELETE expressions. This is because the "evaluate" synchronization strategy would like to search for objects and update them based on the UPDATE criteria passed, however the columns given, literal_column('id'), literal_column('updated_at'), are not mapped to anything. The evaluator has to make a guess that the string contained in these expressions should be matched to a mapped attribute on the given entity and this guess was first removed in [1], then added back in [2] with a warning (likely since oslo.db is invoking it). This uses the actual entity-mapped column for the query rather than the literal string column. [1] https://docs.sqlalchemy.org/en/latest/changelog/changelog_12.html#change-b1e620dece39006ab44c47044e9a6fee [2] https://docs.sqlalchemy.org/en/latest/changelog/changelog_12.html#change-dff3a469788c81a46440584406cb22be Change-Id: I192e84ce757d12d33085a209dd58d8ea46fb90fb Closes-Bug: #1814199
* | exc_filters: fix deadlock detection for MariaDB/Galera clusterPierre-Samuel Le Stang2019-02-082-0/+8
|/ | | | | | | | | | | MariasDB/Galera cluster server produces an error like: (1213, u'Deadlock: wsrep aborted transaction') which is currently not detected properly and, thus, not retried. Change-Id: Ifb4a81d50e490e734e12986e51efd6bd3c339c31 Signed-off-by: Pierre-Samuel Le Stang <pierre-samuel.le-stang@corp.ovh.com>
* Merge "Update hacking version"Zuul2019-01-222-3/+3
|\
| * Update hacking versionZhijunWei2019-01-032-3/+3
| | | | | | | | | | | | | | | | update the hacking to latest, due to [1] [1]: https://github.com/openstack/oslo.db/blob/master/HACKING.rst Change-Id: I04147f3cbcb9c89a9a1afc1bcb299be8bdf06718
* | Merge "Use template for lower-constraints"Zuul2019-01-091-11/+6
|\ \
| * | Use template for lower-constraintsAndreas Jaeger2018-12-201-11/+6
| |/ | | | | | | | | | | | | | | | | | | | | Small cleanups: * Use openstack-lower-constraints-jobs template, remove individual jobs. * Sort list of templates Change-Id: I96e67b9d57710d707328a514d837bfe95d976ce4 Needed-By: https://review.openstack.org/623229
* | Remove convert_unicode flag4.43.0Mike Bayer2018-12-211-1/+0
|/ | | | | | | | | | | | | | This flag is to be deprecated in SQLAlchemy version 1.3, as it is a leftover from the pre-Python 3 legacy days when DBAPIs under Python 2 would crash if you passed them a u'' object. While still available in 1.3, it will emit a deprecation warning, so it's time to stop using this flag and to locate any downstream Openstack projects that might be relying on its behavior in a Python 2 context; the flag has no real effect on Python 3. Change-Id: I01984b4ff7e03dcf91ef8dcb05da67dda8270ae3 References: https://github.com/sqlalchemy/sqlalchemy/issues/4393
* Update mailinglist from dev to discussZhongShengping2018-12-051-1/+1
| | | | | | | openstack-dev was decomissioned this night in https://review.openstack.org/621258 Update openstack-dev to openstack-discuss Change-Id: I773a629ab2fb8273004da92a217cd09f39132108
* Merge "Move warnings to their own module"4.42.0Zuul2018-10-304-28/+55
|\
| * Move warnings to their own moduleStephen Finucane2018-10-174-28/+55
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Raising warnings from an exception module can result in a rather confusing message: Running command: '/usr/bin/nova-scheduler ' /.../sqlalchemy/enginefacade.py:332: NotSupportedWarning: Configuration option(s) ['use_tpool'] not supported exception.NotSupportedWarning For someone not used to Python's 'warning' infrastructure, this can look worse than it is, as seen at [1]. While this particular warning was resolved in change I4a5f8958c3e, it's possible that a similar warning could be raised for other options. Best to move this out of the 'exception' module and into something more sensible. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1639423 Change-Id: I8e0480fb11123067a111ed6aeda6b47614615645 Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
* | Add "is_started" flag to enginefacadeMike Bayer2018-10-243-1/+54
|/ | | | | | | | | | | | | | | | 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
* Clean up .gitignore references to personal toolsZhongShengping2018-10-151-4/+11
| | | | | | | | | | | | | | | | | | | | | | | | Developers run all sorts of different tools within Git repositories, any of which can leave their own special trashfiles all over the place. We can't every hope to catalog them all, so better to recommend developers simply configure a global core.excludesfile to filter the irrelevant files which tend to get created by their personal choice of tools. To this end, remove the long-standing sections for "Mr Developer" and "Editors" since their mere existence here sends the signal that we welcome (and have time to review) additions for any old tool someone ever might happen to try. Also add a comment block explaining this, for clarity. We can, and should of course, continue to list files created by the tools recommended by our workflow (test frameworks called from tox, documentation and packaging builds, et cetera). This change is a port of I1b41efac219fca44e2548fc36633724d0ecfc0cb from the openstack-dev/oslo-cookiecutter repository. Change-Id: I8ba491deac8de5d9f2a8ceefba64c0c6a73f92d1
* Merge "Don't quote {posargs} in tox.ini"Zuul2018-10-101-1/+1
|\
| * Don't quote {posargs} in tox.iniVieri2018-10-091-1/+1
| | | | | | | | | | | | | | | | Quotes around {posargs} cause the entire string to be combined into one arg that gets passed to stestr. This prevents passing multiple args (e.g. '--concurrency=16 some-regex') Change-Id: Id8b5f9e1e334609d39a58706ac2039240f0ce9cb
* | Always build universal wheelsHervé Beraud2018-10-091-1/+1
|/ | | | | | | All of our projects are pure python, so we can build universal wheels by default. Change-Id: Ifbba76848c79be9415c7305f90d020973d3bb116
* Fix FOREIGN KEY messages for MariaDB 10.2, 10.34.41.14.41.0Mike Bayer2018-08-301-4/+4
| | | | | | | | | | | | | | | | | | | | | | | MariaDB 10.2 and 10.3 have changed the format diplayed for MySQL error 1091, adding the phrase "FOREIGN KEY", changing the quoting style of the constraint name, and replacing the phrase "column/key" with the word "it". Adjust the regular expression in exc_filters to accommodate these. - "check that column/key" -> "check that constraint/column/key" https://github.com/MariaDB/server/commit/db7edfed17efe6bc - single quotes -> backticks - "check that constraint/column/key" -> "check that it" https://github.com/MariaDB/server/commit/99e48cb1d94e2d88 - "Can't DROP" -> "Can't DROP FOREIGN KEY" https://github.com/MariaDB/server/commit/5c764a0eb82c87ac Change-Id: I165c595edbbdc101ebd2367ca5680b6cd81eaa7b
* Merge "add lib-forward-testing-python3 test job"Zuul2018-08-271-0/+1
|\
| * add lib-forward-testing-python3 test jobDoug Hellmann2018-08-111-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | This is a mechanically generated patch to add a functional test job running under Python 3 as part of the python3-first goal. See the python3-first goal document for details: https://governance.openstack.org/tc/goals/stein/python3-first.html Change-Id: Idc7f9fc739449683a3a5fbcdd080a5105f061e85 Story: #2002586 Task: #24322
* | 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
* add python 3.6 unit test jobDoug Hellmann2018-08-071-0/+1
| | | | | | | | | | | | This is a mechanically generated patch to add a unit test job running under Python 3.6 as part of the python3-first goal. See the python3-first goal document for details: https://governance.openstack.org/tc/goals/stein/python3-first.html Change-Id: I08f1b22e5d244cf0d4a263707b13286e941f6fde Story: #2002586 Task: #24322
* import zuul job settings from project-configDoug Hellmann2018-08-031-0/+8
| | | | | | | | | | | | | | | This is a mechanically generated patch to complete step 1 of moving the zuul job settings out of project-config and into each project repository. Because there will be a separate patch on each branch, the branch specifiers for branch-specific jobs have been removed. See the python3-first goal document for details: https://governance.openstack.org/tc/goals/stein/python3-first.html Change-Id: Ie480cd3681b0a3eedbaebe1f30b7a863c87360ec Story: #2003250
* Update reno for stable/rockyOpenStack Release Bot2018-07-262-0/+7
| | | | Change-Id: Ie63b9305295fea38d2e142c2fbbd3b94d9515829
* Switch to stestrVu Cong Tuan2018-07-138-33/+20
| | | | | | | | | | According to Openstack summit session [1], stestr is maintained project to which all Openstack projects should migrate. Let's switch to stestr as other projects have already moved to it. [1] https://etherpad.openstack.org/p/YVR-python-pti Change-Id: Ifd51e726de277d33ff61db47110bf8b5563fcda7
* Merge "Rename enginefacade.async to enginefacade.async_"4.40.0Zuul2018-07-042-6/+39
|\
| * Rename enginefacade.async to enginefacade.async_Mike Bayer2018-07-022-6/+39
| | | | | | | | | | | | | | | | | | | | Python 3.7 now makes "async" a keyword, so deprecate the "async" name and replace with "async_". Additionally, use attribute name access only in order to implement and test "async" as it won't work under Python 3.7. Closes-Bug: #1775866 Change-Id: Ifb2c59c2cfbd615b04570b31fcfe868f4ffea3c6
* | Add release notes to README.rstmelissaml2018-06-211-0/+1
| | | | | | | | Change-Id: Ieb5a1c097242542d2fdada305f223d2b43c6b0c6
* | Remove most server_default comparison logic4.39.0Mike Bayer2018-06-154-22/+7
|/ | | | | | | | | | | | | | | | | | Added a new test case that covers comparison of a MySQL server default defined as text("0") in the model as well as in the database. The MySQL default comaprison logic in oslo.db was not accommodating of the model side here being a text() construct. As modern Alembic versions supports most of the use cases tested here, remove all server defaut comparison logic except for the boolean comparison workaround. Alembic minimum is bumped to 0.9.6; the issue repaired between 0.8.10 and 0.9.6 is http://alembic.zzzcomputing.com/en/latest/ changelog.html#change-5459a7552a17d8b658f0f710bedf6da0 Depends-on: I1a8244edae47b04b7b1fed54e577d6534945bcd8 Closes-bug: #1776527 Change-Id: I48a103e28d86128ea84466da4d9d6faab1dd9a9d
* remove sqla_09 test environmentDoug Hellmann2018-06-061-5/+0
| | | | | | | We no longer support SQLAlchemy 0.9.0, so remove the test environment. Change-Id: I614945b178ee09fe3c4c6c61c9356d072d776639 Signed-off-by: Doug Hellmann <doug@doughellmann.com>
* fix tox python3 overridesDoug Hellmann2018-06-061-1/+7
| | | | | | | | | | | | | | | We want to default to running all tox environments under python 3, so set the basepython value in each environment. We do not want to specify a minor version number, because we do not want to have to update the file every time we upgrade python. We do not want to set the override once in testenv, because that breaks the more specific versions used in default environments like py35 and py36. Change-Id: I31a207868c07e08ae27c14635d52506021032cb7 Signed-off-by: Doug Hellmann <doug@doughellmann.com>
* Remove stale pip-missing-reqs tox test4.38.0Kenneth Giusti2018-05-011-9/+1
| | | | | | | | | | pip_missing_reqs tool is no longer maintained and has broken with release 10 of pip Refer to: http://lists.openstack.org/pipermail/openstack-dev/2018-April/130027.html Change-Id: I78b50d28d7d3d06f210a7027b2a74426c891b652
* Deprecate min_pool_sizeErik Olof Gunnar Andersson2018-04-301-0/+3
| | | | | | | | | | This option has for a long time done nothing in oslo.db and sqlalchemy does not support this convention. As such I recommend that we deprecate and eventually remove the option. Closes-bug: #1764786 Change-Id: Ib07b7b4200b5cf3a34b8eed441e6754da7d446cf
* List PyMySQL first in installation docsBen Nemec2018-04-241-2/+2
| | | | | | | | | | It's by far the most tested driver with oslo.db so it makes sense to have it first in the list of driver options. Mostly this is just to have a change to merge so the reno jobs get run again though. Change-Id: I5a9a05b6c3e3008cb1dfefc2df397003c2cbc7fd
* Trivial: Update pypi url to new url4.37.0Tovin Seven2018-04-201-2/+2
| | | | | | | | | Pypi url changed from [1] to [2] [1] https://pypi.python.org/pypi/<package> [2] https://pypi.org/project/<package> Change-Id: Ie8b29b4171dcc833a9178a80ba6d277a2bf3a747
* Merge "Improve exponential backoff for wrap_db_retry"Zuul2018-04-172-7/+90
|\
| * Improve exponential backoff for wrap_db_retryYikun Jiang2018-04-132-7/+90
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The @oslo_db.api.wrap_db_retry is used for db.api methods retrying. If db_error raised, the decorator help us to call the api methods again after a few seconds(accurately, is 2**retry_times seconds). If the db_error is deadlock error, the old wrap_db_retry is not so suitable anymore. As we know, some deadlocks cause because we call some methods(transactions) concurrently. If we only retry after stable 2**retry_times seconds, we will recall the method concurrently again. In order to minimize the chance of regenerating a deadlock and reduce the average sleep time, we propose to add some random jitter to the delay period by default when the deadlock error is detected. Change-Id: I206745708570f1f292529ff58eee9b83fc09a9f2 Closes-bug: #1737869
* | Merge "set default python to python3"4.36.0Zuul2018-04-161-1/+2
|\ \
| * | set default python to python3Doug Hellmann2018-04-131-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | Set the default python to python3 except for the py27 environment. We have to set that explicitly to override the new default. Change-Id: I8557195409a559950da6c95aece5787195f31ad6 Signed-off-by: Doug Hellmann <doug@doughellmann.com>
* | | uncap eventletDoug Hellmann2018-04-111-1/+1
|/ / | | | | | | | | | | | | | | | | | | We will manage the eventlet version using constraints now. See the thread starting at http://lists.openstack.org/pipermail/openstack-dev/2018-April/129096.html for more details. Change-Id: Id852a3e6c7f9ac39001618384ced8289c2e6866e Signed-off-by: Doug Hellmann <doug@doughellmann.com>
* | add lower-constraints jobDoug Hellmann2018-03-243-0/+85
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Create a tox environment for running the unit tests against the lower bounds of the dependencies. Create a lower-constraints.txt to be used to enforce the lower bounds in those tests. Add openstack-tox-lower-constraints job to the zuul configuration. See http://lists.openstack.org/pipermail/openstack-dev/2018-March/128352.html for more details. Change-Id: I33404e115161a430ce0587bf203450c8145db0a0 Depends-On: https://review.openstack.org/555034 Signed-off-by: Doug Hellmann <doug@doughellmann.com>
* | Add testresources / testscenarios to requirements.txt4.35.0Mike Bayer2018-03-162-2/+4
| | | | | | | | | | | | | | | | | | | | | | oslo.db is consumed by the test suites of downstream libraries as a test dependency; they make use of the oslo_db.sqlalchemy.test_fixtures module which imports testresources and testscenarios, therefore these are normal requirements of oslo.db; they are not limited to test requirements. Change-Id: I240fbc28ddf238614ff37e742a1415a5566bcd2d Closes-bug: #1756352
* | Updated from global requirementsOpenStack Proposal Bot2018-03-153-2/+5
| | | | | | | | Change-Id: Ia4e66a804bea3eee74fedc3c5a7f610cb05d9c8c
* | Merge "Remove tox_install.sh and align constraints consumption"4.34.0Zuul2018-03-094-54/+22
|\ \
View Lorry Controller Status