As a developer feature, I would vote for merging in early Ocata rather than as a FFE. Since the potential risk is to users and operators and they won't generally benefit from the feature, I don't see the upside outweighing the potential risk. It's not a localized change either. That said, I think the profiler work will be extremely valuable in Ocata and beyond. Thanks for your continued efforts on bringing it to life. David On Wed, Aug 31, 2016 at 6:14 AM, Timur Sufiev <tsufiev at mirantis.com> wrote: > Hello, folks! > > I'd like to ask for a feature-freeze exception for a Horizon Profiler > feature [1], that has been demoed long ago (during Portland midcycle Feb > 2016) and is finally ready. The actual request applies to the 3 patches [2] > that provide the bulk of Profiler functionality. > > It is a quite useful feature that is aimed mostly to developers, thus it is > constrained within Developer dashboard and disabled by default - so it > shouldn't have any impact on User-facing Horizon capabilities. > > [1] > https://blueprints.launchpad.net/horizon/+spec/openstack-profiler-at-developer-dashboard > [2] > https://review.openstack.org/#/q/topic:bp/openstack-profiler-at-developer-dashboard+status:open > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >