summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Merge "Reverse role of synchronous_reader" into stable/pikepike-em4.25.2Zuul2018-10-093-11/+21
|\
| * Reverse role of synchronous_readerMike Bayer2018-05-243-11/+21
| | | | | | | | | | | | | | | | | | | | | | | | Repaired the "synchronous_reader" modifier of enginefacade so that it refers to the "writer" engine when set to True, thereby allowing "synchronous" behavior with the writer. When set to False, this is "asynchronous", so this should be associated with the async engines. The flag had the reverse behavior previously. Change-Id: Id7fea7562ba90eb710176d497af103303f230531 Closes-bug: #1746116 (cherry picked from commit 5ca329884d492d78e623e2313142238eb256f1a6)
* | import zuul job settings from project-configDoug Hellmann2018-08-031-0/+9
|/ | | | | | | | | | | | | | | 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: I7d348f4f0689d345069b2becb88062973248c304 Story: #2003250
* Fix sphinx-docs job for stable brancheeldill2018-05-021-0/+5
| | | | | | | | | build-openstack-sphinx-docs jobs fail on stable branches due to the new pip version 10 introduces some previously Warning as Error: in case of calling "pip install" without any package name, the command fails. tox_install.sh is called during docs job without any package passed to pip. Change-Id: Idf418fb327475ddf167db8a85d6eff6456ca8c9b
* Use the new PTI for document buildChangBo Guo(gcb)2018-01-113-5/+16
| | | | | | | | | | | | | For compliance with the Project Testing Interface as described in: https://governance.openstack.org/tc/reference/project-testing-interface.html For more detials information, please refer to: http://lists.openstack.org/pipermail/openstack-dev/2017-December/125710.html Change-Id: Iba311cc69ec5272d8beb433e3589c53f371d5d0a (cherry picked from commit 4f81c419947e2793e3eda4ce8f3664058b5a5d2c)
* Updated from global requirements4.25.1OpenStack Proposal Bot2017-08-111-1/+1
| | | | Change-Id: I807cdf29d6b98801093ef2a9e1c6fd37bd592098
* Update UPPER_CONSTRAINTS_FILE for stable/pikeOpenStack Release Bot2017-07-281-1/+1
| | | | Change-Id: I6788e3e39983b7f002a45c4fa727f2f6550c4a7f
* Update .gitreview for stable/pikeOpenStack Release Bot2017-07-281-0/+1
| | | | Change-Id: I379fd5430b0f7beaa29db55c3a0134c66f119cb6
* Merge "Don't access connection.info if connection is invalidated"4.25.0Jenkins2017-07-172-2/+59
|\
| * Don't access connection.info if connection is invalidatedMike Bayer2017-07-142-2/+59
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The connection.info dictionary comes from the underlying pooled connection, which in a disconnection situation is not there; trying to access it makes it try to reconnect. Inside of rollback(), SQLAlchemy doesn't allow us to reconnect yet because we haven't finished removing the transctional state that corresponds to the now-discarded connection. Therefore we have to check connection.invalidated inside of our rollback handlers before trying to add/remove tokens from connection.info. Change-Id: Icd10ada68d6d53410ac88eca3577f04c5e30087e Resolves-bug: #1704474
* | Update URLs according to document migrationChangBo Guo(gcb)2017-07-112-2/+2
|/ | | | | | | * update setup.cfg with right document links * update HACKING.rst with latest link for hacking Change-Id: I8eb294c1d734f9c76951e4b4b9ebb0f69183f8f3
* Merge "update the docs url in the readme"Jenkins2017-07-111-3/+3
|\
| * update the docs url in the readmeDong Ma2017-07-041-3/+3
| | | | | | | | Change-Id: I0f6b5e516813ffd6b90b7283eb893b0d5c3accd0
* | Merge "Add 'save_and_reraise_exception' method when call 'session.rollback()'"4.24.1Jenkins2017-07-052-6/+29
|\ \ | |/ |/|
| * Add 'save_and_reraise_exception' method when call 'session.rollback()'D G Lee2017-05-192-6/+29
| | | | | | | | | | | | | | | | Maybe we need to know the original exception when exception occurs on method 'session.rollback()'. Change-Id: Iccda37a3279d6f24de69cfccef3e29787f1ac694 Closes-Bug: #1684329
* | turn on warning-is-error in doc buildDong Ma2017-07-034-8/+8
| | | | | | | | Change-Id: I0b64c644f40a2da3242274194d1a5d2858813c25
* | switch from oslosphinx to openstackdocsthemeDong Ma2017-07-013-6/+17
| | | | | | | | Change-Id: I66319c2b4e4ec4c10133151f7a867bdca7a3afa8
* | rearrange content to fit the new standard layout4.24.0Dong Ma2017-07-0112-16/+35
| | | | | | | | | | Change-Id: Idaa0dde5e4fd14213ae1611560897a27e9f72514 Depends-On: Ia750cb049c0f53a234ea70ce1f2bbbb7a2aa9454
* | Updated from global requirementsOpenStack Proposal Bot2017-06-291-1/+1
| | | | | | | | Change-Id: Ib8b85d5867ca2f732a0c64af847fa77310b72948
* | Fix compatibility with SQLAlchemy < 1.1.0Javier Pena2017-06-281-1/+1
| | | | | | | | | | | | | | | | https://review.openstack.org/427970 broke compatibility with SQLAlchemy versions <1.1.0 by using sqlalchemy.dialects.mysql.types in test_ndb.py. Change-Id: I773e0931d4f9f345f8095559eff2eb35e0730027
* | Merge "Enable MySQL Storage Engine selection"Jenkins2017-06-289-0/+371
|\ \
| * | Enable MySQL Storage Engine selectionoorgeron2017-06-269-0/+371
| |/ | | | | | | | | | | | | | | Enables new functionality for selecting InnoDB or MySQL Cluster as a DB storage backend in OpenStack services. Closes-Bug: 1564110 Change-Id: I9f1fd2a87fdf75332de2339d3ff4f08ce9220dcf
* | Merge "Using assertIsNone(xxx) instead of assertEqual(None, xxx)"Jenkins2017-06-161-1/+1
|\ \
| * | Using assertIsNone(xxx) instead of assertEqual(None, xxx)blue552017-06-061-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Following OpenStack Style Guidelines: [1] https://docs.openstack.org/developer/hacking/#unit-tests-and-assertraises [H203] Unit test assertions tend to give better messages for more specific assertions. As a result, assertIsNone(xxx) is preferred over assertEqual(None, xxx) and assertIs(xxx, None) Change-Id: Id0e54ddeb461e56fbc8ec3a4bbc8a581f11430df
* | | Updated from global requirementsOpenStack Proposal Bot2017-06-151-1/+1
| | | | | | | | | | | | Change-Id: I7d078fd50d41fa3f212109366693088673067a09
* | | Updated from global requirementsOpenStack Proposal Bot2017-06-101-1/+1
| | | | | | | | | | | | Change-Id: I235056994f9fce034dca8cea5f800656f5f80f89
* | | 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
|\
View Lorry Controller Status