No notifications on Neutron tag operations

Bug #1560226 reported by Steve McLellan
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
OpenStack Searchlight
New
High
Unassigned
neutron
Fix Released
Medium
Hirofumi Ichihara

Bug Description

When a tag's added to (or removed from) a resource, no notification is generated indicating that the network (or port or whatever) has changed, although tags *are* included in notification and API data for those resources. It'd be more consistent if attaching a tag to a network generated a notification in the same way as if it were renamed.

My use case is that Searchlight would really like to index tags attached to networks, routers, etc since it's a very powerful feature but we can't provide up to date information unless a notification's sent.

Tested on neutron mitaka rc1.

Tags: api
Henry Gessau (gessau)
tags: added: api
Revision history for this message
Hirofumi Ichihara (ichihara-hirofumi) wrote :

I'm not sure how notifications are passed to external system about updating network DB although I understand notification mechanism between servers and agents. Does neutron server notify when network is renamed?

Revision history for this message
Steve McLellan (sjmc7) wrote :

Yeah, there are events for update operations like renames - network.update.end, subnet.update.end etc. I know very little about neutron's codebase, unfortunately, though i may take a look once the mitaka release is out of the way.

Revision history for this message
Travis Tripp (travis-tripp) wrote :

On Searchlight side, being able to search by tag is very important (so setting high importance), but of course it is blocked and there is not a blocked status field.

Changed in searchlight:
importance: Undecided → High
summary: - No notifications on tag operations
+ No notifications on Neutron tag operations
Changed in neutron:
importance: Undecided → Medium
assignee: nobody → Hirofumi Ichihara (ichihara-hirofumi)
status: New → Confirmed
milestone: none → newton-1
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (master)

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

Changed in neutron:
status: Confirmed → In Progress
Revision history for this message
Hirofumi Ichihara (ichihara-hirofumi) wrote :

@Steve McLellan: Thank you. I got it. I pushed PoC. Can you review it(especially, I 'd like a suggestion about event_type)?

Changed in neutron:
milestone: newton-1 → newton-2
Changed in neutron:
milestone: newton-2 → newton-3
Changed in neutron:
milestone: newton-3 → newton-rc1
Changed in neutron:
milestone: newton-rc1 → ocata-1
Changed in neutron:
milestone: ocata-1 → ocata-2
Akihiro Motoki (amotoki)
Changed in neutron:
milestone: ocata-2 → ocata-3
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (master)

Reviewed: https://review.openstack.org/298133
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=0daed9ebcab7d46d066fd9d8af576d9aca0a7205
Submitter: Jenkins
Branch: master

commit 0daed9ebcab7d46d066fd9d8af576d9aca0a7205
Author: Hirofumi Ichihara <email address hidden>
Date: Tue Nov 29 14:26:24 2016 +0900

    Add notify for tag operations

    When a tag's added to (or removed from) a resource, no notification is
    generated indicating that the network (or port or whatever) has changed.
    This patch adds notify for tag operations.

    Change-Id: I4373b2220f87751a4d89462bef37d04bf9a71fe7
    Closes-Bug: #1560226

Changed in neutron:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron 10.0.0.0b3

This issue was fixed in the openstack/neutron 10.0.0.0b3 development milestone.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.