zaletniy/gist:6800653

## gistfile1.txt
Trove-Heat Integration Topics:

1. Hardening the heat integration: The instances are not turning ACTIVE on multiple occasions. Further investigation on with the pointer that during some of these cases the prepare method is not called.
2. Heat Events than poll: The polling mechanism to check the status of the heat-stack for completion/failure can be replaced with handling the events from heat and acting accordingly. In the wake of point 1 above, it also needs to be validated that stack- creation-complete status from heat syncs with the instance creation within the stack.
3. Configurable templating: Making the template content as configurable.
4. Trove instance-store updates for multiple instances (governed by the template): In case the template provisions more than one instances then we need a design on the instance state update in trove db.
5. Any further abstractions in trove (may be an instance-group concept) per point 4: Do we need an instance-group like concept in trove for aggregating the multiple instances getting created through a multi-node template?
	Trove-Heat Integration Topics:

	1. Hardening the heat integration: The instances are not turning ACTIVE on multiple occasions. Further investigation on with the pointer that during some of these cases the prepare method is not called.
	2. Heat Events than poll: The polling mechanism to check the status of the heat-stack for completion/failure can be replaced with handling the events from heat and acting accordingly. In the wake of point 1 above, it also needs to be validated that stack- creation-complete status from heat syncs with the instance creation within the stack.
	3. Configurable templating: Making the template content as configurable.
	4. Trove instance-store updates for multiple instances (governed by the template): In case the template provisions more than one instances then we need a design on the instance state update in trove db.
	5. Any further abstractions in trove (may be an instance-group concept) per point 4: Do we need an instance-group like concept in trove for aggregating the multiple instances getting created through a multi-node template?