Log a warning when connected to a routable message bus
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.
commit 827a5176d99479ec9762a7d8dd3571057505f7ec
Author: Andrew Smith <email address hidden>
Date: Tue Jul 26 10:29:13 2016 -0400
[AMQP 1.0] AMQP 1.0 Driver User Guide Document update
This patch includes updates to the user guide document for the
amqp-dispatch-router feature branch. Includes information for deploying
driver to operate with router or broker intermediaries.
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.
Set the default link property to allow message acks
Previously the default snd-settle-mode caused the sender to assume the
message would not be acknowledged so the sender never waited for an
acknowledgement. The 'mixed' setting allows the sender to request
that the receiver acknowledges the message. The term 'mixed' comes
from the AMQP 1.0 standard.
commit ded89418a216bfd28a602eb5713d7665c08e5be1
Author: Andrew Smith <email address hidden>
Date: Fri Jul 1 13:15:35 2016 -0400
[AMQP 1.0] Add configuration parameters for send message deadline
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.
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.
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.
Reviewed: https:/ /review. openstack. org/357376 /git.openstack. org/cgit/ openstack/ oslo.messaging/ commit/ ?id=3ae1cacf105 31d89c0c3c773eb c95fb0b058c1b1
Committed: https:/
Submitter: Jenkins
Branch: master
commit b7717e1616d362c 79d6f366c734482 7f70f127ed
Author: Kenneth Giusti <email address hidden>
Date: Fri Jul 29 12:27:55 2016 -0400
[AMQP 1.0] small fixes to improve timer scalability
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: I83e86bf203e6a6 41085e482c7ccf0 e01f4fb4d86
commit 3109941e5e09d01 e2a75794f8741a1 7a7247cace
Author: Kenneth Giusti <email address hidden>
Date: Thu Aug 4 18:25:50 2016 -0400
Log a warning when connected to a routable message bus
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: I44ba5507d94182 3e2dfa92d52dae4 b85e9bda493
commit 480cd78157cefd5 45b82b863c10fd2 5d98377f5b
Author: Kenneth Giusti <email address hidden>
Date: Mon Aug 1 17:54:33 2016 -0400
[AMQP 1.0] Add link credit configuration options
Change-Id: Ifd483dfc67a4ff 18f2047dbdca0aa b311124627f
Closes-Bug: 1367911
commit 827a5176d99479e c9762a7d8dd3571 057505f7ec
Author: Andrew Smith <email address hidden>
Date: Tue Jul 26 10:29:13 2016 -0400
[AMQP 1.0] AMQP 1.0 Driver User Guide Document update
This patch includes updates to the user guide document for the dispatch- router feature branch. Includes information for deploying
amqp-
driver to operate with router or broker intermediaries.
Change-Id: Icb32743a82bf0f 1e5969a215d880d c736a22f408
Closes-Bug: #1596649
commit 1203ec33b127b8d d7bb3735d7625e0 160e63e2d0
Author: Andrew Smith <email address hidden>
Date: Tue Jul 12 10:13:57 2016 -0400
AMQP 1.0 Driver Architecture Overview Document
Architecture overview document to convey primary capabilities,
functional composition and dynamic behavior of oslo_messaging_amqp driver.
Change-Id: Ic108da7a13d3d8 22a6751a15bae3b 59a3243d366
Closes-Bug: #1596642
commit 5236e991551991a a4dd7572e96f261 dd98a110ad
Author: Kenneth Giusti <email address hidden>
Date: Mon Aug 1 11:19:06 2016 -0400
Remove the max_send_retries option
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: Ic10dd374c865ea f7c7563f379426e 171996184a0
Closes-Bug: #1599518
commit b7a6a0715c7cbc9 01717ceb7f3163f b87d14730f
Author: Andrew Smith <email address hidden>
Date: Tue Jul 26 08:42:33 2016 -0400
[AMQP 1.0] Cancel response treatment for detached link
This patch removes an exception that occurs when an rpc reply is canceled
following the detachment of the link.
Change-Id: Ia743f571b293a7 5d851c0b19549f2 6673d9a734c
Closes-Bug: #1606557
commit 3f38e6b03a3ebcb 9b9faf23ac6b289 093527e812
Author: Kenneth Giusti <email address hidden>
Date: Mon Jul 25 09:01:44 2016 -0400
Set the default link property to allow message acks
Previously the default snd-settle-mode caused the sender to assume the ment. The 'mixed' setting allows the sender to request
message would not be acknowledged so the sender never waited for an
acknowledge
that the receiver acknowledges the message. The term 'mixed' comes
from the AMQP 1.0 standard.
Change-Id: Ida4e04f0827fff 902d692f13ec972 b099703adf0
commit 7fe799d2e03e5aa 0916198935b0e96 d35c12df15
Author: Kenneth Giusti <email address hidden>
Date: Fri Jul 22 14:48:06 2016 -0400
Fix a timer leak in the AMQP 1.0 driver
Change-Id: Ib89ac2f9e866ba b7a62fbdd2b1e8c ddce030e944
commit ded89418a216bfd 28a602eb5713d76 65c08e5be1
Author: Andrew Smith <email address hidden>
Date: Fri Jul 1 13:15:35 2016 -0400
[AMQP 1.0] Add configuration parameters for send message deadline
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: I398a4686abf3df 6e5c802d94d6bda 7ba9995833d da9b2e41ab2a83a b59f15e396e
Depends-On: I6b60b6944a4c44
Closes-Bug: #1596641
commit 4c0674d194f2229 692fbbb0086fe38 75b17ab7bc
Author: Kenneth Giusti <email address hidden>
Date: Wed Jun 15 10:10:30 2016 -0400
Re-factor the AMQP 1.0 addressing semantics
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 subscription address based on the addressing mode. This hides
Addresser class. This class is used to map an oslo.messaging Target
address and notification flag into a corresponding AMQP 1.0
message/
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: I6b60b6944a4c44 da9b2e41ab2a83a b59f15e396e
commit 35ea442a0e350ac 88a5583fe12c75b 5000fb2871
Author: Andrew Smith <email address hidden>
Date: Fri Jun 17 12:38:11 2016 -0400
[AMQP 1.0] Add acknowledge and requeue handling for incoming message
This patch schedules a controller task to handle the acknowledge or
requeue disposition of the incoming message
Change-Id: I9a53959ce20541 7481f6442f712a8 f238394bdae e81a2815fe17dbe 8428d3df619
Depends-On: Icf4dfbb0be1336
Closes-Bug: #1593759
commit b1b4cfce8ce0fed ee3c42febd58c18 4d6d9f2553
Author: Kenneth Giusti <email address hidden>
Date: Fri May 27 16:37:34 2016 -0400
Refactor AMQP 1.0 command task to support timers
Refactors the Task() classes to support per-send timers and
consolidate message sending logic.
Change-Id: Icf4dfbb0be1336 e81a2815fe17dbe 8428d3df619
commit 890ce0e5436f3fb 3474806ba71b4f7 4e725476cc
Author: Kenneth Giusti <email address hidden>
Date: Wed Mar 16 11:48:24 2016 -0400
Refactor link management to support link recovery
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: I14606de55e2e94 d03d865fefe8c8c 2327207ba5c
Closes-Bug: #1434540
commit 23f92124837b498 383bb497464deba 2327686703
Author: Kenneth Giusti <email address hidden>
Date: Wed May 18 13:55:53 2016 -0400
Add the proper branch back to .gitreview
Change-Id: I6db00a83c7c843 a4f1ede6d5352c6 5053fc7736d