Thanks for this discussion and the agreement, it sounds good, I will
upload related changes.
--
Liu sheng
在 2016/3/7 23:42, gordon chung 写道:
On 07/03/2016 8:05 AM, Julien Danjou wrote:
On Mon, Mar 07 2016, gordon chung wrote:
shall we drop 'alarm search' nomenclature and use just 'alarm
On 07/03/2016 8:05 AM, Julien Danjou wrote:
> On Mon, Mar 07 2016, gordon chung wrote:
>
>> shall we drop 'alarm search' nomenclature and use just 'alarm list' for
>> both queries (standard and complex). the concern i have right now is the
>> proposal is to add standard query support to 'alarm
On Mon, Mar 07 2016, gordon chung wrote:
> shall we drop 'alarm search' nomenclature and use just 'alarm list' for
> both queries (standard and complex). the concern i have right now is the
> proposal is to add standard query support to 'alarm list' while complex
> query support is in 'alarm
On 07/03/2016 3:15 AM, Julien Danjou wrote:
> On Fri, Mar 04 2016, liusheng wrote:
>
>> Hi folks,
>> Currently, we have supported "aodh alarm list" and "aodh alarm search"
>> commands
>> to query alarms. They both need mandatory "--type" parameter, and I want to
>> drop the limitation[1]. if
On Fri, Mar 04 2016, liusheng wrote:
> Hi folks,
> Currently, we have supported "aodh alarm list" and "aodh alarm search"
> commands
> to query alarms. They both need mandatory "--type" parameter, and I want to
> drop the limitation[1]. if we agree that, the "alarm list" will only used to
>
On Fri, Mar 04, 2016 at 09:57:35AM +0800, liusheng wrote:
> Hi folks,
> Currently, we have supported "aodh alarm list" and "aodh alarm
> search" commands to query alarms. They both need mandatory "--type"
> parameter, and I want to drop the limitation[1]. if we agree that,
> the "alarm list"
Hi folks,
Currently, we have supported "aodh alarm list" and "aodh alarm search"
commands to query alarms. They both need mandatory "--type" parameter,
and I want to drop the limitation[1]. if we agree that, the "alarm
list" will only used to list all alarms and don't support any query
