Open Stack

RPC  will send the notifications to the queues that have joined the exchanges.

Any notifications that were published before your service registers are not seen by your service.

Your service needs to get hold of the data using Nova and Neutron API.

In summary,  when your service comes up,  in addition to registering for notifications,  it is needed to get the existing data using Nova/Neutrion API.

Thanks
SRini

From: Ravi Chunduru [mailto:ravivsn at gmail.com]
Sent: Wednesday, July 31, 2013 10:57 AM
To: OpenStack Development Mailing List
Subject: Re: [openstack-dev] Openstack Service requirement

Hi,
 Could any one respond on this? This helps us in designing services written on top of openstack.

Thanks,
-Ravi.
On Tue, Jul 30, 2013 at 7:38 PM, Ravi Chunduru <ravivsn at gmail.com<mailto:ravivsn at gmail.com>> wrote:
Hi,
 I was designing a Openstack service that listens on notifications generated from Nova, Neutron etc., for our custom needs to monitor and act up on events.
I have an interesting observation from openstack perspective and I would like to know community thinking about it.

By the time an openstack service starts, it would have missed some notifications.  How do we deal with it?

For example, Designate(DNSaaS) starts and by that time some VMs got created, it would loose to update the DNS servers for those VMs.
Should any openstack service such as Designate  call openstack APIs and get existing configuration?

Thanks,
--
Ravi



--
Ravi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130801/fed49808/attachment.html>