summaryrefslogtreecommitdiff
path: root/releasenotes
Commit message (Collapse)AuthorAgeFilesLines
...
| * Allow connection query string to be passed separately.Mike Bayer2018-01-301-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The Nova project has made the decision to store the entire contents of the "sql_connection" field in the database, with alterations to the host value, such that various "cells" database URLs can be located using Nova's database itself as a central registry of database URLs. This architecture has produced several problems. The first is that it is impossible to apply parameters to the URL that are local to the client machine; the leading example of this is the MySQL "bind_host" variable, which must match the hostname of the connecting host. Because cells puts these URLs into the database and shares them with all controllers, we have to use a workaround with the read_default_file parameter to specify a controller-local file of options; this is not a standard thing for other database drivers, and these parameters only apply to the MySQL driver and not the SQLAlchemy engine. The next issue is that it is inconvenient to add parameters to the URL at all, once Nova has already been running, as one must manually use Nova's command line tools to alter all the URLs that have already been copied into the database and alter the query parameters with each of those individually, and then restart *all* services who will all receive the parameter (no way to add params to just one controller). Nova's "store the URL in the database" feature only needs to be able to locate the host / database name of the alternate database, and not change the URL tuning parameters. This patch adds a new oslo.db parameter connection_parameters which allows the params to be applied separately from the sql_connection parameter, so that Nova can continue persisting sql_connection but the parameters remain local to the nova.conf file. A URL parameter that truly had to remain persisted in Nova's database (there aren't any) could still be applied at the sql_connection level. This feature is essential not just so that we can again place simple parameters into controller-local files like "bind_host", but also to allow for configuration of SQLAlchemy features such as plugins that do connection pool monitoring. Change-Id: Id4de4b09ec4719cbf8b372629fcf58cf368a33d4
* | Imported Translations from ZanataOpenStack Proposal Bot2018-02-181-2/+18
| | | | | | | | | | | | | | For more information about this automatic import see: https://docs.openstack.org/i18n/latest/reviewing-translation-import.html Change-Id: If554c57465fbf5461a6257d1910bcfb870ca07ea
* | Merge "Reverse role of synchronous_reader"Zuul2018-02-121-0/+8
|\ \
| * | Reverse role of synchronous_readerMike Bayer2018-01-291-0/+8
| |/ | | | | | | | | | | | | | | | | | | | | 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
* | Imported Translations from ZanataOpenStack Proposal Bot2018-01-271-2/+6
| | | | | | | | | | | | | | For more information about this automatic import see: https://docs.openstack.org/i18n/latest/reviewing-translation-import.html Change-Id: Ia0892cf2f39d64aac714e0a36536151a3b64ecfd
* | Update reno for stable/queensOpenStack Release Bot2018-01-242-0/+7
|/ | | | Change-Id: I74e72825ffc6c918f8aa1a3a7890f11cc8006c17
* Imported Translations from ZanataOpenStack Proposal Bot2017-12-061-3/+21
| | | | | | | For more information about this automatic import see: https://docs.openstack.org/i18n/latest/reviewing-translation-import.html Change-Id: I634e66ed72301ab085113bd66dbe869c970d978d
* Remove setting of version/release from releasenotesAndreas Jaeger2017-11-161-9/+4
| | | | | | | | | | | | | | | | | | Release notes are version independent, so remove version/release values. We've found that projects now require the service package to be installed in order to build release notes, and this is entirely due to the current convention of pulling in the version information. Release notes should not need installation in order to build, so this unnecessary version setting needs to be removed. This is needed for new release notes publishing, see I56909152975f731a9d2c21b2825b972195e48ee8 and the discussion starting at http://lists.openstack.org/pipermail/openstack-dev/2017-November/124480.html . Change-Id: Id7d6c1b8463feed6cc984ce666f576800dbeeb25
* Drop MySQL-python dependency from oslo.dbDirk Mueller2017-10-171-0/+8
| | | | | | | | | In order to fade out MySQL-python from OpenStack we need to stop testing it. Add release notes entry and adjust documentation references accordingly. Depends-On: Ie1f07062ed18350bcbb9e7b5e33c7ab2390be9ab Change-Id: Ie17f4543fa3d72b507d88d2c4023a9a5a430419e
* Imported Translations from ZanataOpenStack Proposal Bot2017-10-081-3/+162
| | | | | | | For more information about this automatic import see: https://docs.openstack.org/i18n/latest/reviewing-translation-import.html Change-Id: I49b20ce3f02d1f3ff34212beb91ccdace086a1c7
* Rename idle_timeout to connection_recycle_timeMike Bayer2017-08-151-0/+15
| | | | | | | | | | | | | The "idle_timeout" name and documentation are misleading to users. Rename the option to connection_recycle_time to more closely match that of the underlying SQLAlchemy argument name "pool_recycle", which refers to a time period for which a connection present in the pool for longer than that number of seconds will be closed and replaced with a new one *upon checkout*, to prevent usage of stale connections that may have been closed by server-side reapers. Change-Id: I5e39d5ac81eaa8d85b1dfb18862fe27695ab8b96
* Update reno for stable/pikeOpenStack Release Bot2017-07-282-0/+7
| | | | Change-Id: Id334c7c2a25b81cedcbcf30863d180f78b0c9512
* switch from oslosphinx to openstackdocsthemeDong Ma2017-07-011-3/+7
| | | | Change-Id: I66319c2b4e4ec4c10133151f7a867bdca7a3afa8
* 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>
* Merge "Remove deprecated config option sqlite_db"4.19.0Jenkins2017-03-241-0/+5
|\
| * Remove deprecated config option sqlite_dbChangBo Guo(gcb)2017-03-241-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | Imported Translations from ZanataOpenStack Proposal Bot2017-03-242-6/+71
|/ | | | | | | For more information about this automatic import see: http://docs.openstack.org/developer/i18n/reviewing-translation-import.html Change-Id: I4ef80c33244d1513c011cd8b5556d3047934ac3d
* Update reno for stable/ocataOpenStack Release Bot2017-01-202-0/+7
| | | | Change-Id: Ia791d1c6bba9329be4bd09ffa5f5dcd74eb0be5c
* Merge "utils: deprecate InsertFromSelect properly"Jenkins2016-11-101-0/+6
|\
| * utils: deprecate InsertFromSelect properlyRoman Podoliaka2016-11-041-0/+6
| | | | | | | | | | | | | | | | | | | | This is provided out-of-box by SQLAlchemy versions >= 1.0.0. We've had this class deprecated in docs for some time now, now do it properly by the means of debtcollector and a release note. Closes-Bug: #1439092 Change-Id: I562c35c265014c6b19a81961f236a7a0ca438765
* | Enhanced fixtures for enginefacade-based provisioningMike Bayer2016-11-041-0/+5
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The original idea of enginefacade was that applications would call upon the global _TransactionContextManager given in oslo_db.sqlalchemy.enginefacade. However, as it turns out, virtually no Openstack projects seem to be using that technique, and instead, everyone is creating their own ad-hoc _TransactionContextManager objects and usually establishing it as a module-level global. Nova has two of them. Additionally, projects add configuration to these enginefacades (which IS part of the original idea), and this configuration in some cases is necessary to be present for tests that run as well, a key example being the sqlite_fks flag. The original DbFixture integration provided no way of reusing this configuration. Finally, projects very much tend to use custom fixtures in order to define their database communication. Test classes themselves don't really make use of oslo_db's DbTestCase anymore. This patch introduces a modernized fixture system which, in conjunction with the recent provisioning patch, addresses these use cases. Applications will typically create their own subclasses of these fixtures up front to suit the various testing cases they have, including SQLite fixed, SQLite ad-hoc, and opportunistic. In order to accommodate the fixture-based flow along with the use of testresources for opportunistic database provisioning, a mixin class OpportunisticDbTestMixin is still needed when a test needs to use "opportunistic" testing in order to provide the .resources attribute. The calculation of .resources is moved into the fixture system, but because this attribute is consulted before setUp(), the "opportunistic" fixture must be created early and stored. Closes-Bug: #1548960 Change-Id: I0163e637ffef6d45d2573ebe29b5438911d01fce
* standardize release note page ordering4.14.0Doug Hellmann2016-10-121-2/+2
| | | | | | | | | | In order to support automatically updating the release notes when we create stable branches, we want the pages to be in a standard order. This patch updates the order to be reverse chronological, so the most recent notes appear at the top. Change-Id: Ib364dcc8eb31275a31c83b68d7914263b183e393 Signed-off-by: Doug Hellmann <doug@doughellmann.com>
* Enable release notes translationAndreas Jaeger2016-10-061-0/+3
| | | | | | | | | | | | Releasenote translation publishing is being prepared. 'locale_dirs' needs to be defined in conf.py to generate translated version of the release notes. Note that this repository might not get translated release notes - or no translations at all - but we add the entry here nevertheless to prepare for it. Change-Id: I723a3e5f79db0e2fe0ff22795a5200391c967bff
* Update reno for stable/newtonDoug Hellmann2016-09-012-0/+7
| | | | Change-Id: Icc978097f49708001f24e0154ead7d4316bec018
* Merge "release notes: mention changes in wrap_db_retry()"Jenkins2016-08-101-0/+6
|\
| * release notes: mention changes in wrap_db_retry()Roman Podoliaka2016-07-041-0/+6
| | | | | | | | | | | | | | | | | | Just in case mention the changes done in CR #318135, so that people are aware of those (although, we've double checked everyone passes the argument value explicitly now and that's the only reason the decorator actually performs any retries in downstreams). Change-Id: I263b2078535a3f06461e8905003b484a38d05f08
* | Set a min and max on the connection_debug optionEric Brown2016-07-091-0/+7
| | | | | | | | | | | | | | There is a set allowable minimum and maximum to the connection_debug option of 0 and 100. The config option should enforce this. Change-Id: Ica610ad8fc0875a8be1042f7daba5d0a0c1aad03
* | Deprecate config option sqlite_db for removalChangBo Guo(gcb)2016-07-061-0/+7
|/ | | | | | | | | | We should use config option connection or slave_connection to connect to the database. We can remove it when all consuming projects don't use it anymore. Related-Bug: #1329086 Change-Id: I1960e47b27b5f98f19a07f9899079269bac025cc
* Merge "Make it possible to use enginefacade decorators with class methods"Jenkins2016-06-291-0/+6
|\
| * Make it possible to use enginefacade decorators with class methodsRoman Podoliaka2016-06-271-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | The decorator form can now be used with bound methods after a fix for the related bug was merged. Mention this in docs and release notes, so that people are aware of it. A new test is added to make sure this also works with class methods (as well as to check that the proposed decorator applying order is actually correct). Related-Bug: #1520195 Change-Id: Ifea08114d6d89de9d67fcae397eb94c0afc4d339
* | Imported Translations from ZanataOpenStack Proposal Bot2016-06-291-0/+89
|/ | | | | | | For more information about this automatic import see: https://wiki.openstack.org/wiki/Translations/Infrastructure Change-Id: I3982761ba00120358745cdfc1745346c878c8be3
* Fix typo: 'olso' to 'oslo'Edan David2016-06-021-5/+5
| | | | Change-Id: I1f09eac652f7887d57da5c8d5d1245b0e1d96dd5
* Update reno for stable/mitakaDoug Hellmann2016-03-092-0/+7
| | | | Change-Id: I4a468ee3584bc442a37b0b584e7451dd11bd3dc1
* Increase the default max_overflow valueRoman Podoliaka2016-02-241-0/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It turned out that distribution of WSGI requests between forks is not even when eventlet is used, which can cause pool timeout issues under load, while there are idle workers with open DB connections, which should have served these HTTP requests. The default max_overflow value should be increased to allow DB oriented services (mostly APIs) handle spikes in number of concurrent requests trying to use a DB. At the same time, the default number of greenlets is decreased: I65b40b9906b75146a0085bbe168f1e6bcae82f21 which effectively causes a particular worker to stop accepting new requests it has no resources (DB connections) to handle and allow other forks accept()'ing on the same FD to proceed. Testing was performed using this script: https://gist.github.com/zzzeek/c69138fd0d0b3e553a1f With 100 greenthreads in the pool, 50 DB connections allowed overflow no pool timeout issues were seen with up to 500 concurrent requests done by ab, while current default values (1000/10) could not handle even 100 concurrent requests. See this ML thread for details: http://lists.openstack.org/pipermail/openstack-dev/2015-December/082717.html DocImpact This change potentially increases the number of connections open to the RDBMS server. If you start seeing "too many connections" errors, please check these settings and adjust them appropriately: https://dev.mysql.com/doc/refman/5.5/en/server-system-variables.html#sysvar_max_connections http://www.postgresql.org/docs/current/static/runtime-config-connection.html#GUC-MAX-CONNECTIONS Closes-Bug: #1535375 Change-Id: I2e9c2a71d8231e0dfbefc6293ad319e1e459beec
* add reno for release notes managementDoug Hellmann2016-02-237-0/+300
Change-Id: I6574d2bb21fa8c64290b06ab493f8f7c8b1b7c16 Signed-off-by: Doug Hellmann <doug@doughellmann.com>
View Lorry Controller Status