Re: [openstack-dev] Payload within RabbitMQ messages for Nova related exchanges
Hey there, thanks for the input. @Russel My bad, sorry. Yes I was talking about notifications. @Sandy I'll have a look into the links provided. Thanks. I guess we can consider this closed. Cheers, George On Tue, Apr 15, 2014 at 3:40 PM, Sandy Walsh wrote: > > > On 04/15/2014 10:07 AM, George Monday wrote: > > Hey there, > > > > I've got a quick question about the RabbitMQ exchanges. We are writing > > listeners > > for the RabbitMQ exchanges. The basic information about the tasks like > > compute.instance.create.[start|stop] etc. as stored in the 'payload' > > attribute of the > > json message are my concern at the moment. > > > > Does this follow a certain predefined structure that's consistent for > > the lifetime of, say, > > a specific nova api version? Will this change in major releases (from > > havana to icehouse)? > > Is this subject to change without notice? Is there a definition > > available somewhere? Like for > > the api versions? > > > > In short, how reliable is the json structure of the payload attribute in > > a rabbitMQ message? > > > > We just want to make sure, that with an update to the OpenStack > > controller, we wouldn't > > break our listeners? > > Hey George, > > Most of the notifications are documented here > https://wiki.openstack.org/wiki/SystemUsageData > > But, you're correct that there is no versioning on these currently, but > there are some efforts to fix this (specifically around CADF-support) > > Here's some more info on notifications if you're interested: > > http://www.sandywalsh.com/2013/09/notification-usage-in-openstack-report.html > > Hope it helps! > -S > > > > > > > My Best, > > George > > > > > > ___ > > OpenStack-dev mailing list > > OpenStack-dev@lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Payload within RabbitMQ messages for Nova related exchanges
On 04/15/2014 10:07 AM, George Monday wrote: > Hey there, > > I've got a quick question about the RabbitMQ exchanges. We are writing > listeners > for the RabbitMQ exchanges. The basic information about the tasks like > compute.instance.create.[start|stop] etc. as stored in the 'payload' > attribute of the > json message are my concern at the moment. > > Does this follow a certain predefined structure that's consistent for > the lifetime of, say, > a specific nova api version? Will this change in major releases (from > havana to icehouse)? > Is this subject to change without notice? Is there a definition > available somewhere? Like for > the api versions? > > In short, how reliable is the json structure of the payload attribute in > a rabbitMQ message? > > We just want to make sure, that with an update to the OpenStack > controller, we wouldn't > break our listeners? Hey George, Most of the notifications are documented here https://wiki.openstack.org/wiki/SystemUsageData But, you're correct that there is no versioning on these currently, but there are some efforts to fix this (specifically around CADF-support) Here's some more info on notifications if you're interested: http://www.sandywalsh.com/2013/09/notification-usage-in-openstack-report.html Hope it helps! -S > My Best, > George > > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Payload within RabbitMQ messages for Nova related exchanges
On 04/15/2014 09:07 AM, George Monday wrote: > Hey there, > > I've got a quick question about the RabbitMQ exchanges. We are writing > listeners > for the RabbitMQ exchanges. The basic information about the tasks like > compute.instance.create.[start|stop] etc. as stored in the 'payload' > attribute of the > json message are my concern at the moment. > > Does this follow a certain predefined structure that's consistent for > the lifetime of, say, > a specific nova api version? Will this change in major releases (from > havana to icehouse)? > Is this subject to change without notice? Is there a definition > available somewhere? Like for > the api versions? > > In short, how reliable is the json structure of the payload attribute in > a rabbitMQ message? > > We just want to make sure, that with an update to the OpenStack > controller, we wouldn't > break our listeners? First, we're talking specifically about notifications. Nova also uses messages between services, and those messages are considered private internal implementation details. The notifications are of course intended for consumption by other apps. We currently try to make sure that all changes to the body of these messages are backwards compatible. You should be safe within a version, but as usual, please watch the release notes for changes. At some point we really need to do something about the body of notifications so that they're properly versioned. -- Russell Bryant ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] Payload within RabbitMQ messages for Nova related exchanges
Hey there, I've got a quick question about the RabbitMQ exchanges. We are writing listeners for the RabbitMQ exchanges. The basic information about the tasks like compute.instance.create.[start|stop] etc. as stored in the 'payload' attribute of the json message are my concern at the moment. Does this follow a certain predefined structure that's consistent for the lifetime of, say, a specific nova api version? Will this change in major releases (from havana to icehouse)? Is this subject to change without notice? Is there a definition available somewhere? Like for the api versions? In short, how reliable is the json structure of the payload attribute in a rabbitMQ message? We just want to make sure, that with an update to the OpenStack controller, we wouldn't break our listeners? My Best, George ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
