Open Stack

Hi,

On the Stein PTG the nova team agreed to deprecate the legacy, 
unversioned notification interface of nova. We also agreed that we will 
not try to remove the legacy notification sending from the code any 
time soon. So this deprecation means the following:
* by default configuration nova will only emit versioned notifications, 
but the unversioned notifications still can be turned on in the 
configuration.
* nova will not maintain the legacy notification code path further, so 
it can break

I pushed the deprecation patch [2] but it will only be merged after the 
remaining versioned notification transformation patches [3] are merged.

Cheers,
gibi

[2] https://review.openstack.org/#/c/603079
[3] 
https://review.openstack.org/#/q/topic:bp/versioned-notification-transformation-stein

On Tue, Aug 28, 2018 at 4:31 PM, Balázs Gibizer 
<balazs.gibizer at ericsson.com> wrote:
> Thanks for all the responses. I collected them on the nova ptg 
> discussion etherpad [1] (L186 at the moment). The nova team will talk 
> about deprecation of the legacy interface on Friday on the PTG. If 
> you want participate in the discussion but you are not planning to 
> sit in the nova room whole day then let me know and I will try to 
> ping you over IRC when we about to start the item.
> 
> Cheers,
> gibi
> 
> [1] https://etherpad.openstack.org/p/nova-ptg-stein
> 
> On Thu, Aug 9, 2018 at 11:41 AM, Balázs Gibizer 
> <balazs.gibizer at ericsson.com> wrote:
>> Dear Nova notification consumers!
>> 
>> 
>> The Nova team made progress with the new versioned notification 
>> interface [1] and it is almost reached feature parity [2] with the 
>> legacy, unversioned one. So Nova team will discuss on the upcoming 
>> PTG the deprecation of the legacy interface. There is a list of 
>> projects (we know of) consuming the legacy interface and we would 
>> like to know if any of these projects plan to switch over to the 
>> new interface in the foreseeable future so we can make a well 
>> informed decision about the deprecation.
>> 
>> 
>> * Searchlight [3] - it is in maintenance mode so I guess the answer 
>> is no
>> * Designate [4]
>> * Telemetry [5]
>> * Mistral [6]
>> * Blazar [7]
>> * Watcher [8] - it seems Watcher uses both legacy and versioned nova 
>> notifications
>> * Masakari - I'm not sure Masakari depends on nova notifications or 
>> not
>> 
>> Cheers,
>> gibi
>> 
>> [1] 
>> https://docs.openstack.org/nova/latest/reference/notifications.html
>> [2] http://burndown.peermore.com/nova-notification/
>> 
>> [3] 
>> https://github.com/openstack/searchlight/blob/master/searchlight/elasticsearch/plugins/nova/notification_handler.py
>> [4] 
>> https://github.com/openstack/designate/blob/master/designate/notification_handler/nova.py
>> [5] 
>> https://github.com/openstack/ceilometer/blob/master/ceilometer/pipeline/data/event_definitions.yaml#L2
>> [6] 
>> https://github.com/openstack/mistral/blob/master/etc/event_definitions.yml.sample#L2
>> [7] 
>> https://github.com/openstack/blazar/blob/5526ed1f9b74d23b5881a5f73b70776ba9732da4/doc/source/user/compute-host-monitor.rst
>> [8] 
>> https://github.com/openstack/watcher/blob/master/watcher/decision_engine/model/notification/nova.py#L335
>> 
>> 
> 
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: 
> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev