summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Updated from global requirements4.23.0OpenStack Proposal Bot2017-06-021-1/+1
| | | | Change-Id: I60df9099961cb5cfd97499ecbdec556cdb1f6048
* Updated from global requirementsOpenStack Proposal Bot2017-06-021-1/+1
| | | | Change-Id: I753aa7c6c22707658ccd48e0bcc3337ab12c9951
* Merge "Raise only DbMigrationError from migrate 'upgrade' method"Jenkins2017-05-302-1/+20
|\
| * Raise only DbMigrationError from migrate 'upgrade' methoddineshbhor2017-05-252-1/+20
| | | | | | | | | | | | | | | | | | | | | | | | All the exceptions which are raised from sqlalchemy-migrate upgrade method are not more user friendly to the operator. This patch proposes to convert all the exceptions which will be raised by 'upgrade' method to an oslo_db specific 'DbMigrationError' exception. Related-Bug: #1546441 Change-Id: I28533bedba358281ce302b9b021744387a76c04a
* | Merge "Updated from global requirements"4.22.0Jenkins2017-05-271-1/+1
|\ \
| * | Updated from global requirementsOpenStack Proposal Bot2017-05-261-1/+1
| | | | | | | | | | | | Change-Id: Ica64fbd70c8e9acbed1f74c102f2a84b214fc5ce
* | | add release note for new warning about missing driverDoug Hellmann2017-05-261-0/+14
|/ / | | | | | | | | Change-Id: I7e48a45e392c57901d27389f5797c8ce34492861 Signed-off-by: Doug Hellmann <doug@doughellmann.com>
* | Warn on URL without a drivernameMike Bayer2017-05-242-0/+66
|/ | | | | | | | | | Older installations may still be running with URLs of the form "mysql://user:pass@host/dbname", which defaults to the native MySQL driver that is not supported by eventlet. Warn that URLs should be qualified with an explicit driver, and in the case of MySQL that PyMySQL should be used. Change-Id: Ie973a43c8d056778d02703cf75bfc52a90027dea
* Updated from global requirementsOpenStack Proposal Bot2017-05-231-2/+2
| | | | Change-Id: Iad13d017070007bb3c6eb3b23644b08aa701ebfb
* Merge "Move oslo.context to test-requirements"Jenkins2017-05-232-1/+1
|\
| * Move oslo.context to test-requirementsJulien Danjou2017-05-182-1/+1
| | | | | | | | | | | | It's actually only used in tests. Change-Id: Idee419ab60b6395f5f5d0415711e3f02d992fa5f
* | Updated from global requirements4.21.1OpenStack Proposal Bot2017-05-201-2/+2
| | | | | | | | Change-Id: Icbdc156d1dd30c5524e38880a794e06b03634baf
* | Attach context being used to session/connection infoKevin Benton2017-05-182-16/+50
|/ | | | | | | | | | | | | Attaching a reference to the context to the session/connection is useful for SQLAlchemy event handlers that only get access to the session and need access to the context for additional details. The use case driving this is the related bug where we want to pass conditional update constraints set in the context via the HTTP API down into an SQLAlchemy event listener. Related-Bug: #1493714 Change-Id: I5c08e672782344e8778187e257e03c1a1d1b019a
* Updated from global requirementsOpenStack Proposal Bot2017-05-151-1/+1
| | | | Change-Id: Ie5929cf12a5547694a1d1a846ab29ce320d3afc3
* Updated from global requirements4.21.0OpenStack Proposal Bot2017-04-121-1/+1
| | | | Change-Id: I38d6365f853eadfc2f488eda92f6fdf8f21a7d88
* Updated from global requirementsOpenStack Proposal Bot2017-04-051-1/+1
| | | | Change-Id: I8194aea148813d0165a4fdfe3f1fa6ee878c240c
* Merge "Remove log translations"4.20.0Jenkins2017-03-309-41/+23
|\
| * Remove log translationschenlx2017-03-309-41/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Log messages are no longer being translated. This removes all use of the _LE, _LI, and _LW translation markers to simplify logging and to avoid confusion with new contributions. See: http://lists.openstack.org/pipermail/openstack-i18n/2016-November/002574.html http://lists.openstack.org/pipermail/openstack-dev/2017-March/113365.html Closes-Bug: #1674577 Change-Id: I7553ae7c222f61b6796b72ac4a2b744d3e08fee6
* | Merge "Remove deprecated config option sqlite_db"4.19.0Jenkins2017-03-243-21/+8
|\ \
| * | Remove deprecated config option sqlite_dbChangBo Guo(gcb)2017-03-243-21/+8
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | We deprecated config options sqlite_db in July, 2016 [1], and it shows up in many projects' config files but these projects don't use it either, so it's confusing to our users. It's time to remove it, just use config option connection or slave_connection to connect to the database. [1] https://review.openstack.org/#/c/338047/ Closes-Bug: #1329086 Change-Id: Id269d921e40edf95eb977b011f1753f633b79d18
* | Updated from global requirementsOpenStack Proposal Bot2017-03-241-1/+1
| | | | | | | | Change-Id: Ib0d90cbf6bfee38872e23ff2b8781009ad677d15
* | Imported Translations from ZanataOpenStack Proposal Bot2017-03-2411-376/+71
|/ | | | | | | For more information about this automatic import see: http://docs.openstack.org/developer/i18n/reviewing-translation-import.html Change-Id: I4ef80c33244d1513c011cd8b5556d3047934ac3d
* Updated from global requirementsOpenStack Proposal Bot2017-03-131-1/+1
| | | | Change-Id: Ie77d6c27e999b477bbe233e9d1486dabde05917f
* Merge "Remove unused logging import"4.18.0Jenkins2017-03-031-4/+0
|\
| * Remove unused logging importAnh Tran2017-02-171-4/+0
| | | | | | | | Change-Id: I6e69c3198ef7c1dccd42655fbf10210d132b1eab
* | Merge "Fix db_version checking for sqlalchemy-migrate"Jenkins2017-03-032-1/+38
|\ \
| * | Fix db_version checking for sqlalchemy-migrateBrant Knudson2016-04-122-1/+38
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When a project has multiple migration repos and oslo_db.sqlalchemy.migration.db_version() is called using the one repo as the abs_path, it will attempt to put the repo under version control. The next time it's called with the other abs_path, it would fail rather than attempting to put the repo under version control when using sqlalchemy-migrate. When using alembic, db_version would attempt to put the new abs_path under version control. This change makes it so that when sqlalchemy-migrate is used db_version() will attempt to version control the new abs_path just like when alembic is used. Change-Id: If5e2ae1a72f9118c7aca34e925fdc5e3e8480275
* | | Updated from global requirementsOpenStack Proposal Bot2017-03-033-5/+5
| | | | | | | | | | | | Change-Id: I2a9d0f4ced44c30c6443e613fea2e11b908c5025
* | | Update test requirementRoman Podoliaka2017-03-021-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | Since pbr already landed and the old version of hacking seems not work very well with pbr>=2, we should update it to match global requirement. Change-Id: Id2d358ffdca998066b41c8178aac81d170f82d3c Partial-Bug: #1668848
* | | Establish flush() for "sub" facade contextsKevin Benton2017-02-182-1/+69
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When converting existing session context manager code to use enginefacade, normally a flush() is implicit on a "subtransaction" when it closes. Enginefacade has not maintained this behavior. Ideally, this should have been on by default when enginefacade was first released, but for now add this as a behavioral option for projects that require it. Co-authored-by: Mike Bayer <mike_mp@zzzcomputing.com> Closes-Bug: #1664643 Change-Id: I6f4f439928588cff954e749dfa938425892e0931
* | | Support facade arguments, unstarted facade for patch_engine()Mike Bayer2017-02-163-10/+68
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixed two issues in patch_engine() as used in test suites where facade-level arguments would not be propagated to the internal _TestTransactionFactory, and also if the parent factory weren't "started" the patch operation would fail as it assumes a started factory. This removes the "synchronous_reader" argument from _TestTransactionFactory as this is propagated from the parent _TransactionFactory, where synchronous_reader defaults to True. However, arbitrary keyword arguments are currently allowed to allow for outside projects calling _TestTransactionFactory (currently Neutron). Change-Id: I15f85a0ebfd732c09d7cb92d885c1773c393aabd
* | | Repair unused rollback_reader_sessions parameter.Mike Bayer2017-02-141-25/+72
| |/ |/| | | | | | | | | | | | | | | | | | | The rollback_reader_sessions parameter on _TransactionContext is unused; it is instead acquired from the top level factory. Remove the parameter and also move the documentation for it up to _TransactionFactory.configure_defaults. As there was no documentation for parameters here, add docs for all the other parameters too. Change-Id: I30a2548ad038ae218933c5802c6a8b761705d834
* | Updated from global requirementsOpenStack Proposal Bot2017-02-102-2/+2
| | | | | | | | Change-Id: Icffd9bb89af60b9e5cdec619f285ea77c5b3f4ab
* | Merge "Explain paginate_query doesn't provide parameter offset"Jenkins2017-02-071-0/+5
|\ \
| * | Explain paginate_query doesn't provide parameter offsetChangBo Guo(gcb)2017-02-061-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | OFFSET is a terrible thing to use. It seems to work great when you first use it because your table is only a few hundred rows. six months later, everyone complains the app is incredibly slow - it's because the database is being killed doing linear scans through millions of rows because everyone's doing OFFSET. It not only causes slow and unusable applications but hurts everyone by adding tons of meaningless work to the DB load overall. This pagination function already does the "right" way, which is to order the rows and use WHERE criteria (See http://use-the-index-luke.com/no-offset). This commit add docstring to explain why don't need offset. Co-Authored-By: Mike Bayer <mike_mp@zzzcomputing.com> Change-Id: I6fdb094085d133c8910415efea2eb44225a66216
* | | Merge "Prepare for using standard python tests"Jenkins2017-02-072-0/+61
|\ \ \
| * | | Prepare for using standard python testsAndreas Jaeger2017-02-062-0/+61
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add simple script to setup mysql and postgresql databases, this script can be run by users during testing and will be run by CI systems for specific setup before running unit tests. This is exactly what is currently done by OpenStack CI in project-config. This allows to change in project-config the python-db jobs to python-jobs since python-jobs will call this script initially. See also http://lists.openstack.org/pipermail/openstack-dev/2016-November/107784.html Update CONTRIBUTING.rst for this. Needed-By: Ia298e25f9b15a2dcfc4553ea058fc2c0f3705a8b Change-Id: I825b72e3f645d02f7efdb3315a12825a8c937759
* | | Merge "Update reno for stable/ocata"Jenkins2017-02-062-0/+7
|\ \ \ | |/ / |/| |
| * | Update reno for stable/ocataOpenStack Release Bot2017-01-202-0/+7
| | | | | | | | | | | | Change-Id: Ia791d1c6bba9329be4bd09ffa5f5dcd74eb0be5c
* | | Updated from global requirementsOpenStack Proposal Bot2017-01-211-1/+1
|/ / | | | | | | Change-Id: I7a401a55826924858ddc396ce19530b8bda3bcf7
* | Merge "Remove references to Python 3.4"Jenkins2017-01-192-2/+1
|\ \
| * | Remove references to Python 3.4Eric Brown2017-01-172-2/+1
| | | | | | | | | | | | | | | | | | | | | Now that there exists only a gate job for Python 3.5 and not 3.4, we should remove those references to the 3.4 that is untested. Change-Id: Ic2e61f28bc82f64814a528d210d1dee8d79b49e5
* | | Coerce booleans to integer values in paginate_queryKevin Benton2017-01-172-3/+29
|/ / | | | | | | | | | | | | | | This will avoid a traceback resulting from using > or < on a boolean value (example in bug report). Change-Id: I4b90f18737e62bb35bacf75ad7a85603fb7b45cc Closes-Bug: #1656947
* | Merge "docs: mention that it's possible to use Connection directly"4.17.0Jenkins2017-01-041-0/+15
|\ \
| * | docs: mention that it's possible to use Connection directlyRoman Podoliaka2016-12-121-0/+15
| | | | | | | | | | | | | | | | | | | | | | | | Sometimes people just do not need the ORM part and a Session at all. Mention the fact, that it's possible to ask for a Connection in enginefacade. Change-Id: I7a135be7149cd3fa140e0268fea5a17f23f402b2
* | | Modify word "whetever" to "whether"ahdj0072016-12-291-1/+1
| | | | | | | | | | | | Change-Id: I627b1fd01d01d79ed4a4fe131f5edec733703635
* | | Updated from global requirementsOpenStack Proposal Bot2016-12-221-1/+1
| | | | | | | | | | | | Change-Id: I30a9d74d90479d8d335dd2e1f097b1fcefd53cf8
* | | Merge "Add Constraints support"Jenkins2016-12-212-1/+34
|\ \ \
| * | | Add Constraints supportTony Breeds2016-12-202-1/+34
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Adding constraints support to libraries is slightly more complex than services as the libraries themselves are listed in upper-constraints.txt which leads to errors that you can't install a specific version and a constrained version. This change adds constraints support by also adding a helper script to edit the constraints to remove oslo.db. Change-Id: I31febfe00698e36f4c2e0e41c3f7bf64acf47adf
* | | Support packet sequence wrong errorMike Bayer2016-12-142-0/+9
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In I484237c28a83783689bb8484152476de33f20e3a, we observed MariaDB-specific error code 1927 as a new kind of disconnect situation. In some failure-mode testing we are also observing with PyMySQL that a stale connection, when it is attempted to be used for the initial ping, does not return any error code but instead trips up PyMySQL with packets sequence numbers (this is an internal value used by the MySQL client/server protocol to track messages). The connection is definitely not recoverable in this state so this also needs to be a disconnect situation so that the ping listener refreshes the connection pool. Change-Id: Iee1c4533e2457acc30e2046b63145c2502012c5f References: https://bugs.launchpad.net/tripleo/+bug/1642944
View Lorry Controller Status