[openstack-dev] [aodhclient] does the aodh have the feature for import/export batch alarms?
r-mibu at cq.jp.nec.com
Fri May 20 05:24:14 UTC 2016
I also agree with ZhiQiang.
How about using Heat Template which improve portability of app and configs?
> -----Original Message-----
> From: ZhiQiang Fan [mailto:aji.zqfan at gmail.com]
> Sent: Friday, May 20, 2016 11:42 AM
> To: li.yuanzhen at zte.com.cn
> Cc: OpenStack Development Mailing List; Ildikó Váncsa; lianhao.lu at intel.com; Sheng Liu; Mibu Ryota(壬生 亮太); Julien
> Subject: Re: [openstack-dev] [aodhclient] does the aodh have the feature for import/export batch alarms?
> batch alarm is not supported, and I think it is a burden instead of good feature to implement it in aodh
> import/export alarm is not supported, considering dump db and restore it in new env? or you can get alarm list from old
> env and create new alarm in new env via REST API if data set is not too large.
> On Fri, May 20, 2016 at 9:37 AM, <li.yuanzhen at zte.com.cn> wrote:
> HI All,
> in the aodh/aodhclient, I not find the feature for import/export batch alarms.
> I mainly want to use it to implement the following requirement:
> In "migrate alarms from one openstack env to another openstack env" scenario, I would like to do this
> by a simple method, such as exporting/downloading the alarms from one env and then importing these alarms
> to a new env.
> currently, does the aodh have the similar command for import/export batch alarms?
> or does have an alternative method to implement this requirement?
> If not have, does the feature need to add in aodh/aodhclient?
> ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith)
> is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended
> recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly
> prohibited. If you have received this mail in error, please delete it and notify us immediately.
More information about the OpenStack-dev