On Fri, Apr 08, 2016 at 09:52:31AM +0000, Balázs Gibizer wrote: > > -----Original Message----- > > From: Qiming Teng [mailto:[email protected]] > > Sent: April 07, 2016 15:42 > > > > The only gap based on my limited understanding is that nova is not emitting > > events compute host state changes. This knowledge is still kept inside nova > > as some service states. If that info is posted to oslo messaging, a lot of > > usage > > scenarios can be enabled and we can avoid too much churns to nova itself. > > Nova does not really know the state of the compute host, it knows only the > state of the nova-compute service running on the compute host. In Mitaka we > added notification about the service status[2]. > Also there is a proposal about notification about hypervisor info change [1]. > > Cheers, > Gibi > > [1] https://review.openstack.org/#/c/299807/ > [2] > http://docs.openstack.org/developer/nova/notifications.html#existing-versioned-notifications > >
Thanks for the sharing, Balázs. The mitaka service status notification looks pretty useful, I'll try it. Regards, Qiming > > > > Regards, > > Qiming > > > > > > __________________________________________________________ > > ________________ > > OpenStack Development Mailing List (not for usage questions) > > Unsubscribe: OpenStack-dev- > > [email protected]?subject:unsubscribe > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
