<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>As you mention, searchlight consumes notifications from nova and other services. We've been moving towards versioned notifications over the last couple of cycles. Our use case is maybe unusual that we'd prefer notifications to represent the current state
of a resource (with a timestamp) though I can think of others where the delta is more important. We've been working with you towards having the payloads have more in common with what you'd get from nova api responses since part of what we're trying to do is
act as a fast cache.<br>
<br>
-------- Original message --------<br>
From: Balazs Gibizer <balazs.gibizer@ericsson.com> <br>
Date: 8/30/17 09:32 (GMT-06:00) <br>
To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org>
<br>
Subject: [openstack-dev] [all] connecting nova notification users and developers <br>
<br>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Hi,<br>
<br>
Nova emits notifications for many different event, like different <br>
instance actions[1]. Also the nova developer community is working on <br>
making nova notifications well defined and easy to consume [2].<br>
<br>
The goal of this mail is twofold.<br>
<br>
1) We in the nova developer community would like to see which projects <br>
are using (or planning to use) the nova notification interface. Also we <br>
would like to know if you are using the legacy unversioned <br>
notifications or the new versioned ones. We would like to know what are <br>
your use cases towards our notification interface and we also would <br>
like to get any type of feedback about the interface (both the old and <br>
the new one). Based on this information we can make better decision <br>
where to focus our development effort. As a good example we already <br>
have a cooperation with the searchlight project to enhance nova's <br>
versioned notification interface based on their needs [3].<br>
<br>
I opened an etherpad [4] to collect the projects and the feedback and <br>
we can go through that feedback in the PTG to define some actions.<br>
<br>
2) Creating a well defined and easy to use notification interface gives <br>
us plenty of work in nova. So we are also looking for developers who <br>
can help us in this work. Big chunk of [2] is considered as low hanging <br>
fruit and I'm happy to mentor anybody who is interested learning this <br>
part of nova. If you want to join to this work just ping me (gibi) or <br>
IRC.<br>
<br>
Cheers,<br>
gibi<br>
<br>
[1]https://docs.openstack.org/nova/latest/reference/notifications.html<br>
[2]https://blueprints.launchpad.net/nova/+spec/versioned-notification-transformation-queens<br>
[3]https://blueprints.launchpad.net/nova/+spec/additional-notification-fields-for-searchlight<br>
[4]https://etherpad.openstack.org/p/queens-nova-notifications<br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div>
</span></font>
</body>
</html>