Enable event-list reverse ordering

[Amy Fong]

When limits are applied to event-list, it would be helpful to see the most recent events. ie when there are many event-lists, and the user wants to see the more recent values first.

One option is to default to reverse ordering by default when limits are applied, another option is to introduce another parameter to explicitly specify a reserve ordering on the return values.

[Hanxi Liu (hanxi-liu)]

It is convenient to users because users can get the recent records with limits function.So I think you proposal is useful.

[xiaozhuangqing (xiaozhuangqing)]

maybe I can add a option parameter on cli: event list --resent ?

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/372851
Committed: https://git.openstack.org/cgit/openstack/panko/commit/?id=272c872f2fe9d0658f059538c019836d093a5486
Submitter: Jenkins
Branch: master

commit 272c872f2fe9d0658f059538c019836d093a5486
Author: Amy Fong <email address hidden>
Date: Thu Sep 22 13:51:23 2016 -0400

    Enable paginate query for event listing

    sorting and marker options are enabled for event listing (for sqlalchemy only)
    using oslob.db.

        sort -- list of sorting criteria. Each sorting option has to format
                <sort key>:<sort direction>

                Valid sort keys: message_id, generated
                Valid sort directions: asc (ascending), desc (descending)
                        This defaults to asc if unspecified

                If sort list is unspecified, this defaults to
                ['generated:asc', 'message_id:asc']

        marker -- If specified, assumed to be an integer and assumed to be the
                  message id of the last object on the previous page of the results

    limit is still available and supported for non sqlalchemy databases

    Closes-bug: #1615699
    Change-Id: I0441ca6283be5859c09c3d381ffbb52ca4a79eca

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/panko 2.0.0 release.