I don't think we need two APIs to act duplicated functionalities, the
"sample-list -m" command actually invoke API "GET
/V2/meters/<meter_name>", it is more like a meter related API, not
sample. I personally prefer to mark the "sample-list -m" command
deprecated and dropped in future cycle. is this reasonable ?
在 2015/11/6 6:39, gord chung 写道:
i'm sort of torn on this item. there's a general feeling that
regarding api, nothing should be dropped so i'm hesitant to actually
deprecate it. i think changing the data also is very dangerous when it
comes to compatibility (even though keeping it increases inconsistency).
maybe the better solution is to document that these are different APIs
and will return different results.
On 05/11/2015 2:30 AM, Lin Juan IX Xia wrote:
Hi,
Here is an open bug : https://bugs.launchpad.net/ceilometer/+bug/1497073
Is it a bug or not?
For the command "ceilometer sample-list --meter cpu", it calls
"/v2/meter" API and return the OldSample objects
which return body is different from "ceilometer sample-list --query
'meter=cpu'".
To fix this inconformity, we can deprecate the command using -m or
fix it to return the same body as command sample-list
Best Regards,
Xia Linjuan
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:[email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
gord
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
