List of redis sentinel hosts is now supported in order to
use automatic failover when redis master goes down.
Change-Id: I5fad4c9b6c6aea4f8f382f7469899a7d05c068c1
Closes-Bug: #1518292
New option 'zmq_target_expire' added which defines the
TTL in seconds for each target key.
Consumers should periodically update their target records in
background.
Change-Id: Ic4f2fc46b55e324dd9b6ecb7436a00141a4cd881
Closes-Bug: #1524097
Each config option has limitation for type and value. If we use
method CONF.set_override without parameter enforce_type=True, we
may pass wrong type to config option.
This commit makes sure calling method CONF.set_override with
enforce_type=True.
Change-Id: I1430c93777d6e5d98086a8700663ab9f58c1e5ab
Closes-Bug: #1517839
The usage of assertEqual(True/False, ***) should be changed
to a meaningful format of assertTrue/False(***).
Change-Id: Idda812a34be8aa53654d6791eac47028339d3cb7
Closes-Bug:#1512207
1. Use translation marker functions, their argument must just be a string
2. Any message with more than one variable should use named
interpolation instead of positional to allow translators
to move the variables around in the string to account for
differences in grammar and writing direction.
3. String interpolation should be delayed to be handled by the logging
code, rather than being done at the point of the logging call.
For more details, please refert to oslo.i18n guideline [1]
Note: this commit doesn't touch test code.
[1] http://docs.openstack.org/developer/oslo.i18n/guidelines.html
Change-Id: I5f013d65b20396bbe0e5a2cceaed2a33fad1af23
kombu has already made a conversion from seconds to milliseconds,
so we do not need to do it again.
Closes-Bug: #1531148
Change-Id: Ia4478f15f1980a93a53f7e1e6570f68aeec75c69
The group is still DEFAULT at the moment, but the correct group is
oslo_messaging_notifications. Sample configurations files generated with
the oslo.config tools are invalid due to this incorrect group.
Change-Id: Idc6c52f4b15dfff6e8d6b4a2ef9f5598bb3468cd
Closes-Bug: #1531219
Missing to pass parameter 'timeout' to the method '_ensure_publishing'
when publishing a message.
That will cause RPCClient.call unable to pass timeout to the underlying.
Change-Id: I1abc7e9c6f5204fa336f29a94114c18d8b982fcb
In this change PUB/SUB pattern was used for notifications.
Reduced useless split to direct/fanout notifications.
All notifications are fanout by default.
Change-Id: I232c093af76757dc6fc5e942d47f0473877f9efa
Closes-Bug: #1529845
RPC server uses direct_send method to send replies.
The method sets "passive" flag on an exchange.
Thus auto_declare doesn't bring any good there, but it costs
an additional "exchange.declare" call to RabbitMQ.
simulator.py RPC tests shows that a perfomance gain is ~7%
Change-Id: Ia9f5f9f52c6cb324eca4ca6a63e80d604ddefa23
* Avoid string concatenation during logging, especially
when logging level is disabled.
* Initialize the Randomized strings we will be using
as payloads *before* we start sending the messages
as the string creation takes time and reduces
throughput
Change-Id: I546229fe7ade95572e11bcda95a587228d84bc28
Method import_zmq returns None if can't import zmq module.
For runtime code, an ImportError is raised, and for tests,
a skip message "zmq not available" is sent, so it's unnecessary
to log error which shows up in other projects' unit test logs.
Co-Authored-By: Oleksii Zamiatin <ozamiatin@mirantis.com>
Change-Id: Iebf15042f45da56eb633a0a70822c487dc72c884
Closes-Bug: #1528415
Also small mistakes were fixed,
msg_id, unique_id and reply_q fields were
moved to corresponding AMQP properties
Change-Id: I5147c35c1a2ce0205e08ca81db164a3cc879fb0a
In this change PUB-SUB pipeline was added
and used for CAST-Fanout pattern.
Added 2 new options:
* use_pub_sub - configures the driver to use
PUB/SUB if True, fallbacks to DEALER/ROUTER implementation
otherwise.
PUB/SUB implementation is assumed to be always used with proxy.
* direct_over_proxy - specifies to use proxy with direct patterns
(CALL,CAST). This option is in replace of zmq_use_broker.
Latter is meaningless in context of PUB/SUB architecture,
so renamed.
Change-Id: I7c02d4d62632293941bc0d9d947e5362a5317db6
Closes-Bug: #1515185
When a client is gone (died/restart) and somes replies cannot be sent because
the the exchange of this client will never comeback. We log one message per
reply every 0.25 messages during 60 seconds. When the only useful log
is the one where we decide to drop this replies.
This change moves the less important message to debug level.
Change-Id: I508787c0db4dcec2c0027b89eb4e65c4f98022b9
Related-bug: #1524418
