OpenStack Searchlight

No notifications on Neutron tag operations

Bug #1560226 reported by Steve McLellan on 2016-03-21

This bug affects 3 people

Affects		Status	Importance	Assigned to	Milestone
	OpenStack Searchlight	New	High	Unassigned
	neutron	Fix Released	Medium	Hirofumi Ichihara	neutron ocata-3 "o3"

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:

Henry Gessau (gessau) on 2016-03-22

tags:

added: api

Revision history for this message

Hirofumi Ichihara (ichihara-hirofumi) wrote on 2016-03-23:

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 on 2016-03-23:

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 2016-03-25:

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

Hirofumi Ichihara (ichihara-hirofumi) on 2016-03-28

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 on 2016-03-28: 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 on 2016-03-28:

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

Armando Migliaccio (armando-migliaccio) on 2016-06-03

Changed in neutron:
milestone:	newton-1 → newton-2

Armando Migliaccio (armando-migliaccio) on 2016-07-15

Changed in neutron:
milestone:	newton-2 → newton-3

Armando Migliaccio (armando-migliaccio) on 2016-09-01

Changed in neutron:
milestone:	newton-3 → newton-rc1

Armando Migliaccio (armando-migliaccio) on 2016-09-13

Changed in neutron:
milestone:	newton-rc1 → ocata-1

Armando Migliaccio (armando-migliaccio) on 2016-11-16

Changed in neutron:
milestone:	ocata-1 → ocata-2

Akihiro Motoki (amotoki) on 2016-12-22

Changed in neutron:
milestone:	ocata-2 → ocata-3

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2017-01-05: 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