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.
Change-Id: I9ddb6595fc52e46ed8844e39d2fa71029c90b65c
Closes-Bug: #1674567
The call monitoring feature was introduced in commit
b34ab8b1cc9f4d513a2927c102dbbe82031d9c2a for RabbitMQ. This patch
enables the feature on the AMQP 1.0 driver - currently the only other
driver that supports RPC.
Change-Id: Ic787696852690b59779fb4716aec1e78c48bbe6a
This adds an optional call_monitor_timeout parameter to the RPC client,
which if specified, will enable heartbeating of long-running calls by
the server. This enables the user to increase the regular timeout to
a much larger value, allowing calls to take a very long time, but
with heartbeating to indicate that they are still running on the server
side. If the server stops heartbeating, then the call_monitor_timeout
takes over and we fail with the usual MessagingTimeout instead of waiting
for the longer overall timeout to expire.
Change-Id: I60334aaf019f177a984583528b71d00859d31f84
This adds a heartbeat() method to RpcIncomingMessage to be used by a
subsequent patch implementation of active-call heartbeating. This is
unimplemented in all drivers for the moment.
Change-Id: If8ab0dc16e3bef69d5a826c31c0fe35e403ac6a1
Adds the 'pseudo_vhost' option which when enabled will incorporate the
virtual host into the address semantics. This creates a 'subnet' like
address space for each virtual host. Use this when the messaging bus
does not provide virtual hosting support. It is enabled by default as
to date none of the supported AMQP 1.0 message buses natively support
virtual hosting.
It also updates SSL support: SSL can either use the connection
hostname or the vhost name when validating a server's
certificate. This is controlled by the 'ssl_verify_vhost' option.
This option is disabled by default as it requires both vhost and SNI
support from the server. By default SSL will use the DNS name from
the TransportURL.
Change-Id: I49bb99d1b19e8e7e6fded76198da92ca5f7d65ab
Closes-Bug: #1700835
Partial-Bug: #1706987
The pre-settled configuration option was being ignored in the case of
RPC call transfers.
Change-Id: I35989c8a653bac0d9a7c3e33a8af2027574f4bd9
Closes-Bug: 1680905
When driver load we allow to override option unrelated to the driver and
to set option useless for the driver.
This change validates the query string when the driver load to report as
soon as possible invalid options. And allow to override only option
of the driver option group (ie: [oslo_messaging_<driver_name>].
Related-bug: #1666903
Change-Id: Iaf23f773279c10bf37d545883ada7c2f6a9ffbbf
ConfigOptsProxy have been implemented only pika driver while
the oslo.messaging allow to pass the query string for all drivers.
This change fixes that.
Closes-Bug: #1666903
Closes-Bug: #1607889
Next step is to validate the query with ConfigOptsProxy, to
raise appropriate exception in case of mis-configuration.
Change-Id: I573334e774ccf33ecd27a85067045f3c6489ee89
A message ack status of 'RELEASED' or 'MODIFIED' indicates that the
message was not accepted by the destination due to some temporary
issue. These status are used to indicate to the sender that the
message can be safely re-transmitted without risk of duplication
(i.e. the delivery is not 'in-doubt'). For example this may happen
during a message bus topology update if a message is sent before the
topology stabilizes.
This change implements re-send for these cases.
Closes-Bug: #1646586
Change-Id: I419e23b59e3eb90fda3f1c0e7ddf54ef98870e4b
Avoid blocking the RPC Server thread when it attempts to acknowledge
the RPC request message. Blocking is unnecessary as the acknowledge
command does not return a status and can be processed asynchronously
from the server thread.
Avoiding this context switch improves overall RPC call throughput
according to the simulator tool by approximately ten percent on my
test systems.
Change-Id: I71548eb6f9f7dcaf74cb426d4e9b369b54856419
Decrease the size of the debug log output drastically by removing
debug messages issued for each message. This patch only removes those
log statements that log correct behavior - errant behavior is still
logged for debug.
Change-Id: I1c67e6ed7e503ef3b9543fdfce31b91c46bd851a
This patch allows the ack processing behavior to be configured based
on the type of message sent. This allows the proper ack behavior for
a given backend to be customized. By default Cast messages are now
sent pre-acked (best effort).
Change-Id: I0d4e44a7a87f3c917a3eb44f6e02af74a9af10a5
Closes-Bug: #1616612
This patch introduces the following tweaks to the timer
implementation:
Reduce the number of timers that need to be tracked by reducing the
timer granularity to units of seconds.
Decrease the default timeout values to further reduce the total number
of tracked timers.
Batch multiple expiring events that share the same deadline.
Inline the timer comparison code in the main event loop.
Avoid using an expensive comparison method in the heap sort by using
an integer primitive instead.
Use monotonic time instead of time.time()
Change-Id: I83e86bf203e6a641085e482c7ccf0e01f4fb4d86
Newton will be the first release of support for this new message bus
technology. Make users aware that this feature is 'bleeding edge' and
queuing is not supported in this release.
Change-Id: I44ba5507d941823e2dfa92d52dae4b85e9bda493
This option was added for feature parity with the rabbitmq driver.
Since then the option was removed from rabbitmq. Since this option
was never released we can simply remove it rather than deprecating it.
Change-Id: Ic10dd374c865eaf7c7563f379426e171996184a0
Closes-Bug: #1599518
This patch add driver configuration option parameters for oslo_messaging_amqp
reply, send and notification timeout. These timeouts are used when the caller
does not provide a timeout expiry.
Change-Id: I398a4686abf3df6e5c802d94d6bda7ba9995833d
Depends-On: I6b60b6944a4c44da9b2e41ab2a83ab59f15e396e
Closes-Bug: #1596641
This patch introduces a new routable addressing format. This new
address format not only works with traditional broker-based messaging
backends but can be used to optimally route messages across a mesh
messaging topology. This new addressing format may be enabled either
via configuration or by message bus identification.
This patch moves all of the AMQP 1.0 addressing logic into a new
Addresser class. This class is used to map an oslo.messaging Target
address and notification flag into a corresponding AMQP 1.0
message/subscription address based on the addressing mode. This hides
the addressing details from the rest of the driver.
For backward compatibility with previous releases the Addresser can be
configured to automatically detect a non-routable messaging back end
and fall back to using the legacy addressing scheme.
The intention is to use routable addressing as the only form of
addressing supported by the driver regardless of messaging back end.
However before that can happen the legacy addressing must follow the
standard deprecation process. Until then legacy addressing will
remain available for backwards compatibility.
Change-Id: I6b60b6944a4c44da9b2e41ab2a83ab59f15e396e
This patch schedules a controller task to handle the acknowledge or
requeue disposition of the incoming message
Change-Id: I9a53959ce205417481f6442f712a8f238394bdae
Depends-On: Icf4dfbb0be1336e81a2815fe17dbe8428d3df619
Closes-Bug: #1593759
This refactors the driver to process send/subscribe requests as they
arrive from the application rather than blocking these requests until
the reply link is activated. This allows recoverable failures
occurring at the connection or link level to be applied to the sender
retry count. This patch also implements link re-connect for
subscriptions.
These changes are required to support a brokerless routed mesh
backend.
Change-Id: I14606de55e2e94d03d865fefe8c8c2327207ba5c
Closes-Bug: #1434540
This patch removes log_failure argument from the function
serialize_remote_exception and from driver implementations
using it (because it is never used and always defaults to True)
and prevents error logging in this function (because these errors
are already logged by servers while processing incoming messages).
Change-Id: Ic01bb11d6c4f018a17f3219cdbd07ef4d30fa434
Closes-Bug: 1580352
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