messaging notification configuration is missing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack-Ansible |
Fix Released
|
Undecided
|
weizj |
Bug Description
messaging notification configuration is missing
Changed in openstack-ansible: | |
assignee: | nobody → weizj (wei.zhijun) |
status: | New → In Progress |
OpenStack Infra (hudson-openstack) wrote : Fix proposed to openstack-ansible-os_tacker (master) | #1 |
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-ansible-os_tacker (master) | #2 |
Reviewed: https:/
Committed: https:/
Submitter: Zuul
Branch: master
commit 88a678bbadd79e5
Author: ZhijunWei <email address hidden>
Date: Wed Sep 19 08:42:03 2018 -0400
Remove the unnecessary verbose defined
Change-Id: Ie188de9270e666
Closes-Bug: #1794320
Changed in openstack-ansible: | |
status: | In Progress → Fix Released |
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-ansible-os_magnum (master) | #3 |
Reviewed: https:/
Committed: https:/
Submitter: Zuul
Branch: master
commit 9508e525eda4eb8
Author: ZhijunWei <email address hidden>
Date: Wed Sep 19 08:20:41 2018 -0400
Update messaging notification configuration
This patch add the conditional inclusion of the notification
section of the service configuration. This ensures that oslo.messaging
notifications use the correct transport for deployments that have
separate rpc and notify messaging backends. For example, if the
transport_url is not provided in the notification section of the
service configuration, the transport_url specified in the default
section will be used instead.
This patch conditionally selects the notifier driver. The noop
driver will be selected when notification publishing is disabled.
The messagingv2 driver is selected when notification publishing is
enabled.
Change-Id: Iaadc0d852c003e
Closes-Bug: #1794320
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-ansible-os_blazar (master) | #4 |
Reviewed: https:/
Committed: https:/
Submitter: Zuul
Branch: master
commit 6703cf06dd5a7d9
Author: ZhijunWei <email address hidden>
Date: Wed Sep 19 08:20:48 2018 -0400
Update messaging notification configuration
This patch add the conditional inclusion of the notification
section of the service configuration. This ensures that oslo.messaging
notifications use the correct transport for deployments that have
separate rpc and notify messaging backends. For example, if the
transport_url is not provided in the notification section of the
service configuration, the transport_url specified in the default
section will be used instead.
This patch conditionally selects the notifier driver. The noop
driver will be selected when notification publishing is disabled.
The messagingv2 driver is selected when notification publishing is
enabled.
Change-Id: I2b4c4a119fa300
Closes-Bug: #1794320
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-ansible-os_trove (master) | #5 |
Reviewed: https:/
Committed: https:/
Submitter: Zuul
Branch: master
commit 3bbc52b399d0aaf
Author: ZhijunWei <email address hidden>
Date: Wed Sep 19 08:20:41 2018 -0400
Update messaging notification configuration
This patch add the conditional inclusion of the notification
section of the service configuration. This ensures that oslo.messaging
notifications use the correct transport for deployments that have
separate rpc and notify messaging backends. For example, if the
transport_url is not provided in the notification section of the
service configuration, the transport_url specified in the default
section will be used instead.
This patch conditionally selects the notifier driver. The noop
driver will be selected when notification publishing is disabled.
The messagingv2 driver is selected when notification publishing is
enabled.
Change-Id: Ie967b281e15127
Closes-Bug: #1794320
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-ansible-os_tacker (master) | #6 |
Reviewed: https:/
Committed: https:/
Submitter: Zuul
Branch: master
commit 56dc20030b9c391
Author: ZhijunWei <email address hidden>
Date: Wed Sep 19 08:20:41 2018 -0400
Update messaging notification configuration
This patch add the conditional inclusion of the notification
section of the service configuration. This ensures that oslo.messaging
notifications use the correct transport for deployments that have
separate rpc and notify messaging backends. For example, if the
transport_url is not provided in the notification section of the
service configuration, the transport_url specified in the default
section will be used instead.
This patch conditionally selects the notifier driver. The noop
driver will be selected when notification publishing is disabled.
The messagingv2 driver is selected when notification publishing is
enabled.
Change-Id: I60e92e14c0893b
Closes-Bug: #1794320
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-ansible-os_sahara (master) | #7 |
Reviewed: https:/
Committed: https:/
Submitter: Zuul
Branch: master
commit 7f595f01b10a59d
Author: ZhijunWei <email address hidden>
Date: Wed Sep 19 08:20:41 2018 -0400
Update messaging notification configuration
This patch removes the conditional inclusion of the notification
section of the service configuration. This ensures that oslo.messaging
notifications use the correct transport for deployments that have
separate rpc and notify messaging backends. For example, if the
transport_url is not provided in the notification section of the
service configuration, the transport_url specified in the default
section will be used instead.
This patch conditionally selects the notifier driver. The noop
driver will be selected when notification publishing is disabled.
The messagingv2 driver is selected when notification publishing is
enabled.
Change-Id: Ib68aa2669b5d70
Closes-Bug: #1794320
OpenStack Infra (hudson-openstack) wrote : Fix proposed to openstack-ansible-os_tacker (stable/rocky) | #8 |
Fix proposed to branch: stable/rocky
Review: https:/
OpenStack Infra (hudson-openstack) wrote : Fix proposed to openstack-ansible-os_sahara (stable/rocky) | #9 |
Fix proposed to branch: stable/rocky
Review: https:/
OpenStack Infra (hudson-openstack) wrote : Fix proposed to openstack-ansible-os_magnum (stable/rocky) | #10 |
Fix proposed to branch: stable/rocky
Review: https:/
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-ansible-os_designate (master) | #11 |
Reviewed: https:/
Committed: https:/
Submitter: Zuul
Branch: master
commit 3cdd0d103afef8b
Author: ZhijunWei <email address hidden>
Date: Wed Sep 19 08:20:41 2018 -0400
Update messaging notification configuration
This patch add the conditional inclusion of the notification
section of the service configuration. This ensures that oslo.messaging
notifications use the correct transport for deployments that have
separate rpc and notify messaging backends. For example, if the
transport_url is not provided in the notification section of the
service configuration, the transport_url specified in the default
section will be used instead.
This patch conditionally selects the notifier driver. The noop
driver will be selected when notification publishing is disabled.
The messagingv2 driver is selected when notification publishing is
enabled.
Change-Id: Ie5cc5499980f98
Closes-Bug: #1794320
OpenStack Infra (hudson-openstack) wrote : Change abandoned on openstack-ansible-os_sahara (stable/rocky) | #12 |
Change abandoned by weizj (<email address hidden>) on branch: stable/rocky
Review: https:/
OpenStack Infra (hudson-openstack) wrote : Change abandoned on openstack-ansible-os_tacker (stable/rocky) | #13 |
Change abandoned by weizj (<email address hidden>) on branch: stable/rocky
Review: https:/
OpenStack Infra (hudson-openstack) wrote : Change abandoned on openstack-ansible-os_magnum (stable/rocky) | #14 |
Change abandoned by weizj (<email address hidden>) on branch: stable/rocky
Review: https:/
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_designate stein-eol | #15 |
This issue was fixed in the openstack/
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_magnum stein-eol | #16 |
This issue was fixed in the openstack/
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_sahara stein-eol | #17 |
This issue was fixed in the openstack/
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_tacker stein-eol | #18 |
This issue was fixed in the openstack/
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_trove stein-eol | #20 |
This issue was fixed in the openstack/
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_designate train-eol | #21 |
This issue was fixed in the openstack/
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_magnum train-eol | #22 |
This issue was fixed in the openstack/
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_sahara train-eol | #23 |
This issue was fixed in the openstack/
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_tacker train-eol | #24 |
This issue was fixed in the openstack/
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_trove train-eol | #26 |
This issue was fixed in the openstack/
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_designate ussuri-eol | #27 |
This issue was fixed in the openstack/
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_magnum ussuri-eol | #28 |
This issue was fixed in the openstack/
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_sahara ussuri-eol | #29 |
This issue was fixed in the openstack/
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_tacker ussuri-eol | #30 |
This issue was fixed in the openstack/
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_trove ussuri-eol | #32 |
This issue was fixed in the openstack/
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_designate yoga-eom | #33 |
This issue was fixed in the openstack/
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_magnum yoga-eom | #34 |
This issue was fixed in the openstack/
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_sahara yoga-eom | #35 |
This issue was fixed in the openstack/
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_tacker yoga-eom | #36 |
This issue was fixed in the openstack/
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_trove yoga-eom | #38 |
This issue was fixed in the openstack/
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_designate victoria-eom | #39 |
This issue was fixed in the openstack/
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_magnum victoria-eom | #40 |
This issue was fixed in the openstack/
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_sahara victoria-eom | #41 |
This issue was fixed in the openstack/
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_tacker victoria-eom | #42 |
This issue was fixed in the openstack/
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_trove victoria-eom | #44 |
This issue was fixed in the openstack/
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_designate wallaby-eom | #45 |
This issue was fixed in the openstack/
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_magnum wallaby-eom | #46 |
This issue was fixed in the openstack/
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_sahara wallaby-eom | #47 |
This issue was fixed in the openstack/
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_tacker wallaby-eom | #48 |
This issue was fixed in the openstack/
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_trove wallaby-eom | #50 |
This issue was fixed in the openstack/
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_designate xena-eom | #51 |
This issue was fixed in the openstack/
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_magnum xena-eom | #52 |
This issue was fixed in the openstack/
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_sahara xena-eom | #53 |
This issue was fixed in the openstack/
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_tacker xena-eom | #54 |
This issue was fixed in the openstack/
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_trove xena-eom | #56 |
This issue was fixed in the openstack/
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_designate zed-eom | #57 |
This issue was fixed in the openstack/
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_magnum zed-eom | #58 |
This issue was fixed in the openstack/
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_sahara zed-eom | #59 |
This issue was fixed in the openstack/
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_tacker zed-eom | #60 |
This issue was fixed in the openstack/
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_trove zed-eom | #62 |
This issue was fixed in the openstack/
Fix proposed to branch: master /review. openstack. org/605117
Review: https:/