Description of problem: notifications are supposed to be enabled by default (via neutron-dist.conf), but due to the fact that in Ocata we dropped old aliases for notification drivers, and we used such an old alias in neutron-dist.conf, it stopped working. This totally breaks billing for Neutron services. Steps to Reproduce: 1. set up default OSP11 environment with Ceilometer. 2. create neutron resources. Actual results: events for new resources not seen in Ceilometer. Expected results: events should be available via Ceilometer.
> Description of problem: notifications are supposed to be enabled by default > (via neutron-dist.conf), but due to the fact that in Ocata we dropped old > aliases for notification drivers, and we used such an old alias in > neutron-dist.conf, it stopped working. > > This totally breaks billing for Neutron services. @pradk I would argue that deployment tools should explicitly set notification options when Telemetry is enabled, and not rely on defaults.
Alan, I agree, but there should be an explicit decision (and installer integration) for that in place. + release note and stuff. We can't do it without thinking through the implications like we did for Ocata. There is a noop driver for what I know that could be explicitly picked if we don't need to do anything. (Or maybe empty list which is the default is enough?) Let's discuss it in broader scope than just for Neutron.
Just to add a comment here, this probably shouldn't be fixed in packaging as it does require some knowledge of the end user's deployment to know if ceilometer is actually configured. If the notifications are enabled and no one is listening, this can fill up the rabbit queues for the operator. It would be better to disable it by default in packaging (unless there's some other functionality that requires it) and enable it only if ceilometer is being deployed.
@Alex, feel free to report a bug against neutron, and we will have a proper look at it (with handling upgrades and whatnot).
Hi, Is network create is enough to trigger ceilometer event ? tnx
Yes.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:1785