messaging notification configuration is missing

[jacky06]

messaging notification configuration is missing

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/605117

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/605117
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_tacker/commit/?id=88a678bbadd79e5afd703290673dc1cb2465c12c
Submitter: Zuul
Branch: master

commit 88a678bbadd79e5afd703290673dc1cb2465c12c
Author: ZhijunWei <email address hidden>
Date: Wed Sep 19 08:42:03 2018 -0400

    Remove the unnecessary verbose defined

    Change-Id: Ie188de9270e6666f2ca1e5c755f6db757375abb8
    Closes-Bug: #1794320

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/605112
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_magnum/commit/?id=9508e525eda4eb883bdde1efce1c517f4f1d3f5d
Submitter: Zuul
Branch: master

commit 9508e525eda4eb883bdde1efce1c517f4f1d3f5d
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: Iaadc0d852c003e653e00b4736ddc28f16ddfec5a
    Closes-Bug: #1794320

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/605113
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_blazar/commit/?id=6703cf06dd5a7d9ccefbbd5e6db2126cf47d8d21
Submitter: Zuul
Branch: master

commit 6703cf06dd5a7d9ccefbbd5e6db2126cf47d8d21
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: I2b4c4a119fa300fb5b64eaaf947e3c688bdb6e84
    Closes-Bug: #1794320

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/605114
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_trove/commit/?id=3bbc52b399d0aaf2874a7f88806f94f2514e2aa3
Submitter: Zuul
Branch: master

commit 3bbc52b399d0aaf2874a7f88806f94f2514e2aa3
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: Ie967b281e15127bbf611aca557e99ac6b3d1cd4b
    Closes-Bug: #1794320

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/605108
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_tacker/commit/?id=56dc20030b9c391a921d5fdbad014f07313a4cc6
Submitter: Zuul
Branch: master

commit 56dc20030b9c391a921d5fdbad014f07313a4cc6
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: I60e92e14c0893b80f4023b6b6681864fee5228e5
    Closes-Bug: #1794320

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/605111
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_sahara/commit/?id=7f595f01b10a59d8fc9df3509a765e8f722ee3eb
Submitter: Zuul
Branch: master

commit 7f595f01b10a59d8fc9df3509a765e8f722ee3eb
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: Ib68aa2669b5d70626ed2777d5601d8914207451d
    Closes-Bug: #1794320

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/623943

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/623944

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/623945

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/605109
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_designate/commit/?id=3cdd0d103afef8b7d9f48da72c1c47765e473bad
Submitter: Zuul
Branch: master

commit 3cdd0d103afef8b7d9f48da72c1c47765e473bad
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: Ie5cc5499980f986f1a7e530adf42f4dcc43fbaca
    Closes-Bug: #1794320

[OpenStack Infra (hudson-openstack)]

Change abandoned by weizj (<email address hidden>) on branch: stable/rocky
Review: https://review.openstack.org/623944

[OpenStack Infra (hudson-openstack)]

Change abandoned by weizj (<email address hidden>) on branch: stable/rocky
Review: https://review.openstack.org/623943

[OpenStack Infra (hudson-openstack)]

Change abandoned by weizj (<email address hidden>) on branch: stable/rocky
Review: https://review.openstack.org/623945

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-ansible-os_designate stein-eol release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-ansible-os_magnum stein-eol release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-ansible-os_sahara stein-eol release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-ansible-os_tacker stein-eol release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-ansible-os_trove stein-eol release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-ansible-os_designate train-eol release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-ansible-os_magnum train-eol release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-ansible-os_sahara train-eol release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-ansible-os_tacker train-eol release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-ansible-os_trove train-eol release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-ansible-os_designate ussuri-eol release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-ansible-os_magnum ussuri-eol release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-ansible-os_sahara ussuri-eol release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-ansible-os_tacker ussuri-eol release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-ansible-os_trove ussuri-eol release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-ansible-os_designate yoga-eom release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-ansible-os_magnum yoga-eom release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-ansible-os_sahara yoga-eom release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-ansible-os_tacker yoga-eom release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-ansible-os_trove yoga-eom release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-ansible-os_designate victoria-eom release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-ansible-os_magnum victoria-eom release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-ansible-os_sahara victoria-eom release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-ansible-os_tacker victoria-eom release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-ansible-os_trove victoria-eom release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-ansible-os_designate wallaby-eom release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-ansible-os_magnum wallaby-eom release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-ansible-os_sahara wallaby-eom release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-ansible-os_tacker wallaby-eom release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-ansible-os_trove wallaby-eom release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-ansible-os_designate xena-eom release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-ansible-os_magnum xena-eom release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-ansible-os_sahara xena-eom release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-ansible-os_tacker xena-eom release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-ansible-os_trove xena-eom release.