quantum server does not honor default_notification_level

[Akihiro Motoki]

Notifications in quantum api do not honor default_notification_level in quantum.conf and always use INFO level.
If default_notification_level is set to a value other than INFO, dhcp-agent cannot receive notification from quantum server.

[Akihiro Motoki (amotoki)]

I am wondering how this bug should be fixed.
Notification level is usually used to filter notifications. E.g., I don't want to receive DEBUG level notifications.
However, dhcp-agent must receive some kinds of notifications regardless of its level.
My opinion is dhcp-agent should use RPC instead of notification to receive subnet events from the quantum server.

[dan wendlandt (danwent)]

i see no active review here, so i'm moving this bug out of G-2.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/19545
Committed: http://github.com/openstack/quantum/commit/faa1733ef0adfdfb3e625d60d96b08ce764ca824
Submitter: Jenkins
Branch: master

commit faa1733ef0adfdfb3e625d60d96b08ce764ca824
Author: Akihiro MOTOKI <email address hidden>
Date: Tue Jan 8 16:57:23 2013 +0900

    Use default_notification_level when notification

    Fix bug 1089773

    Notifications in quantum api do not honor default_notification_level
    in quantum.conf and always use INFO level. On the other hand
    dhcp-agent refers to default_notification_level.
    If default_notification_level is set to a value other than INFO,
    dhcp-agent cannot receive notification from quantum server.

    Change-Id: Ie3ae576d62e91651aa59b2324ec114716181107f

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/folsom
Review: https://review.openstack.org/19929

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/19929
Committed: http://github.com/openstack/quantum/commit/1a24b687287393f96b724a6cfc98a796fa3cb2ea
Submitter: Jenkins
Branch: stable/folsom

commit 1a24b687287393f96b724a6cfc98a796fa3cb2ea
Author: Akihiro MOTOKI <email address hidden>
Date: Tue Jan 8 16:57:23 2013 +0900

    Use default_notification_level when notification

    Fix bug 1089773

    Notifications in quantum api do not honor default_notification_level
    in quantum.conf and always use INFO level. On the other hand
    dhcp-agent refers to default_notification_level.
    If default_notification_level is set to a value other than INFO,
    dhcp-agent cannot receive notification from quantum server.

    Change-Id: Ie3ae576d62e91651aa59b2324ec114716181107f