Re: [openstack-dev] [all] connecting nova notification users and developers
On Wed, Aug 30, 2017 at 4:30 PM, Balazs Gibizer wrote: 1) We in the nova developer community would like to see which projects are using (or planning to use) the nova notification interface. Also we would like to know if you are using the legacy unversioned notifications or the new versioned ones. We would like to know what are your use cases towards our notification interface and we also would like to get any type of feedback about the interface (both the old and the new one). Based on this information we can make better decision where to focus our development effort. As a good example we already have a cooperation with the searchlight project to enhance nova's versioned notification interface based on their needs [3]. I opened an etherpad [4] to collect the projects and the feedback and we can go through that feedback in the PTG to define some actions. Thanks for all the replies and etherpad updates. We will discuss the gathered information on the nova track on the PTG most probably on Friday. Cheers, gibi __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] connecting nova notification users and developers
On 04/09/17 09:55 PM, Lingxian Kong wrote: > Hi Gordon, does Aodh rely on Ceilometer to receive events or it could > receive notifications directly from other services? yes. Ceilometer normalises the message into something Aodh can understand. (that's how it behaves currently) -- gord __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] connecting nova notification users and developers
Novajoin[1] uses notifications to detect when an instance is provisioned and register it to FreeIPA (in short). I added it to the etherpad accordingly. We're not yet using versioned notifications. [1] https://review.openstack.org/#/admin/projects/openstack/novajoin On Wed, Aug 30, 2017 at 5:30 PM, Balazs Gibizer wrote: > Hi, > > Nova emits notifications for many different event, like different instance > actions[1]. Also the nova developer community is working on making nova > notifications well defined and easy to consume [2]. > > The goal of this mail is twofold. > > 1) We in the nova developer community would like to see which projects are > using (or planning to use) the nova notification interface. Also we would > like to know if you are using the legacy unversioned notifications or the > new versioned ones. We would like to know what are your use cases towards > our notification interface and we also would like to get any type of > feedback about the interface (both the old and the new one). Based on this > information we can make better decision where to focus our development > effort. As a good example we already have a cooperation with the > searchlight project to enhance nova's versioned notification interface > based on their needs [3]. > > I opened an etherpad [4] to collect the projects and the feedback and we > can go through that feedback in the PTG to define some actions. > > 2) Creating a well defined and easy to use notification interface gives us > plenty of work in nova. So we are also looking for developers who can help > us in this work. Big chunk of [2] is considered as low hanging fruit and > I'm happy to mentor anybody who is interested learning this part of nova. > If you want to join to this work just ping me (gibi) or IRC. > > Cheers, > gibi > > [1]https://docs.openstack.org/nova/latest/reference/notifications.html > [2]https://blueprints.launchpad.net/nova/+spec/versioned- > notification-transformation-queens > [3]https://blueprints.launchpad.net/nova/+spec/additional- > notification-fields-for-searchlight > [4]https://etherpad.openstack.org/p/queens-nova-notifications > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Juan Antonio Osorio R. e-mail: jaosor...@gmail.com __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] connecting nova notification users and developers
Hi, Vitrage holds a topology graph with all resources in the system and the relationships between them, for fault correlation purposes[1]. It uses notifications from Nova (as well as from other components) to update its internal state[2]. It is important for us to get immediate notifications about state changes, so we can react fast. For example, if a new instance is created on a host with high CPU load, we will immediately raise an alarm on that instance that it may suffer from CPU performance degradation. I’ll be happy to discuss our use cases at the PTG. [1] https://wiki.openstack.org/wiki/Vitrage [2] https://github.com/openstack/vitrage/blob/master/vitrage/datasources/nova/instance/driver.py Best Regards, Ifat. On 30/08/2017, 17:30, "Balazs Gibizer" wrote: Hi, Nova emits notifications for many different event, like different instance actions[1]. Also the nova developer community is working on making nova notifications well defined and easy to consume [2]. The goal of this mail is twofold. 1) We in the nova developer community would like to see which projects are using (or planning to use) the nova notification interface. Also we would like to know if you are using the legacy unversioned notifications or the new versioned ones. We would like to know what are your use cases towards our notification interface and we also would like to get any type of feedback about the interface (both the old and the new one). Based on this information we can make better decision where to focus our development effort. As a good example we already have a cooperation with the searchlight project to enhance nova's versioned notification interface based on their needs [3]. I opened an etherpad [4] to collect the projects and the feedback and we can go through that feedback in the PTG to define some actions. 2) Creating a well defined and easy to use notification interface gives us plenty of work in nova. So we are also looking for developers who can help us in this work. Big chunk of [2] is considered as low hanging fruit and I'm happy to mentor anybody who is interested learning this part of nova. If you want to join to this work just ping me (gibi) or IRC. Cheers, gibi [1]https://docs.openstack.org/nova/latest/reference/notifications.html [2]https://blueprints.launchpad.net/nova/+spec/versioned-notification-transformation-queens [3]https://blueprints.launchpad.net/nova/+spec/additional-notification-fields-for-searchlight [4]https://etherpad.openstack.org/p/queens-nova-notifications __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] connecting nova notification users and developers
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. Original message From: Balazs Gibizer Date: 8/30/17 09:32 (GMT-06:00) To: "OpenStack Development Mailing List (not for usage questions)" Subject: [openstack-dev] [all] connecting nova notification users and developers Hi, Nova emits notifications for many different event, like different instance actions[1]. Also the nova developer community is working on making nova notifications well defined and easy to consume [2]. The goal of this mail is twofold. 1) We in the nova developer community would like to see which projects are using (or planning to use) the nova notification interface. Also we would like to know if you are using the legacy unversioned notifications or the new versioned ones. We would like to know what are your use cases towards our notification interface and we also would like to get any type of feedback about the interface (both the old and the new one). Based on this information we can make better decision where to focus our development effort. As a good example we already have a cooperation with the searchlight project to enhance nova's versioned notification interface based on their needs [3]. I opened an etherpad [4] to collect the projects and the feedback and we can go through that feedback in the PTG to define some actions. 2) Creating a well defined and easy to use notification interface gives us plenty of work in nova. So we are also looking for developers who can help us in this work. Big chunk of [2] is considered as low hanging fruit and I'm happy to mentor anybody who is interested learning this part of nova. If you want to join to this work just ping me (gibi) or IRC. Cheers, gibi [1]https://docs.openstack.org/nova/latest/reference/notifications.html [2]https://blueprints.launchpad.net/nova/+spec/versioned-notification-transformation-queens [3]https://blueprints.launchpad.net/nova/+spec/additional-notification-fields-for-searchlight [4]https://etherpad.openstack.org/p/queens-nova-notifications __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] connecting nova notification users and developers
On Sat, Sep 2, 2017 at 1:28 AM, gordon chung wrote: > > > On 2017-08-30 10:30 AM, Balazs Gibizer wrote: > > 1) We in the nova developer community would like to see which projects > > are using (or planning to use) the nova notification interface. Also we > > would like to know if you are using the legacy unversioned notifications > > or the new versioned ones. We would like to know what are your use cases > > towards our notification interface and we also would like to get any > > type of feedback about the interface (both the old and the new one). > > Based on this information we can make better decision where to focus our > > development effort. As a good example we already have a cooperation > > with the searchlight project to enhance nova's versioned notification > > interface based on their needs [3]. > > ceilometer uses it to create events and meters. events just capture the > message as is and might strip out some superfluous details. meters are > numerical values (associated with time). in both cases, we have yaml > files where we just define 'if message event_type equals blah, strip out > values x, y, and z'[1][2] Hi Gordon, does Aodh rely on Ceilometer to receive events or it could receive notifications directly from other services? __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] connecting nova notification users and developers
On 2017-08-30 10:30 AM, Balazs Gibizer wrote: > 1) We in the nova developer community would like to see which projects > are using (or planning to use) the nova notification interface. Also we > would like to know if you are using the legacy unversioned notifications > or the new versioned ones. We would like to know what are your use cases > towards our notification interface and we also would like to get any > type of feedback about the interface (both the old and the new one). > Based on this information we can make better decision where to focus our > development effort. As a good example we already have a cooperation > with the searchlight project to enhance nova's versioned notification > interface based on their needs [3]. ceilometer uses it to create events and meters. events just capture the message as is and might strip out some superfluous details. meters are numerical values (associated with time). in both cases, we have yaml files where we just define 'if message event_type equals blah, strip out values x, y, and z'[1][2] we don't use versioned notifications but if we had resources we might[3] > > I opened an etherpad [4] to collect the projects and the feedback and we > can go through that feedback in the PTG to define some actions. most of us wont' be at PTG. if you find Hanxi Liu, then you might have someone with some knowledge of telemetry projects. we can be reached on irc or ML regardless. [1] https://github.com/openstack/ceilometer/blob/master/ceilometer/pipeline/data/event_definitions.yaml [2] https://github.com/openstack/ceilometer/blob/master/ceilometer/data/meters.d/meters.yaml [3] https://bugs.launchpad.net/ceilometer/+bug/1665449 cheers, -- gord __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [all] connecting nova notification users and developers
Hi, Nova emits notifications for many different event, like different instance actions[1]. Also the nova developer community is working on making nova notifications well defined and easy to consume [2]. The goal of this mail is twofold. 1) We in the nova developer community would like to see which projects are using (or planning to use) the nova notification interface. Also we would like to know if you are using the legacy unversioned notifications or the new versioned ones. We would like to know what are your use cases towards our notification interface and we also would like to get any type of feedback about the interface (both the old and the new one). Based on this information we can make better decision where to focus our development effort. As a good example we already have a cooperation with the searchlight project to enhance nova's versioned notification interface based on their needs [3]. I opened an etherpad [4] to collect the projects and the feedback and we can go through that feedback in the PTG to define some actions. 2) Creating a well defined and easy to use notification interface gives us plenty of work in nova. So we are also looking for developers who can help us in this work. Big chunk of [2] is considered as low hanging fruit and I'm happy to mentor anybody who is interested learning this part of nova. If you want to join to this work just ping me (gibi) or IRC. Cheers, gibi [1]https://docs.openstack.org/nova/latest/reference/notifications.html [2]https://blueprints.launchpad.net/nova/+spec/versioned-notification-transformation-queens [3]https://blueprints.launchpad.net/nova/+spec/additional-notification-fields-for-searchlight [4]https://etherpad.openstack.org/p/queens-nova-notifications __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev