At DNS record creation step Trove should not speak to Nova if Heat provisioning enabled

[Denis M.]

When DNS record creation happens Trove-Taskmanager should not speak to Nova, it should speak to Heat for defining Compute Instance IP (PublicIP in terms Heat AWS::EC2::Instnace resource)

Prof. link: https://github.com/openstack/trove/blob/master/trove/taskmanager/models.py#L592-L634

Instead of given mechanism Trove should able to read Stack outputs if Heat provisioning enabled.

Example(HOT): https://github.com/openstack/heat-templates/blob/master/hot/hello_world.yaml#L53

Example (AWS, JSON): https://github.com/openstack/heat-templates/blob/master/cfn/deb/WordPress_Single_Instance_deb.template#L152

Example (AWS, YAML): https://github.com/openstack/heat-templates/blob/master/cfn/deb/MultiNode_DevStack.yaml#L436-L450

[Amrith Kumar (amrith)]

Updating importance to "Low" (bugscrub, 2014-10-23)