liu-sheng 6244caf058 Delete its corresponding history data when deleting an alarm ... The history data of an alarm will still be stored in storage after the alarm being deleted. that is easy to cause residue issue. Change-Id: I5f6d7a1998104335079b7988e3d0b929b8854b28 Closes-Bug: #1476883		2015-07-27 19:25:54 +08:00
..
api	Delete its corresponding history data when deleting an alarm	2015-07-27 19:25:54 +08:00
cmd	evaluator: stop using global conf in evaluator service	2015-07-24 11:14:35 +02:00
evaluator	Use user_id/project_id from service_credentials in alarm_change	2015-07-27 14:38:25 +08:00
hacking	Rename to aodh	2015-06-25 14:46:39 +02:00
locale	Imported Translations from Transifex	2015-07-23 06:18:27 +00:00
notifier	notifier: stop using global conf object	2015-07-24 15:10:06 +02:00
openstack	Switch to oslo.utils.fileutils	2015-07-24 10:13:05 +02:00
storage	Delete its corresponding history data when deleting an alarm	2015-07-27 19:25:54 +08:00
tests	Delete its corresponding history data when deleting an alarm	2015-07-27 19:25:54 +08:00
__init__.py	Rename to aodh	2015-06-25 14:46:39 +02:00
coordination.py	coordination: stop using global conf object	2015-07-24 15:10:01 +02:00
i18n.py	Rename to aodh	2015-06-25 14:46:39 +02:00
keystone_client.py	keystone_client: stop using cfg.CONF	2015-07-24 10:13:31 +02:00
messaging.py	rpc: stop using global conf object in some functions	2015-07-24 10:13:31 +02:00
opts.py	Move Gnocchi options out of the "alarms" group	2015-07-24 10:13:05 +02:00
rpc.py	rpc: stop using global conf object in some functions	2015-07-24 10:13:31 +02:00
service.py	Move service classes to their correct subdir	2015-07-24 10:13:31 +02:00
utils.py	Rename to aodh	2015-06-25 14:46:39 +02:00