summaryrefslogtreecommitdiff
path: root/setup.cfg
Commit message (Collapse)AuthorAgeFilesLines
* Drop python3.6/3.7 support in testing runtimeHervé Beraud2022-05-051-3/+1
| | | | | | | | | | In Zed cycle testing runtime, we are targetting to drop the python 3.6/3.7 support, project started adding python 3.8 as minimum, example nova: - https://github.com/openstack/nova/blob/56b5aed08c6a3ed81b78dc216f0165ebfe3c3350/setup.cfg#L13 Change-Id: Id23d3845db716d26175d71280dbedf93736d19de
* Update python testing classifierdengzhaosen2021-12-211-0/+1
| | | | | | | | | | | | | | Yoga testing runtime[1] has been updated to add py39 testing as voting. Unit tests update are handled by the job template change in openstack-zuul-job - https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/820286 this commit updates the classifier in setup.cfg file. [1] https://governance.openstack.org/tc/reference/runtimes/yoga.html Change-Id: I26743858a0ca7a6e46bda821c8f29b6dff34ea15
* setup.cfg: Replace dashes with underscoresyangyawei2021-05-131-4/+4
| | | | | | | | | | | | | | | | Setuptools v54.1.0 introduces a warning that the use of dash-separated options in 'setup.cfg' will not be supported in a future version [1]. Get ahead of the issue by replacing the dashes with underscores. Without this, we see 'UserWarning' messages like the following on new enough versions of setuptools: UserWarning: Usage of dash-separated 'description-file' will not be supported in future versions. Please use the underscore name 'description_file' instead [1] https://github.com/pypa/setuptools/commit/a2e9ae4cb Change-Id: I6e015bf3955e3ff7aa21bc86d3f6f69e0017ca29
* [goal] Migrate testing to ubuntu focalGhanshyam Mann2020-09-101-1/+1
| | | | | | | | | | | | | | | | | | | As per victoria cycle testing runtime and community goal[1] we need to migrate upstream CI/CD to Ubuntu Focal(20.04). Fixing: - bug#1886298 Bump the lower constraints for required deps which added python3.8 support in their later version. Story: #2007865 Task: #40207 Closes-Bug: #1886298 [1] https://governance.openstack.org/tc/goals/selected/victoria/migrate-ci-cd-jobs-to-ubuntu-focal.h> Change-Id: Id6b499239fa8b6480c5f67d460215ab458677c6d
* Add py38 package metadataSean McGinnis2020-04-241-0/+1
| | | | | | | | | Now that we are running the Victoria tests that include a voting py38, we can now add the Python 3.8 metadata to the package information to reflect that support. Change-Id: Ibe733cb482501544644133fed494f672ef566b7a Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
* Remove the deprecated blocking executorHervé Beraud2020-02-181-1/+0
| | | | | | | | | | | | | 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
* [ussuri][goal] Drop python 2.7 support and testing11.0.0Hervé Beraud2020-02-031-5/+3
| | | | | | | | | | | | | | 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
* Add Python 3 Train unit testsCorey Bryant2019-07-051-0/+1
| | | | | | | | | | | | This is a mechanically generated patch to ensure unit testing is in place for all of the Tested Runtimes for Train. See the Train python3-updates goal document for details: https://governance.openstack.org/tc/goals/train/python3-updates.html Change-Id: I699a3ee210c4b45018566b520eaf641e0e582362 Story: #2005924 Task: #34234
* Dropping the py35 testingGhanshyam Mann2019-04-151-1/+1
| | | | | | | | | | | | | | | | | All the integration testing has been moved to Bionic now[1] and py3.5 is not tested runtime for Train or stable/stein[2]. As per below ML thread, we are good to drop the py35 testing now: http://lists.openstack.org/pipermail/openstack-discuss/2019-April/005097.html [1] http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004647.html [2] https://governance.openstack.org/tc/reference/runtimes/stein.html https://governance.openstack.org/tc/reference/runtimes/train.html Change-Id: I1874f96f78cb403e6f3a56a49cb83df40d531f8d
* Merge "Switch driver to confluent-kafka client library"9.3.0Zuul2018-12-071-2/+1
|\
| * Switch driver to confluent-kafka client libraryAndy Smith2018-12-041-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | 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: I7d889d3f9a6c95e707ed57dbf5a9cffb1d41ddf5
* always build universal wheelsHervé Beraud2018-10-041-1/+1
| | | | | | All of our projects are pure python, so we can build universal wheels by default. Change-Id: I3369303d278af6154cdcf06b727e8ff941dc410a
* Remove the deprecated ZeroMQ driverAndy Smith2018-08-281-13/+0
| | | | | | | | Users of the oslo.messaging RPC communications service must use the rabbit ("rabbit://...") or AMQP 1.0 ("amqp://...") drivers. Change-Id: If3474142f1fe99d41d7b4466061ed0e23ca38549 Closes-Bug: 1789259
* Move requirements for the optional drivers (amqp1, kafka)Kenneth Giusti2018-04-161-0/+14
| | | | | | | | | | | Move the requirements for the optional drivers to test-requirements.txt and setup.cfg. The default rabbitmq driver's dependencies should be the only hard requirements for the base package. Leaving ZeroMQ deps unchanged for now as it will be removed in Stein Change-Id: I19dd699ccf87e43202ccefb99258fbaa9ea17b7e
* Remove the deprecated Pika driver6.0.0Kenneth Giusti2018-03-211-16/+0
| | | | | | | | | | | It is recommended that all users of the Pika driver transition to using the Rabbit driver instead. Typically this is done by changing the prefix of the transport_url configuration option from "pika://..." to "rabbit://...". There are no changes required to the RabbitMQ server configuration. Change-Id: I52ea5ccb7e7c247abd95e2d8d50dac4c4ad11246 Closes-Bug: #1744741
* Follow the new PTI for document buildSean McGinnis2018-01-081-9/+0
| | | | | | | | | | | | 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: I39b9806013a0912b27c0523dfc2b713b3105bdf1
* Update URLs in documents according to document migrationChangBo Guo(gcb)2017-07-121-1/+1
| | | | Change-Id: I139d4d38e49590d50e51495b6e3b84836975c6ed
* Build universal wheelsJeremy Stanley2017-06-071-0/+3
| | | | | | | | The trove metadata for this package claims to support both Python 2.x and Py3K; build universal wheels so Python 3.x interpreters can consume them too. Change-Id: I0b88fcaa2ea36e1d7478d76b86c6c1f1e68c8616
* Use Sphinx 1.5 warning-is-errorStephen Finucane2017-03-161-4/+2
| | | | | | | | | | | | | With pbr 2.0 and Sphinx 1.5, the setting for treat sphinx warnings as errors is setting warning-is-error in build_sphinx section. Migrate the setting from the old warnerrors one. The history document is removed because some of the commit messages used in ChangeLog were being identified as invalid markup and there doesn't appear to be anyway to edit there retroactively nor disable warnings on a specific file. Change-Id: I79e7ac56d5af1151865686761f3d40a11efbf472
* Remove references to Python 3.4Eric Brown2017-01-131-1/+0
| | | | | | | 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: I2a00ead626d9eced96487ee82b5d7857126d8355
* Fix typos in addressing.py and setup.cfgHu Yupeng2016-10-171-1/+1
| | | | | | TrivialFix Change-Id: I403ede0d11357c76da2432fd14a6b843969c1c17
* [zmq] Maintain several redis hostsGevorg Davoian2016-10-101-0/+1
| | | | | | | This patch makes it possible to maintain several redis hosts at once in order to increase driver's reliability and fault tolerance. Change-Id: Id6f63a4bb67a39340a74d16144c79028c7af245d
* modify the home-page info with the developer documentationavnish2016-09-201-1/+1
| | | | Change-Id: I9b049fe3e0dc68302d0f50cf9c4098a2cfccdac6
* [zmq] Redis unavailability is not criticalOleksii Zamiatin2016-08-161-2/+2
| | | | | | | | | Each time driver couldn't update from Redis warning message is being logged and work continues with cached targets state and on existing connections. Change-Id: I459532f1f60fab1d4c9926e02cdc3c3c6a162047 Closes-Bug: #1610958
* notify: add a CLI tool to manually send notificationsJulien Danjou2016-07-131-0/+1
| | | | Change-Id: I01ebd8402e322c5c27dc2fc4c61fb5beb2dddae8
* Add Python 3.5 classifier and venvChangBo Guo(gcb)2016-07-121-0/+1
| | | | | | | | Now that there is a passing gate job, we can claim support for Python 3.5 in the classifier. This patch also adds the convenience py35 venv. Change-Id: I8871f4e17ab806c00661d0c960a216d0a3fc5449
* Reorganize the AMQP 1.0 driver source filesKenneth Giusti2016-05-131-1/+1
| | | | | | | | | | This patch simply moves the existing AMQP 1.0 driver files into a directory layout that is consistent with the other drivers. The driver unit tests are also moved to the proper test directory. There are no changes in driver functionality or API. Change-Id: I83a5d5433be8c3b317597100af69192ec5be81f1 Closes-Bug: #1579823
* Implements configurable connection factoryDmitriy Ukhlov2016-05-121-0/+15
| | | | | | | | | new - create new connection each times single - use single connection for whole transport read_write - use two connections for whole transport (one for listening and one for sending) Change-Id: I464c83beb498453b6df2237e7b8022d47ca3fa14
* Remove Beta development status from classifiersRonald Bradford2016-05-021-1/+0
| | | | | | | | | | Remove the Beta trove classifier to be in line with other Oslo projects. While there is a Production/Stable status none of the other Oslo projects use it. https://pypi.python.org/pypi?%3Aaction=list_classifiers Change-Id: I3689c6faf60be49ce2bf19f45e977dd64798954b
* [zmq] Reduce number of connectionsOleksii Zamiatin2016-03-311-1/+2
| | | | | | | | | | | | | | | | | | | In this change 'use_router_proxy' option was added to switch between direct connections and proxy. Proxy was reimplemented and splitted onto two types of proxies: * PUBLISHER proxy for fanout pattern * ROUTER proxy for direct messaging Each type of proxy is configured over command line argument --type. Deployment guide was updated accordingly to the change. Change-Id: If36e9c26e2a8ebe622cfa7e9f2a07b1a69aabe34 Closes-Bug: #1555007
* Claim python3 compatability for Newton onwardsDavanum Srinivas2016-03-241-0/+3
| | | | | | | | | | | | | | | | | | | | The following oslo.messaging changes make sure python3 works: Id630cb32dc5fe29774ae9e0d2766535906f605bf I5cd7475618f7a7532db770c2c5c61576a657fbb4 I1f8bb964aef23867a651e192dc355635e36f78a1 This one adds a functional test for py34: Ibc695762fb12b60a8094be187001dd2bd42f402e Which is enabled in the gate: Ifdbd4ab1eae6c5e5364a99906995dff3bb1ff4f0 The following re-enables voting for py34 unit tests: Ibbcd20d297fdf90ce846f0162329b9410cd6f482 With all the above, we are ready to claim python3 support Change-Id: Ie89f96cee0eadcad5f84dd0423645b894eec9116
* Move server's logic from executorsdukhlov2016-02-231-3/+3
| | | | | | | | | | | | | | | | | | | | Now we have situation when openstack projects like Mistral needs extra oslo.messaging functionality. But it is too complicated now to to implement something new and integrate it with current code because there is a little bit mess. 1) Executor should be responsible for how to run jobs (but now also has code with server logic) 2) Dispatcher should be responsible for routing message to the target endpoint for processing (but it also has serialisation, sending replies, executing some executor's callbacks etc) 3) Server should do all server specific logic, we need to have different implementation of servers for RPC and notification, not different implementations of dispatchers This patch fixes 1-st point Change-Id: Ib6408f408889bb7b7056722be636a5547b1a780d
* Remove aioeventlet executorVictor Stinner2016-02-171-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | I wrote the aioeventlet executor as a first step to replace eventlet with trollius in OpenStack. Sadly, the project of replacing eventlet with something else (trollius, threads or whatever) looks to be stuck because of various reasons. See the spec: "Replace eventlet + monkey-patching with ??" https://review.openstack.org/#/c/164035/ Recently, I deprecated the trollius project in favor of asyncio: http://trollius.readthedocs.org/deprecated.html Since I abandonned my project to replace eventlet with trollius, I now propose to remove the unused aioeventlet executor from Oslo Messaging to simplify the code and remove unused dependencies (especially trollius). Since the aioeventlet executor is not used by any application, it's safe to remove it. Removing the executor removes trollius and aioeventlet dependencies. ... The executor may come back "later" when the first OpenStack service will start to drop Python 2 support. For more information on asyncio in OpenStack, see: http://aioeventlet.readthedocs.org/openstack.html Note: the executor was added by the change I7a78ed998719a703077232726f66d882463b1297. Change-Id: I10d8d7d4134b32e4fc0badfa15e9ffb005910139
* Update translation setupAndreas Jaeger2016-01-291-6/+6
| | | | | | | | | | | | | | | Follow new infra setup for translations, see spec http://specs.openstack.org/openstack-infra/infra-specs/specs/translation_setup.html for full details. This basically renames oslo.messaging/locale/oslo.messaging.pot to oslo_messaging/locale/oslo_messaging.pot. For this we need to update setup.cfg. Update also domain name in i18n.py. Change-Id: Idf5300224f572d29953261ac998e7bf32a12822d
* Merge remote-tracking branch 'origin/master' into merge-branchDavanum Srinivas2015-12-141-1/+3
|\ | | | | | | Change-Id: Ice6dcc3867dff6b7fea5647a3b79d1c765bf9d73
| * Add a driver for Apache KafkaKomei Shimamura2015-12-011-0/+3
| | | | | | | | | | | | | | | | | | Adding a driver for Apache Kafka connection, supporting notification via Kafka. This driver is experimental until having functional and integration tests Change-Id: I7a5d8e3259b21d5e29ed3b795d04952e1d13ad08 Implements: blueprint adding-kafka-support
| * Remove qpidd's driver from the treeFlavio Percoco2015-11-201-1/+0
| | | | | | | | | | | | | | | | | | | | Back in liberty we marked this driver as deprecated. This patch removes it from the tree. The patch also removes tests, options and other references in the documentation. Note that one script is being kept because it's required by the amqp driver. Depends-On: If4b1773334e424d1f4a4e112bd1f10aca62682a9 Change-Id: I4a9cba314c4a2f24307504fa7b5427424268b114
* | Adds comment for pika_pooler.pyDmitriy Ukhlov2015-12-091-1/+1
| | | | | | | | | | | | | | | | Also this patch: 1) fixed import's order 2) removes PikaDriverCompatibleWithOldRabbit (tests, show that after retry implementation all works fine) Change-Id: Ib34f6db569cadb5c27d8865f13ba32ef9a6c73e9
* | Implements rabbit-pika driverDmitriy Ukhlov2015-10-201-0/+1
|/ | | | | | | | | | In this patch new driver implementation added and registered in setup.cfg, integrated ith tox functional tests. Implements: bp rabbit-pika Depends-On: I7bda78820e657b1e97bf888d4065a917eb317cfb Change-Id: I40842a03ce73d171644c362e3abfca2990aca58a
* Merge "Non-blocking outgoing queue was implemented"Jenkins2015-09-301-1/+1
|\
| * Non-blocking outgoing queue was implementedOleksii Zamiatin2015-09-281-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The main issue with eventlet.green.zmq is that libzmq as a C-library is completely monkey-patch unfriendly. So any blocking call inside the native library makes calling process stuck. We can't avoid this actually in an absolutely normal situation when a client appears earlier than listener we have all client process get stuck until listener raised. If the listener for example is also blocked awaiting for some other service to appear we have a chain of locks which may occasionally result in a dead-lock. The other situation with Notifier is quite similar. For that reason zmq-broker was restored, but now it serves as an outgoing queue on a client side. Servers remained the same dynamically port-binded. Now all clients can still use green-zmq, but presence of the broker-queue on a host guarantees that green threads will never blocked in a client because all messages will wait their listeners inside the broker queue. The broker process's modules are not monkey-patched, they make use of native threading and native zmq. Possibility to run without broker also remains. The option zmq_use_broker introduced for that reason. Closes-Bug: #1497315 Change-Id: I786b100fd6ee1cf4b99139db0ca044d358d36345
* | Merge "Fix the home-page value with Oslo wikipage"Jenkins2015-09-251-1/+1
|\ \
| * | Fix the home-page value with Oslo wikipagevenkatamahesh2015-09-251-1/+1
| | | | | | | | | | | | Change-Id: I4b72377329e055096d8636f4734c9272ca8ec3a8
* | | Allow custom notification driversDavanum Srinivas2015-09-251-2/+2
| |/ |/| | | | | | | | | | | | | | | Our class hierarchy hides classes and modules that so its hard for folks to write a custom Notification driver. We should make these public and document them Closes-Bug: #1426046 Change-Id: Ifb96c2ae9868426cac2700bf4917c27c02c90b15
* | Merge remote-tracking branch 'origin/feature/zmq' into merge-branchDavanum Srinivas2015-09-151-3/+2
|\ \ | |/ |/| | | Change-Id: If189d03131efc02045955508cef06fdd2ed590ee
| * Remove oslo namespace packageDoug Hellmann2015-07-291-4/+0
| | | | | | | | | | | | | | | | Blueprint remove-namespace-packages Cherry-picked from: 03265410e0294e176d18dd42b57268a8056eb8fc Change-Id: Ibaba19ef10b4902c4f4f9fbdf7078e66b75f2035
| * ZMQ: Initial matchmaker implementationVictor Sergeyev2015-07-161-3/+2
| | | | | | | | | | | | | | | | | | This patch replaces the old outdated matchmakers and replace it into the new ones. Call/Cast test_specific_server() functional tests passes now. Change-Id: I8635396110d30d26812f39b242fbbabd1a0feaaa
* | Remove oslo namespace packageDoug Hellmann2015-07-161-4/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Blueprint remove-namespace-packages Depends-on: I2eeef93ee2e61a721c69f62add819f93f62f077d for openstack/ceilometer Depends-on: I26390dd908769be5f1a5b70be22d3b98e3a45563 for openstack/ceilometermiddleware Depends-on: Ifa8baab33cdb3e606cf175a8c29c3a4ef6c44480 for openstack/glance Depends-on: I029c3260051aa48cfaae428c096c1ac7b43b2bd2 for openstack/ceilometermiddleware Change-Id: I8c5595bbafa82db33f62fa47d214f5cb756a2639
* | Remove 2.6 classifierJoshua Harlow2015-07-061-1/+0
|/ | | | | | | | | | | This removes the 2.6 classifier so that support for 2.6 is not noted (when building packages, on pypi...) as happening anymore for oslo.messaging (since check/gating support for it has been turned off). Depends-On: I4013bf38a197c9a9d82b3956ddbd25450d913df9 Change-Id: Ic4150332fff0724e5178e14f91ac54d5a80d408b