On Wed, Jan 31, 2018 at 1:17 AM, Matt Riedemann <mriede...@gmail.com> wrote:
> On 1/30/2018 9:37 AM, Mathieu Gagné wrote: > >> So I just discovered this documentation. It's awesome! Great job to >> all the ones involved! >> Now I wish we had the same in all projects. =) >> > > Maybe it's worth putting something into the community goals etherpad: > > https://etherpad.openstack.org/p/community-goals > > At this point, I'd say it's probably premature to push across all projects > since we don't have another service consuming nova's versioned > notifications yet. Searchlight was working on it, but then I think that got > stalled. Maybe after the Telemetry team starts looking at it to see how > things work for them from a consumer / client standpoint. It's so glad that Ceilometer is the first consumer of versioned notifications. Can I understand it as a trend that versioned notifications will replace unversioned notifications even though versioned notifications may have the only consumer for long time? You know Ceilometer consume unversioned notifications for now. So should we replace unversioned with versioned one by one according to the link[1] because we can't consume both as then we'd end up duplicating data? It may result in data lost with thoroughly transformation. [1] http://burndown.peermore.com/nova-notification/ -- Cheers, Hanxi Liu (IRC: lhx_) __________________________________________________________________________ > 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