| 2014-01-27 14:23:37 |
Swann Croiset |
description |
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 :
orchestration.{create,update,delete,suspend,resume}.{start,error,end}
[1] https://wiki.openstack.org/wiki/SystemUsageData#orchestration.stack..7Bcreate.2Cupdate.2Cdelete.2Csuspend.2Cresume.7D..7Bstart.2Cerror.2Cend.7D: |
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 :
orchestration.{create,update,delete,suspend,resume}.{start,error,end}
[1] https://wiki.openstack.org/wiki/SystemUsageData |
|
| 2014-01-27 14:24:44 |
Swann Croiset |
description |
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 :
orchestration.{create,update,delete,suspend,resume}.{start,error,end}
[1] https://wiki.openstack.org/wiki/SystemUsageData |
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 :
orchestration.{create,update,delete,suspend,resume}.{start,error,end}
[1] https://wiki.openstack.org/wiki/SystemUsageData |
|
