On Fri, Feb 28, 2014 at 12:48 PM, Nader Lahouti <[email protected]>wrote:
> > The idea behind this when we originally implemented notifications in >> Keystone was to >> provide the resource being changed, such as 'user', 'project', 'trust' >> and the uuid of that >> resource. From there your plugin and could request more information from >> Keystone by doing a >> GET on that resource. This way would could keep the payload of the >> notification sent minimal >> in case all the information on the resource wasn't required. > > > The issue is that, notification is send after project is deleted, so no > additional information can be fetched (i.e. project name,...). The GET > request fails. As there is only project ID is in resource_info in the > notification. In my case I at least need the name of the project. > What's the use case for needing the name of a project after it's been deleted? It's mutable in keystone anyway, so you certainly shouldn't be keeping references to project names. > > Thanks, > Nader. > > > > > On Mon, Feb 24, 2014 at 10:50 AM, Lance D Bragstad <[email protected]>wrote: > >> Response below. >> >> >> Best Regards, >> >> Lance Bragstad >> [email protected] >> >> Nader Lahouti <[email protected]> wrote on 02/24/2014 11:31:10 AM: >> >> > From: Nader Lahouti <[email protected]> >> > To: "OpenStack Development Mailing List (not for usage questions)" >> > <[email protected]>, >> > Date: 02/24/2014 11:37 AM >> > Subject: Re: [openstack-dev] [keystone] Notification When Creating/ >> > Deleting a Tenant in openstack >> >> > >> > Hi Swann, >> > >> > I was able to listen to keystone notification by setting >> > notifications in the keystone.conf file. I only needed the >> > notification (CURD) for project and handle it in my plugin code so >> > don't need ceilometer to handle them. >> > The other issue is that the notification is only for limited to >> > resource_id and don't have other information such as project name. >> >> The idea behind this when we originally implemented notifications in >> Keystone was to >> provide the resource being changed, such as 'user', 'project', 'trust' >> and the uuid of that >> resource. From there your plugin and could request more information from >> Keystone by doing a >> GET on that resource. This way would could keep the payload of the >> notification sent minimal >> in case all the information on the resource wasn't required. >> > > The issue that I'm facing is that GET fails as the project is deleted from > database, so cannot get any info from the resource_info in the notification > from > >> >> >> > >> > Thanks, >> > Nader. >> > >> > >> >> > On Mon, Feb 24, 2014 at 2:10 AM, Swann Croiset <[email protected]> >> wrote: >> > >> > Hi Nader, >> > >> > These notifications must be handled by Ceilometer like others [1]. >> > it is surprising that it does not already identity meters indeed... >> > probably nobody needs them before you. >> > I guess it remains to open a BP and code them like I recently did for >> Heat [2] >> > >> > >> > http://docs.openstack.org/developer/ceilometer/measurements.html >> > >> https://blueprints.launchpad.net/ceilometer/+spec/handle-heat-notifications >> > >> >> > 2014-02-20 19:10 GMT+01:00 Nader Lahouti <[email protected]>: >> > >> > Thanks Dolph for link. The document shows the format of the message >> > and doesn't give any info on how to listen to the notification. >> > Is there any other document showing the detail on how to listen or >> > get these notifications ? >> > >> > Regards, >> > Nader. >> > >> > On Feb 20, 2014, at 9:06 AM, Dolph Mathews <[email protected]> >> wrote: >> >> > Yes, see: >> > >> > http://docs.openstack.org/developer/keystone/event_notifications.html >> > >> > On Thu, Feb 20, 2014 at 10:54 AM, Nader Lahouti < >> [email protected] >> > > wrote: >> > Hi All, >> > >> > I have a question regarding creating/deleting a tenant in openstack >> > (using horizon or CLI). Is there any notification mechanism in place >> > so that an application get informed of such an event? >> > >> > If not, can it be done using plugin to send create/delete >> > notification to an application? >> > >> > Appreciate your suggestion and help. >> > >> > Regards, >> > Nader. >> > >> > _______________________________________________ >> > OpenStack-dev mailing list >> > [email protected] >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > >> > _______________________________________________ >> > OpenStack-dev mailing list >> > [email protected] >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > >> > _______________________________________________ >> > OpenStack-dev mailing list >> > [email protected] >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > >> > >> > _______________________________________________ >> > OpenStack-dev mailing list >> > [email protected] >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > _______________________________________________ >> > OpenStack-dev mailing list >> > [email protected] >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> >> _______________________________________________ >> OpenStack-dev mailing list >> [email protected] >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
