start_timestamp/end_timestamp and start/end is not unified

Bug #1295100 reported by Liusheng
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ceilometer
Fix Released
Undecided
Liusheng

Bug Description

In 'ceilometer alarm-history', we can use start_timestamp/end_timestamp in query field;

In 'ceilometer resource-list', we can use start_timestamp/end_timestamp in query field;

In 'ceilometer sample-list', we can use start/end in query field;

In 'ceilometer statistics', we can use start/end in query field;

We should make these unified.

additionally, the 'timestamp' in query field has the same function

Liusheng (liusheng)
Changed in ceilometer:
assignee: nobody → Liusheng (liusheng)
Revision history for this message
gordon chung (chungg) wrote :

switching to ceilometerclient... please change back if this is incorrect.

affects: ceilometer → python-ceilometerclient
Liusheng (liusheng)
description: updated
Liusheng (liusheng)
affects: python-ceilometerclient → ceilometer
Liusheng (liusheng)
Changed in ceilometer:
assignee: Liusheng (liusheng) → nobody
assignee: nobody → Liusheng (liusheng)
Revision history for this message
Openstack Gerrit (openstack-gerrit) wrote : Fix proposed to ceilometer (master)

Fix proposed to branch: master
Review: https://review.openstack.org/90636

Changed in ceilometer:
status: New → In Progress
Revision history for this message
gordon chung (chungg) wrote :
Changed in ceilometer:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.