summaryrefslogtreecommitdiff
path: root/releasenotes
Commit message (Collapse)AuthorAgeFilesLines
* 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: I80f227a59c36693c83bb94890536745610ba2393
* Fix typo in quorum-related variables for RabbitMQDmitriy Rabotyagov2023-02-141-0/+6
| | | | | | | | | | In [1] there was a typo made in variable names. To prevent even futher awkwardness regarding variable naming, we fix typo and publish a release note for ones that already using variables in their deployments. [1] https://review.opendev.org/c/openstack/oslo.messaging/+/831058 Change-Id: Icc438397c11521f3e5e9721f85aba9095e0831c2
* Support overriding class for get_rpc_* helper functions14.2.0Tobias Urdin2023-01-231-0/+5
| | | | | | | | | | | | | | | | | | We currently do not support overriding the class being instantiated in the RPC helper functions, this adds that support so that projects that define their own classes that inherit from oslo.messaging can use the helpers. For example neutron utilizes code from neutron-lib that has it's own RPCClient implementation that inherits from oslo.messaging, in order for them to use for example the get_rpc_client helper they need support to override the class being returned. The alternative would be to modify the internal _manual_load variable which seems counter-productive to extending the API provided to consumers. Change-Id: Ie22f2ee47a4ca3f28a71272ee1ffdb88aaeb7758
* Merge "Remove logging from ProducerConnection._produce_message"14.1.0Zuul2022-12-211-0/+8
|\
| * Remove logging from ProducerConnection._produce_messageGuillaume Espanel2022-08-031-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | In impl_kafka, _produce_message is run in a tpool.execute context but it was also calling logging functions. This could cause subsequent calls to logging functions to deadlock. This patch moves the logging calls out of the tpool.execute scope. Change-Id: I81167eea0a6b1a43a88baa3bc383af684f4b1345 Closes-bug: #1981093
* | Merge "Implement get_rpc_client function"Zuul2022-12-011-0/+11
|\ \
| * | Implement get_rpc_client functionTobias Urdin2022-10-251-0/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We already expose functions to handle the instantiation of classes such as RPCServer and RPCTransport but the same was never done for RPCClient so the API is inconsistent in its enforcement. This adds a get_rpc_client function that should be used instead of instatiating the RPCClient class directly to be more consistent. This also allows to handle more logic inside the function in the future such as if implementations for an async client is implemented, as investigation in [1] has shown. [1] https://review.opendev.org/c/openstack/oslo.messaging/+/858936 Change-Id: Ia4d1f0497b9e2728bde02f4ff05fdc175ddffe66
* | | Merge "Force creating non durable control exchange when a precondition failed"Zuul2022-11-161-0/+5
|\ \ \ | |/ / |/| |
| * | Force creating non durable control exchange when a precondition failedHervé Beraud2021-12-151-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Precondition failed exception related to durable exchange config may be triggered when a control exchange is shared between services and when services try to create it with configs that differ from each others. RabbitMQ will reject the services that try to create it with a configuration that differ from the one used first. This kind of exception is not managed for now and services can fails without handling this kind of issue. These changes catch this kind exception to analyze if they related to durable config. In this case we try to re-declare the failing exchange/queue as non durable. This problem can be easily reproduced by running a local RabbitMQ server. By setting the config below (sample.conf): ``` [DEFAULT] transport_url = rabbit://localhost/ [OSLO_MESSAGING_RABBIT] amqp_durable_queues = true ``` And by running our simulator twice: ``` $ tox -e venv -- python tools/simulator.py -d rpc-server -w 40 $ tox -e venv -- python tools/simulator.py --config-file ./sample.conf -d rpc-server -w 40 ``` The first one will create a default non durable control exchange. The second one will create the same default control exchange but as durable. Closes-Bug: #1953351 Change-Id: I27625b468c428cde6609730c8ab429c2c112d010
* | | 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: Ic1020b39172981abcc9fc3d66fc6ec58f440a456
* | | Change default value of "heartbeat_in_pthread" to False14.0.0Slawek Kaplonski2022-08-161-0/+9
| |/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As was reported in the related bug some time ago, setting that option to True for nova-compute can break it as it's non-wsgi service. We also noticed same problems with randomly stucked non-wsgi services like e.g. neutron agents and probably the same issue can happen with any other non-wsgi service. To avoid that this patch changes default value of that config option to be False. Together with [1] it effectively reverts change done in [2] some time ago. [1] https://review.opendev.org/c/openstack/oslo.messaging/+/800621 [2] https://review.opendev.org/c/openstack/oslo.messaging/+/747395 Related-Bug: #1934937 Closes-Bug: #1961402 Change-Id: I85f5b9d1b5d15ad61a9fcd6e25925b7eeb8bf6e7
* | Merge "Add quorum queue control configurations"13.0.0Zuul2022-06-131-0/+6
|\ \
| * | Add quorum queue control configurationshamza alqtaishat2022-04-061-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | the quorum queue type add features that did not exist before or not handled in rabbitmq the following link shows some of them https://blog.rabbitmq.com/posts/2020/04/rabbitmq-gets-an-ha-upgrade/ the options below control the quorum queue and ensure the stability of the quorum system x-max-in-memory-length x-max-in-memory-bytes x-delivery-limit which control the memory usage and handle message poisoning Closes-Bug: #1962348 Change-Id: I570227d6102681f4f9d8813ed0d7693a1160c21d
* | | Merge "Add a new option to enforce the OpenSSL FIPS mode"Zuul2022-04-261-0/+10
|\ \ \
| * | | Add a new option to enforce the OpenSSL FIPS modeHervé Beraud2021-11-081-0/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This option ``ssl_enforce_fips_mode`` allow us to enforce the FIPS mode if supported by the version of python in use. https://en.wikipedia.org/wiki/Federal_Information_Processing_Standards Change-Id: I50c7de71bfd38137eb83d23e910298946507ce9f
* | | | 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: I3d2b041769c5c14a7d391c223dc499218a937e76
* | | Merge "Adding support for rabbitmq quorum queues"12.13.0Zuul2022-02-081-0/+11
|\ \ \
| * | | Adding support for rabbitmq quorum queuesHervé Beraud2022-02-051-0/+11
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | https://www.rabbitmq.com/quorum-queues.html The quorum queue is a modern queue type for RabbitMQ implementing a durable, replicated FIFO queue based on the Raft consensus algorithm. It is available as of RabbitMQ 3.8.0. the quorum queues can not be set by policy so this should be done when declaring the queue. To declare a quorum queue set the x-queue-type queue argument to quorum (the default is classic). This argument must be provided by a client at queue declaration time; it cannot be set or changed using a policy. This is because policy definition or applicable policy can be changed dynamically but queue type cannot. It must be specified at the time of declaration. its good for the oslo messaging to add support for that type of queue that have multiple advantaged over mirroring. If quorum queues are sets mirrored queues will be ignored. Closes-Bug: #1942933 Change-Id: Id573e04c287e034e50626daf6e18a34735d45251
* | | [rabbit] use retry parameters during notification sendingBalazs Gibizer2022-01-121-0/+8
| |/ |/| | | | | | | | | | | | | | | | | | | | | | | The rabbit backend now applies the [oslo_messaging_notifications]retry, [oslo_messaging_rabbit]rabbit_retry_interval, rabbit_retry_backoff and rabbit_interval_max configuration parameters when tries to establish the connection to the message bus during notification sending. This patch also clarifies the differences between the behavior of the kafka and the rabbit drivers in this regard. Closes-Bug: #1917645 Change-Id: Id4ccafc95314c86ae918336e42cca64a6acd4d94
* | Merge "Remove deprecation of heartbeat_in_pthread"12.11.0Zuul2021-10-211-0/+6
|\ \
| * | Remove deprecation of heartbeat_in_pthreadHervé Beraud2021-10-141-0/+6
| |/ | | | | | | | | | | | | | | | | | | | | | | | | In some circumstances services can be executed outside of mod_wsgi and in a monkey patched environment. In this context we need to leave the possibility to users to execute the heartbeat in a green thread. The heartbeat_in_pthread was tagged as depreacted few months and planned for a future removal. These changes drop this deprecation to allow to enable green threads if needed. Closes-Bug: #1934937 Change-Id: Iee2e5a6f7d71acba70bbc857f0bd7d83e32a7b8c
* | 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: Ia40ac2ccee4fe230605f3183b0b432b0e31bff04
* Add Support For oslo.metricsChing Kuo2021-06-081-0/+8
| | | | | | | | | | | | | | This commit added support to send rpc metrics to oslo.metrics. Changes includes: - Adding client wrapper for oslo.metrics to process metrics information and send to oslo.metrics socket - Modify rpc client to send metric when certain rpc events happens For more information on oslo.metrics https://opendev.org/openstack/oslo.metrics Change-Id: Idf8cc0e52ced1f697ac4048655eff4c956fd5c79
* Fix formatting of release listPierre Riteau2021-04-161-13/+13
| | | | Change-Id: I1f859a964de7f96e5decdec0977faa355b6a2a60
* 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: I2deb189cfdd7420e69060cd89c45b03b43c211af
* Merge "Correctly handle missing RabbitMQ queues"12.7.1Zuul2021-02-091-0/+5
|\
| * Correctly handle missing RabbitMQ queuesHervé Beraud2021-02-041-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently, setting the '[oslo_messaging] direct_mandatory_flag' config option to 'True' (the default) will result in a 'MessageUndeliverable' exception being raised when sending a reply if a RabbitMQ queue is missing [1]. It was the responsibility of the application to handle this exception, however, many applications are not doing so. This has resulted in a number of bug reports. Start handling this error condition, using a retry loop to attempt to resend the message and work around any temporary glitches. Since attempting to send a reply will will no longer raise an exception, there is little benefit in retaining the '[oslo_messaging] direct_mandatory_flag' config option: users setting this to False will simply not benefit from the retry logic and improved logging added here. This option is already deprecated though and will be fully removed in a future release. [1] https://www.rabbitmq.com/channels.html Change-Id: Id5cddbefbe24ef100f1cc522f44430df77d217cb Closes-Bug: #1905965
* | Merge "remove unicode from code"Zuul2021-02-031-1/+1
|\ \ | |/ |/|
| * remove unicode from codexuanyandong2021-01-031-1/+1
| | | | | | | | Change-Id: Ib2b816728307166450a4cea2ccdb3c4b550a0713
* | Deprecate the mandatory flagHervé Beraud2021-02-011-0/+5
|/ | | | | | It will not be possible to deactivate this functionality anymore. Change-Id: I1cbafff03349f7da9224de46285707fbf2a81a68
* Merge "Run rabbitmq heartbeat in python thread by default"Zuul2020-10-151-0/+10
|\
| * Run rabbitmq heartbeat in python thread by defaultHervé Beraud2020-08-271-0/+10
| | | | | | | | | | | | | | | | | | | | Removing the experimental nature of this feature and activating it by default. Now to run heartbeat in a green thread users should set this option to False. Also deprecating this option to prepare future removal and force to always run heartbeat in a python thread whatever the context. Change-Id: I32a6c4ad0a456282ec02b5e4c8309489b3c17553
* | 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: I0e5758da8c95474b1ddda5419f80ae94da71d147 Sem-Ver: feature
* | Merge "Add a ping endpoint to RPC dispatcher"12.4.0Zuul2020-08-281-0/+13
|\ \ | |/ |/|
| * Add a ping endpoint to RPC dispatcherArnaud Morin2020-08-181-0/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The purpose of this patch is to add an endpoint directly in RPC dispatcher, so this endpoint will always be available, in a cross project manner, without the need for projects to manage it by themself. This endpoint stay disabled by default, so this change is harmless without a specific configuration option. To enable this ping endpoint, an operator will just have to add a new parameter in the [DEFAULT] section, alongside with rpc_response_timeout [DEFAULT] rpc_ping_enabled=true # default is false The purpose of this new endpoint is to help operators do a RPC call (a ping) toward a specific RPC callback (e.g. a nova-compute, or a neutron-agent). This is helping a lot for monitoring agents (for example, if agents are deployed in a kubernetes pod). The endpoint is named oslo_rpc_server_ping. Change-Id: I51cf67e060f240e6eb82260e70a057fe599f9063 Signed-off-by: Arnaud Morin <arnaud.morin@corp.ovh.com>
* | Cancel consumer if queue downshenjiatong2020-07-311-0/+6
|/ | | | | | | | | | | | | | | | | | | | | | | | Previously, we have switched to use default exchanges to avoid excessive amounts of exchange not found messages. But it does not actually solve the problem because reply_* queue is already gone and agent will not receive callbacks. after some debugging, I found under some circumstances seems rabbitmq consumer does not receive basic cancel signal when queue is already gone. This might due to rabbitmq try to restart consumer when queue is down (for example when split brain). In such cases, it might be better to fail early. by reading the code, seems like x-cancel-on-ha-failover is not dedicated to mirror queues only, https://github.com/rabbitmq/rabbitmq-server/blob/master/src/rabbit_channel.erl#L1894, https://github.com/rabbitmq/rabbitmq-server/blob/master/src/rabbit_channel.erl#L1926. By failing early, in my own test setup, I could solve a certain case of exchange not found problem. Change-Id: I2ae53340783e4044dab58035bc0992dc08145b53 Related-bug: #1789177
* 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 Update Sphinx version as well. Remove docs requirements from lower-constraints, they are not needed during install or test but only for docs building. openstackdocstheme renames some variables, so follow the renames before the next release removes them. A couple of variables are also not needed anymore, remove them. Depends-On: https://review.opendev.org/728938 Change-Id: I70c7edf8b95cde890e6263195be1de6bb826e700
* Imported Translations from ZanataOpenStack Proposal Bot2020-04-161-3/+290
| | | | | | | For more information about this automatic import see: https://docs.openstack.org/i18n/latest/reviewing-translation-import.html Change-Id: I792154ba794512046b265718c2f01db624413f30
* 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: I74595d2712ed45ce5b9336e17152f50caab838a0 Sem-Ver: feature
* Remove the deprecated blocking executorHervé Beraud2020-02-181-0/+8
| | | | | | | | | | | | | The blocking executor has been deprecated in Pike and marked for removal in Rocky, but some user like Mistral asked us to wait before. We decided to remove this executor for Train or next cycle, now we are in the Ussuri and after some researchs on usage I think we can go ahead. This patch drop the deprecation warnings, related unit tests and set the server with the threading executor is the default executor. Change-Id: If07bab61ee2b148658b88be98b12f8539f274efe Closes-Bug: #1715141
* reword releasenote for py27 support droppingHervé Beraud2020-02-061-1/+1
| | | | Change-Id: Ic65842371eac32cec3a7b66cb6aa0f3ef52b8637
* [ussuri][goal] Drop python 2.7 support and testing11.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: I15cc79159b603e232e442e202c78d6c56dc73252
* Merge "Add support for kafka SSL autentication"Zuul2020-01-301-0/+9
|\
| * Add support for kafka SSL autenticationMichal Arbet2020-01-161-0/+9
| | | | | | | | Change-Id: Idef066a2e3b4923789a6b081d5442e931aba4507
* | Don't log NoSuchMethod for special non-existing methodsOleg Bondarev2020-01-231-0/+5
|/ | | | | | | | Such non-existing methods are used as health probes. Please see bug for details. Change-Id: I8f6b4a669ec11721f76cf03abcd7d802c3c11eb5 Closes-Bug: #1857319
* Update master for stable/trainOpenStack 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: I99e73a88a654b27cbd9334974413daf9e4a30e5d Sem-Ver: feature
* Bump the openstackdocstheme extension to 1.20pengyuesheng2019-07-191-4/+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: Ib5e22f6a5374f05e576bbc00a209209fdb09acad
* 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: Icb3ca5bb875df1dda9f3d86bb164b6299059664e Sem-Ver: feature
* Bump amqp requirement version to >=2.4.1mb2019-02-181-0/+16
| | | | | | | | | | Bumping the version of amqp in requirements.txt and lower-constraints.txt from 2.4.0 to 2.4.1 to mitigate issues with MessagingTimeouts when using TLS due to a amqp bug that was fixed in 2.4.1 Change-Id: I0b094f32dec24c70f95ccd509164a14a71fcfc7d Closes-Bug: #1800957
* Switch driver to confluent-kafka client libraryAndy Smith2018-12-041-0/+13
| | | | | | | | | | | | | | | | | | | This patch switches the kafka python client from kafka-python to confluent-kafka due to documented threading issues with the kafka-python consumer and the recommendation to use multiplrocessing. The confluent-kafka client leverages the high performance librdkafka C client and is safe for multiple thread use. This patch: * switches to confluent-kafka library * revises consumer and producer message operations * utilizes event.tpool method for confluent-kafka blocking calls * updates unit tests * adds kafka specific timeouts for functional tests * adds release note Depends-On: Ice374dca539b8ed1b1965b75379bad5140121483 Change-Id: Idfb9fe3700d882c8285c6dc56b0620951178eba2
View Lorry Controller Status