According to the documentation [1] and for consistency, notifications
sent by Heat for stack CRUD operations must be :
orchestration.stack.{create,update,delete,suspend,resume}.{start,error,end}
Currently the notifications sent looks like (missing 'stack.')
orchestration.{create,update,delete,suspend,resume}.{start,error,end}
Reviewed: https:/ /review. openstack. org/69372 /git.openstack. org/cgit/ openstack/ heat/commit/ ?id=793fbf6a472 f042d8738a29479 47ed59c1c43b0b
Committed: https:/
Submitter: Jenkins
Branch: master
commit 793fbf6a472f042 d8738a2947947ed 59c1c43b0b
Author: Swann Croiset <email address hidden>
Date: Mon Jan 27 14:51:18 2014 +0100
Fix event_type names for stack CRUD notifications
According to the documentation [1] and for consistency, notifications on.stack. {create, update, delete, suspend, resume} .{start, error,end}
sent by Heat for stack CRUD operations must be :
orchestrati
Currently the notifications sent looks like (missing 'stack.') on.{create, update, delete, suspend, resume} .{start, error,end}
orchestrati
[1] https:/ /wiki.openstack .org/wiki/ SystemUsageData
Fixes bug #1273240
Change-Id: Id46158c495f104 36b62755deaf5b6 a91e2e7e4bc